Version: Early Access

Admin Privileges Role Summary and Descriptions

Overview

This article is intended for administrators responsible for creating and managing member accounts and provides instructions for assigning Admin Privileges roles to member accounts.

The Admin 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 Admin 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 Admin 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.

Admin Privileges Role Access Summary

The table below shows each Admin Privileges role and their level of system configuration access.

Admin Privileges

	Role Name												Edit
Feature Access	System Admin	Member Admin	Project Admin	Project Lead	Team Member	Developer	Tester	Customer	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	●