I am working to simplify my User Groups set-up; by separating the License privileges into one group per license type; and keeping the access privileges in separate groups. This should make it easier to see where all the licenses are being consumed.
I would also like to reduce redundant license assignments, but I am not sure how the licenses relate to each other.
Does a 'bigger" license include the "smaller" or "lower level" license?
For example, if I assign an Architect license to a user; do they also need to be assigned a Connect Designer license, to use Connect Designer?
Similarly, if a user has a Connect Designer license; do they also need a Viewer Pro license to contribute?
Is there a reference for this somewhere?
thanks in advance,
John
Runé Becker on
Dear John,
In the document ARIS Functional Product Matrix.pdf you can find almost all features mapped to the respective ARIS products.
An Architect license doesn't include any Connect client license. But a Connect Designer license covers everything what Connect Viewer includes. Therefore the available check boxes are disabled when you assign the one or the other license.
Several base client licenses offer so called Extension Packs (EPs), shown in the user interface as indented check boxes. The latter can only be assigned when the base license has been assigned. Also that dependency is supported by disabled check boxes for all EPs when the base license isn't yet ticked.
Does this help?
Cheers
Rune