Skip to main content
System StatusContact Support Agility Community

Understanding Roles and Project Membership

This feature is available in all editions.


Overview Agility uses two access levels to determine what each member can and cannot do within the system. The first level is called Admin Privileges (previously called "Default Role") and the second level is called Project Role (see explanations below). By grouping access levels in this way, system administrators can easily assign access to members based on the way they use the system.

  • Admin Privileges Role. The first level, called Admin Privileges, is the initial role assigned to each member when their account is created. It grants them basic access to Agility and controls the set of administrative tasks they can perform. These tasks include the maintenance and configuration activities required to manage the system, including system configuration, adding new members, and so on.
  • Project Role. When a member is assigned to a project, they receive a specific Project Role.  The Project Role grants access to projects based on the role the member plays within each project they work on (for example, team member, project lead, tester, and so on). This role is important because it determines if a member can create, view, and modify project artifacts on a per-project basis. If a member has not been assigned a Project Role on a project, they cannot see the project listed in the project tree.

  • The Project Role is not the same as the Admin Privileges role, even though the names in the selection list are similar.
  • The Admin Privileges role (previously called the Default role) is the role assigned to each member when their account is first created.

Learn how to create and manage users in Agility