Teams
Learn how to use teams for change management.
Contributors: Jennifer Hoffman.
Discuss in our Forum Discuss in SlackTeams allow you to define the users who will have access to a workspace or site. Team members added to a workspace will have access to all sites in that workspace, whereas team members added to a site can only access that site.
Roles and Permissions
These tables detail the actions each role can execute on each Dashboard.
In some Workspaces, you may notice the "User in Charge" label applied to a user. This helps distinguish who created a site for Enterprise and EDU workspaces where members are allowed to spin up new Sandbox sites at will. However, in these workspaces, the "User in Charge" cannot adjust the site service level — e.g. to take a site live. Because this may affect the overall bill for the workspace, only workspace admins are allowed to change service levels.
If you are an administrator for a Pantheon workspace, contact support to have the User in Charge changed.
Workspace Level Permissions
| Permissions | Administrator | Team Member | Developer | Unprivileged |
|---|---|---|---|---|
| Create sites within an org | ✔ | ✔ | ✔ | ✔ |
| Work in Dev environments | ✔ | ✔ | ✔ | ✔ |
| Access to Multidev environments | ✔ | ✔ | ✔ | ✔ |
| Create new Multidev environments | ✔ | ✔ | ✔ | ✔ |
| Create or view support tickets | ✔ | ✔ | ✔ | ❌ |
| Access and manage Autopilot | ✔ | ✔ | ✔ | ❌ |
| Access the workspace | ✔ | ✔ | ✔ | ❌ |
| Access the org Dashboard | ✔ | ✔ | ✔ | ❌ |
| Change site upstream | ✔ | ✔ | ✔ | ❌ |
| Deploy to Test and Live | ✔ | ✔ | ❌ | ❌ |
| Invite new team members | ✔ | ✔ | ❌ | ❌ |
| Manage user roles | ✔ | ❌ | ❌ | ❌ |
| Delete sites or remove users from an org | ✔ | ❌ | ❌ | ❌ |
| Manage a site's plan | ✔ | ❌ | ❌ | ❌ |
| Create or manage Custom Upstreams | ✔ | ❌ | ❌ | ❌ |
Site Level Permissions
| Permissions | Org Admin / Owner | Team Member | Developer |
|---|---|---|---|
| Access the site Dashboard | ✔ | ✔ | ✔ |
| Work in Dev environments | ✔ | ✔ | ✔ |
| Change site upstream | ✔ | ✔ | ✔ |
| Deploy from Custom Upstreams | ✔ | ✔ | ✔ |
| Add/Manage Custom Domains | ✔ | ✔ | ❌ |
| Deploy to Test and Live | ✔ | ✔ | ❌ |
| Upload files to Test and Live | ✔ | ✔ | ❌ |
| Access SFTP download logs on Test and Live | ✔ | ✔ | ❌ |
| Clear cache on Test and Live | ✔ | ✔ | ❌ |
| Manage user roles | ✔ | ❌ | ❌ |
| Delete sites or remove users from a site | ✔ | ❌ | ❌ |
| Add a Supporting Organization | ✔ | ❌ | ❌ |
| Manage a site's plan | ✔ Org admin or Owner | ❌ | ❌ |
| Enable Pantheon Search | ✔ | ❌ | ❌ |
Manage Teams
Add a User
Go to the workspace, select the Team tab, and click Add User.
Click Invite Team Member.
Enter the email address of the new user, select a role, then click Send Invite.
Open the Site Dashboard for the site.
Click Team.
Under Team Members, enter the user's email address, select a role (EDU+ and Enterprise sites only), then click Add to Team
An email confirmation is sent to the user. Users with an existing Pantheon account are immediately added to the workspace. Users without existing accounts must first click the confirmation link in the email to create their account.
Change a User's Role
Go to the workspace and select the Team tab.
Find and select the team member(s) whose role you want to change.
Click Actions, and choose Change Role.
Select the new role, then click Save Changes.
Remove a User
Note
All users can be removed except the site owner.
To remove a user:
Go to the workspace and select the Team tab.
Find and select the team member(s) you wish to remove.
Select Actions, then Remove.
Select Yes, I am sure I want to remove this person, then click Yes, Remove.
To remove a team member from a site:
Open the Site Dashboard for the site.
Click Team.
Select the 'x' for each team member you wish to remove.
When a person with access to your site(s) on the platform leaves the company or project, it is important to immediately remove them from the team so that they no longer have access to make changes to your site.
After a user leaves, in addition to the steps above, we recommend you:
- Delete or block the user's account in Drupal or WordPress.
- Change any shared account passwords the user may have had access to.
- Review the Git history in the commit log to see if the site team member made code changes after leaving. Refer to recommendations from Drupal and WordPress.
Add a Supporting Organization to Site
One of the best things about Pantheon is the ability to collaborate with agencies and shops on web projects. If you have contracted with a Pantheon Partner Agency, you can add them to the site as a Supporting Organization, which will give their company access to help build, launch, or maintain your site.
Workspace Administrators, Users in Charge, or Site Owners can add a Supporting Organization.
Open the Site Dashboard for the site.
Click Team in the Site Dashboard.
Click Add a Supporting Organization, enter the workspace's name in the search box, and click Search. The workspace name must match exactly.
Select a role, then click Add. All members of the Supporting Organization receive the role assigned on the site, regardless of their role in the Supporting Organization.
FAQ
Can I restrict access to a specific site with the Developer role?
Only sites owned by Enterprise and EDU+ can assign the developer role to specific users. Partner workspaces cannot specify which members have access to specific sites.
Which role should I assign a user to give them the lowest level of access?
At the site level, the Developer role has the least amount of permissions and can create sites, view the Workspace Dashboard, and deploy to the Development and Multidev environments. At the Professional Workspace level, the Unprivileged role has the least amount of permissions and can only create sites.
Which environments can a user with the Developer role deploy to?
The Developer role can only deploy to Development and Multidev environments. If a user needs to deploy to Live, you can promote a Developer to Team Member for a single site by adding the user to the site's team.
Who can add users to workspaces?
Enterprise Administrators can add site Team Members or Supporting Organizations to sites owned by the workspace, with the Developer or workspace Team Member roles. Partner workspaces can assign users the role of an Administrator, Team Member, or Developer at the workspace level.
How do I recover an account after a site owner leaves?
Refer to the steps in our Site Access doc for recovery instructions.