P1 user management lets websites' owners and administrators manage the people who work in their Business Account to oversee the content of their fleet of websites. This also covers the AI agents those people use, so access can be granted and revoked for both. Use this guide to add users, assign Business Account roles, update access, and remove users or agents when they no longer need access.
This page focuses on Business Account-level user management. Site-specific permissions, collections, and agent access are managed separately directly in the sites or workstreams.
The selected Business Account is the scope for the Users page and for the actions you take there. If you manage more than one Business Account, repeat these steps for each Business Account rather than assuming a change applies everywhere.
Role | Use this role for | User-management access |
Admin | People who need to help manage the organization’s P1 users and access | Can open Users and add users, change roles, deactivate users, and remove users |
Member | People who need to work in P1 but should not administer organization membership at large | Cannot access the organization’s user-management interface |
Assign Admin only when a person needs to manage organization membership. Use Member for everyone else who does not need administrative responsibility.
Feature | Admin | Member | Viewer |
Create site | ✅ | ||
Archive site | ✅ | ||
Create workstream | ✅ | ||
Archive workstream | ✅ | ||
View Site structure and settings | ✅ | ✅ | ✅ |
View page in Visual Editor | ✅ | ✅ | ✅ |
Create page | ✅ | ✅ | |
Publish page to live | ✅ | ✅ | |
Delete page | ✅ | ✅ | |
Create / update / archive template | ✅ | ||
Manage pinned component | ✅ | ||
Review workstream | ✅ | ✅ | |
Resolve conflicts | ✅ | ✅ | |
Merge workstream | ✅ | ✅ | |
Add user to Business Account | ✅ | ||
Deactivate user | ✅ | ||
Remove user | ✅ | ||
Add user to site | ✅ | ||
Create site token | ✅ | ||
Revoke site token | ✅ | ||
Create agent | ✅ | ||
Comment (future) | ✅ | ✅ | ✅ |
Invite people with the email address they will use to sign in to Pantheon. An invited user should be associated with the Business Account to which they were invited, rather than creating a separate P1 subscription or Business Account.
If the person already works with another Pantheon Business Account, they can use the same login and switch between the Business Accounts they are authorized to access.
Use the lowest-privilege role that supports the person’s responsibilities. Give someone Admin access only when they need to manage users or other Business Account-level administration.
Deactivate a user when they should temporarily lose access but may need to return later.
For employee leave, temporary contractor pauses, or other short-term access changes, deactivation is preferable to deleting the user because it preserves the Business Account relationship for later restoration.
Remove a user when they should no longer be a member of the Business Account.
Removing a user from one Business Account does not necessarily remove them from other Business Accounts they belong to. Verify the active Business Account before and after the change.
Keep at least one administrator for the Business Account. Do not remove the last person responsible for administering the Business Account, and do not remove the owner unless your Business Account has another supported ownership path.
Agents are automated users that can act on behalf of your Business Account. They are managed separately from human users so that administrators can review and control their access independently.
Use agents when an integration or automated workflow needs to work with P1 content or a site. Give each agent only the access it needs, and review that access regularly.
P1 Agent is Pantheon’s first-party agent. It is available by default in every Business Account and is authorized by P1, so administrators do not need to register or invite it like a customer-created agent.
Availability does not mean that every Business Account can use every P1 Agent capability. Each Business Account may be entitled—or not entitled—to specific P1 Agent functionality or usage. Your Business Account’s entitlements determine what the P1 Agent can do for that Business Account.
P1 Agent is managed differently from customer-created agents:
Agents should have their own identity and credentials. Do not share a person’s login or API key with an agent, and do not share an agent’s key between multiple agents.
Agent access is separate from a person’s Admin or Member role. Giving someone Admin access does not automatically give an agent access to the same sites, and creating an agent does not give a person additional access.
If P1 provides a key when you register an agent, store it securely and treat it like a password.
For each agent, keep a record of its owner, purpose, sites, permissions, and key rotation or expiration plan. Review this information regularly and remove agents that are no longer used.
You may be viewing the wrong Business Account, or you may be a Member rather than an Admin. Switch to the intended Business Account and confirm that your account has an administrative role.
P1 scopes user visibility to the current Business Account. Confirm that you selected the correct Business Account and that the person has been added to it. Users who belong only to another Business Account should not appear in the current Business Account’s user list.
The invitation should associate the person with the Business Account that invited them. Confirm that they are signing in with the invited email address and that they opened the invitation intended for your Business Account. If the user is still routed to create a separate Business Account, contact your Pantheon administrator or support team.
Use the Business Account switcher to select the Business Account the user should work in. Manage the user’s role separately in each Business Account where they have access.
Use the Business Account switcher to select the Business Account you want to manage, then use its Users page to add users, assign Admin or Member roles, deactivate access, or remove users. Keep Business Account boundaries in mind: user lists and changes are scoped to the active Business Account.