A new user has no rights assigned by default and belongs only to the PUBLIC group, which has no rights. In order for the user to be able to do anything, the repository administrator must assign rights to the user. The same types of rights can be assigned to groups and users.
The user rights can be combined to create different kinds of user profiles. The following table shows typical project profiles. Note the difference between data administrator who manages data in the repository, and repository administrator who manages the repository and the users.
User profile |
Required user rights |
---|---|
Database Administrator |
Connect, Manage Repository, and Manage Users |
Data Administrator |
Connect and Manage All Documents |
Team Leader |
Connect, Lock Versions, Freeze Versions, Manage Branches, and Manage Configurations. |
Designer |
Connect, Lock Versions, and Freeze Versions |
User rights can be associated with permissions on documents to define the actions a user can effectively perform on a document.
Some user rights are automatically associated with permissions for consistency reasons:
Lock and Freeze Versions are associated with the Write permission. A user with the Lock or Freeze Versions right must have a Write permission on the repository document.
A user with the Full permission on a document can unlock or unfreeze a version he did not lock or freeze.
For more information on document permissions, see Controlling Permissions for Repository Items.