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:

See published versions See all versions, drafts Can edit the object Can delete the object Can set security perm. Access to Env. Admin Section
Read published X
Read latest X X
Write X X X
Delete X X X X If modeler, yes
Env. Admin X X X X X X

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

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
Visit the Support Portal

Post Comment