Team Roles

A Role defines what a team member can see and do within an initiative or program — assigned when adding someone to a team.

A team role is separate from an admin role. A team role controls what a team member can see and do within the initiatives or programs they're a team member of, and is assigned when they're added to a team. An admin role controls access to the Administration menu, across the whole instance, and is assigned on the user record. See Admin Roles.

Each permission area within a Role uses the same permission levels as Admin Roles: None, Read, Update, or Full.

Creating a role for an initiative classification

In the Advanced Model, roles for initiatives are created via the Administration pages:

1. Navigate to the Administration section.

   

2. Click Teams & Roles in the side navigation.

   

3. Select the Team Roles tab.
4. Click Create New Team Role, or the edit button for an existing role.

5. Give the Role an easily identifiable name.

   

6. Select the option to grant for each permission. Read each one carefully before you choose.

   

7. Use Select Lowest and Select Highest to bulk-apply options where needed.

   

8. Select Cascade permissions where a user with this role should retain these permissions down through the hierarchy.

   

9. An initiative's data typically rolls up to the levels above it. Deselect Allow dashboard access to child initiative and benefit data if you don't want this role to see that rolled-up data.

   

10. Once configured, click Create or Save.

    

    

Creating a role for a program

In the Simple Model, roles for programs and projects are created within each individual Program:

1. Navigate to the Program you want to manage.

   

2. Click Teams & Roles in the side navigation.

3. Click Roles & Permissions.

   

4. Click + New Role, or the edit icon for an existing role.

   

5. Give the Role an easily identifiable name.

   

6. Select the option to grant for each permission. Read each one carefully before you choose.

   

7. Use Select Lowest and Select Highest to bulk-apply options where needed.

   

8. Once configured, click Save.

   

Default access for new users

Every new user — whether created by an administrator, imported, or created through single sign-on — is added to the Default Access shared team, with the Default Role. Together, they set what new users can see as soon as they first sign in.

• Default Access — a shared team. Add it to the levels of the hierarchy new users should see, such as the enterprise or a portfolio. Until it's added somewhere, it gives new users no access. See Managing Shared Teams.
• Default Role — the role new users have in that team. It starts with read access to initiatives only, with Cascade permissions turned on, so new users can also see the levels below where Default Access is added. Edit it under Administration > Teams & Roles, like any other role. It can't be deleted.

Checking someone's permissions

To see what people can do on an initiative, open the initiative's Teams & Roles menu, and select Audit. Opening it needs permission to view the initiative's team.

The table lists everyone who can view the initiative, or see its data on dashboards at the levels above, sorted by name. Locked users aren't listed. Each permission has a column — or a Read and an Update column — showing Yes where the person has it, and No where they don't.

The table shows the permissions Amplify applies, however the person holds them: through the initiative's own team, a shared team, a role that cascades from a level above, or administrator access.

For adding people to teams, see Adding Team Members.