Understanding Agility Roles & Project Membership

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 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, etc.

• Project Role
  When a member is assigned to a project, they receive a specific Project Role which grants access to projects based on the role the member plays within each project they work on (e.g., team member, project lead, tester, etc.). This role is important because it determines whether 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 will not see the project listed in the project tree.