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?
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.
My question is most specfically about Architect and Connect Designer. During our pre-sale discussions, I was led to believe that if a person is assigned an Architect license, they do not need to also consume a Connect Designer license. But it appears this is not the case; if a user needs to use both Architect and Connect Designer, then they must be assigned both (via the user groups) and that one person will consume both licenses.
I think the main distinction is between the old-style Architect and Designer client licenses, and the newer Connect Designer and other Connect components. Apparently the licenses are separate. I did not understand that from our pre-sale conversations.
Please let me know if I misunderstood any of the above, otherwise I am "good for now" and I thank you again.
