10.4.6 Set Group Security

Different levels of security can be assigned to Environments when added to a Group in the System Admin section:

• None: The group won’t have any pre-determined permissions on the environment’s objects. If applied to all objects, the group won’t have access to the environment unless the security is changed manually within an object for the group of for the user(s).
• Read published: The group will be able to see only the published version of objects and won’t see “in progress” (draft) versions. Additionally, they won’t be able to edit or delete.
• Read latest: The group will be able to see all versions of objects but won’t be able to edit or delete.
• Write: The group will have access to all versions of objects as well as editing rights but won’t be able to delete.
• Delete: The group will have access to all versions of the object. They can also edit and delete. Modelers with this permission can set security of objects.
• Environment Admin check box: The group will be environment admins in the environment. They will have Delete permission on all objects in the environment as well as being able to access the environment admin section.

If the “Apply to all objects” box is clicked, this is what group security will look like on all objects in the environment (unless the security is changed manually within an object for the group of for the users):

!If users have different permissions granted in different levels, like one for group and one for user, then the highest security is the one granted. For example, if you have read latest permission on an object, but your group has delete permission on that same object, you will have delete permission. To learn more about security permissions, please click here.