About Sub-Administrators

A sub-administrator is a user who has been assigned specific rights by a system administrator to one or more administration tools (User Admin, Web Layout Editor, Repository Manager, and Workflow Admin) to administer portions of the software that correspond to those rights. Users with the admin role are the only users who can access the Configuration Manager and Archiver tools.

Sub-administrators need to have Admin permission to at least one security group to be able to perform administrative tasks. Typically, a sub-administrator is assigned to be the administrator for a particular security group or account.

The following table describes the functions that a sub-administrator can perform:


Right	Description
UserAdmin	Add, edit, and delete users whose roles and accounts are a subset of the roles and accounts of the sub-administrator.
WebLayout	Add, edit, and delete Library pages to which the sub-administrator has Admin permission for the corresponding security groups and accounts.
RepMan	View documents and execute Repository Manager functions (update, approve, delete, and so forth) on documents to which the sub-administrator has Admin permission.
Workflow	Add, edit, or delete workflows that are in a security group to which the sub-administrator has Admin permission.

Consider JDoe’s sub-administrator rights as identified in Figure 5-2 and the corresponding explanation.

UserAdmin: User MLing’s roles and accounts are a subset of user JDoe’s roles and accounts, so JDoe has the authority to add, edit, and delete user MLing. However, user LTesch has higher permissions for the MKTDocs security group than does JDoe, so JDoe cannot add, edit, or delete LTesch.

WebLayout: JDoe cannot perform any Web Layout Editor administrative tasks because JDoe does not have WebLayout rights.

RepMan: JDoe can execute Repository Manager functions on documents that are in the EngDocs security group account a, or documents that are in the EngDocs security group and are not assigned an account. However, JDoe cannot execute Repository Manager functions on documents that are in the EngDocs security group in account b, c, or documents in any other security group because JDoe does not have Admin permission for these documents.

Workflow: JDoe can add, edit, and delete workflows that are in the EngDocs security group.

Managing Security and User Access

Internal Security: Assigning User Logins and Aliases > Sub-Administrators > About Sub-Administrators