SQ
Hi
In ARIS Connect, on a versionable database, there are nine possible values (see attachment) for a user's database privileges. Please can someone explain a) what they do, b) how they differ from each other, and c) is there a way of seeing a user's existing privileges before opening the drop-down list?
I've checked the ARIS Adminstration Help but it just says 'select the one you want'; it gives zero guidance about what they mean. I've searched the Community but after trawling several pages of posts could not find an answer.
Thanks, Simon
Hello,
be very careful with this feature. As it says: "It affects all groups in the database". Whatever privilege you select there will be written to ALL groups in the database, potentially elevating privileges for this user on groups where he currently has no or less privileges. The better way is to administer authorizations on individual groups in the database by assigning privileges to individual user groups (as opposed to individual users).
Here is the translation:
R: The user may see the objects in the group, read their attributes and open models in the portal for viewing or in Connect Designer in Read-only mode (if he has got a Connect Designer license).
C: The user may comment on the models of the group in the model feed of the collaboration.
W: The user may modify objects and models in the group and create new models and objects in the group. He may create occurrences of objects in models of the group. He needs at least read permission to the group containing the objects he wants to create occurrences of.
D: The user may delete objects and models in the group and additionally the group itself (if he has delete permissions on all subgroups).
V: The user may version models in this group. For successful versioning of a model he also needs versioning privileges for all groups containing the objects that have occurrences in the model.
Remark on versioning: Versioning should follow a well established concept, particularly if it is used for publishing content in the Connect portal.
Remark on deletion: Deletion should also follow a well established concept, particularly if versioning is used for publishing content in the Connect portal.
EDIT: In short, there are no "database privileges". It is only a shortcut feature to set privileges across the whole database.
