What is User Security in Enterprise Architect?

User security in Enterprise Architect can be used to limit the access to update functions within the model. Elements can be locked per user or per group. Where user security is enabled a password is required to log in to the model. Security in Enterprise Architect is not designed to prevent unauthorized access; rather it is intended as a means of improving collaborative design and development  by preventing concurrent editing and limiting the possibility of inadvertent model changes by users not designated as model authors. 

User Security Basics

User security is available only in the Corporate edition of Enterprise Architect. User security in Enterprise Architect offers two policies, the standard security model and the rigorous security model. In the standard security model all elements are considered unlocked and, as necessary, a user can lock any element or set of elements at the user or group levels depending on permission rights that the user has to the model. The rigorous security model assumes that everything in the model is locked until explicitly checked out with a user lock. In this mode, an Enterprise Architect model is read-only until a user applies an editing lock on one or more elements. For more detailed information on the security policies see the Security Policy topic.

User Security Tasks

A number of security tasks can only be performed by users with Administrative rights to the model. These tasks include:

Other Security tasks can be performed by users who do not have Administrative rights. These tasks include:

 

Note: User security is not enabled by default in Enterprise Architect; you must enable it first.

Note: For a number of operations in Enterprise Architect, if security is enabled, a user must have the appropriate user or group access permission to perform the operation. However, if security is not enabled, the user does not have to have access permissions. See List of Available Permissions.