Administration Privileges Role Summary and Descriptions in Agility
This topic explains the Admin Privileges Role Summary and Descriptions in Agility.
Overview
This article is intended for administrators responsible for creating and managing member accounts and provides instructions for assigning Administration Privileges roles to member accounts.
The Administration Privileges role determines what actions members can perform in the system, including:
- Making system configuration changes
- Managing sprint or iteration schedules and adding individual sprints
- Managing member accounts
- Managing Digital.ai Agility subscription and account details
Important Notes
- A member's Administration Privileges role does not determine access to projects or permissions. To grant access to a project, you must first assign them to a project, and then assign a project role to grant permissions.
- When a member is assigned to a project using the drag-and-drop method, their Admin Privileges role is copied to the project as their project role. Depending on the Admin Privileges role that is copied, the member may not have access to the project's assets. For example, an Administration Privileges role of No Access or Visitor will limit access when applied as a project role at the project level. To grant explicit access to the project's assets that is different from those allowed by the initial project role, a new project role must be explicitly assigned.
- In Catalyst edition, only the System Admin and Team Member Administration Privileges roles are available. In addition, the project role cannot be changed on a per project basis; Catalyst members have the same role for both Administration Privileges and project role (for all projects).
Administration Privileges Role Access Summary
The table below shows each Administration Privileges role and their level of system configuration access. To learn how to assign a role to a member's account, see Assigning an Administration Privileges Role to an Existing Member.
Role Name | ● Edit | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Feature Access | System Administration | Member Administration | Project Administration | Project Lead | Team Member | Developer | Tester | Product Owner | Requestor | Observer | Visitor | Inheritor | No Access |
System Configuration | ● | ||||||||||||
Account Admin | ● | ● | |||||||||||
Member Admin | ● | ● | |||||||||||
Roles | ● | ||||||||||||
Lists | ● | ||||||||||||
Member Groups | ● | ● | |||||||||||
Test Integration | ● | ● | ● | ||||||||||
Change Sets | ● | ● | ● | ● | ● | ● | ● | ● | |||||
Teams | ● | ● | ● | ● | ● | ||||||||
Build Projects | ● | ● | ● | ● | |||||||||
Sprint or Iteration Schedules | ● | ● | ● | ● | |||||||||
Applications | ● | ||||||||||||
Workspace Required Fields | ● |
Related concepts
Related tasks
Enabling Team Process Management
Adding New Status Value to Team Process
Changing the Status Value Order