User properties

See Table 18.1 for descriptions of user properties that might require further explanation, beyond their field names.

Table 18.1. User properties

FieldDescription
StateDetermines whether the user can connect to the repository. An active user can connect to the repository. An inactive user cannot.
NameThe user’s name as it appears on the user’s home cabinet, and on items the user creates or modifies.
User Login NameThe name with which the user logs into the repository.
User SourceThe authentication source. Select None if the user is authenticated in a Windows domain or if the user has an account on the Content Server host, and is authenticated by the operating system.
E-Mail AddressThe address to which notifications are sent for workflow tasks, and registered events.
User OS NameThe login name for authenticating the user on an operating system or on an LDAP server.
Windows DomainThe user’s Windows domain, to be used if the repository is on a Windows host or on a UNIX host with a domain map for Windows domain authentication.
Home RepositoryThe repository where the user receives notifications, and tasks.
Restrict Folder Access ToRestricts the user’s repository access to particular repository locations.
Default FolderThe location for storing items the user creates.
Default GroupThe group assigned to items the user creates.
Default Permission SetThe permission set assigned to items the user creates.
Db NameThe user’s name in an RDBMS. This is used if the user is a repository owner or registers RDBMS tables.
Privileges

This authorizes the user to perform certain activities.

When setting this, if you grant superuser privileges to a user after installing or upgrading a repository or after manually running the toolset.ebs script, add that user manually to the group called admingroup.

If you revoke a user’s superuser privileges, remove the user from the admingroup.

Alias SetThe user’s default alias set.
Workflow DisabledIndicates that the user is not available to receive workflow tasks.
Propagate changes to members

If creating a global user, this propagates your changes to members of the repository federation. A global user is a user who is found in all members of a repository federation, and whose property values are the same in all of the repositories. Global users are managed through the governing repository. Global users can also have local properties, which you can modify in a local repository.

For more information on global users, see the Documentum Administrator User Guide.

Turn off authentication failure checkingAllows the user more login attempts than the limit set in the repository config object.