10.2.6 Set Environment Security

Different levels of security can be assigned to the Users and Groups added to an Environment:

• None: The user won’t have any pre-determined permissions on the environment’s objects.
• Read published: The user 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 user will be able to see all versions of objects but won’t be able to edit or delete.
• Write: The user will have access to all versions of objects as well as editing rights but won’t be able to delete.
• Delete: Users 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 user will be environment admin 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 and set security permissions on objects.

When clicking on the “Apply to all objects” box, the chosen permission will be automatically propagated to all objects of this environment. This is what the user’s or group’s security will look like on all objects in the environment:

!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.

To know how to change the security of a group or a user to the environment, see this topic.