Assigning Workflow and Document Project Administrators
The super administrator is responsible for setting up Integrity Lifecycle Manager and therefore has access to all administrative objects, including users, groups, dynamic groups, workflow and document projects, states, types, fields, and triggers. The super administrator can also designate groups or individual users, or a combination of them, to be project administrators for selected projects in Integrity Lifecycle Manager.
An Integrity Lifecycle Manager project administrator is responsible for administering specific workflow and document projects, assigned by the super administrator. To enhance project security, only the projects that a project administrator is assigned to display in the Integrity Lifecycle Manager administration client GUI and CLI, allowing them to select, edit, and view only those projects. Project administrators can also edit and view all child projects of the project they are assigned to. Project administrators cannot edit and view projects assigned to another project administrator, and they can only create and delete subprojects—they cannot create top level projects unless they have been granted the CreateProject permission.
Project administrators can also view all users, groups, and dynamic groups, but they can only edit dynamic groups membership for the projects they are assigned to.
Workflow and document projects are hierarchical; therefore, when creating a top level project, the creating super administrator is automatically set as the project administrator. When creating a subproject, the administrator list is empty because administrators of the parent project are, by default, administrators of its subprojects. The creating administrator can modify the default as required.
If the assigned project administrators are granted the CreateProject ACL permission, they are allowed to create top level projects, as well as to delete any top level projects. Integrity Lifecycle Manager project administrators who are granted the CreateProject permission can also assign other project administrators.
|
Project administrators are not allowed to assign themselves as administrators to any other projects or to assign others as project administrator, unless they have first been granted the CreateProject permission.
|
The list of available users and groups contains all active and inactive members that have been imported into Integrity Lifecycle Manager; however, the available list does not necessarily include all users and groups available in the realm.
The following table summarizes the basic functionality available to the project administrator:
Project administrators can:
|
Project administrators cannot:
|
Create new subproject (child project) in workflow and document project they are assigned to.
|
Create top level workflow and document project or create users, groups, dynamic groups, states, types, fields, or triggers.
|
Edit workflow and document projects they are assigned to, including images, descriptions, and permissions.
Edit project memberships in corresponding dynamic groups.
|
Edit any other process and control objects such as users, groups, states, types, fields, triggers, or projects they are not assigned to.
|
View users, groups, dynamic groups, and projects they are assigned to.
|
View states, types, fields, triggers, or projects they are not assigned to.
|
Delete subprojects they created.
|
Delete top level workflow and document project.
|
Create top level workflow and document project (if CreateProject permission is allowed).
|
Assign another project administrator or view administrator information for project they do not administer.
|
Example
Neil is the project administrator for the SourceCode project. By extension, he is also the project administrator for the two subprojects under SourceCode (Client and Server).
If the super administrator also grants Neil the CreateProject permission, Neil is allowed to create top level projects and assign other Integrity Lifecycle Manager project administrators at the time the project is first created. With the CreateProject permission, Neil can also assign another project administrator to the SourceCode project. By extension, all assigned project administrators for the SourceCode project are allowed to edit the Client and Server subprojects.
Key Considerations
• Only the super administrator can automatically assign a project administrator in Integrity Lifecycle Manager.
• Project administrators are not allowed to assign themselves as administrators to any other projects or to assign others as project administrator, unless they have first been granted the CreateProject permission.
• If a project administrator has additional permissions that allow them to view projects they are not assigned to, such as Admin or CreateProject, those projects also display.
• If a project administrator is assigned to a subproject but not the parents of that subproject, they can see the names of the parent projects in the context of the subproject only; those parent projects cannot be viewed or edited individually.
Related Links