Project access
Roles decide what a member can do. Project access decides where: every project in your organization, or only the ones you choose. Use it for agencies, freelancers, or teams that should only see their own sites.
The two choices
| Choice | Means |
|---|---|
| All projects | Every project in the organization, including projects created later. |
| Specific projects | Only the projects you choose. New projects are not added automatically. |
A member's role applies the same way in each project they can open. A Content Editor limited to two projects is a Content Editor in both; there is no separate role per project.
Who always has every project
Some members can't be limited. For them Studio shows All projects, locked, with the reason:
- the account owner;
- organization admins;
- anyone holding the Admin role. To limit their projects, give them another role first.
If someone stops being exempt (for example, you change their role from Admin to Content Editor), the project access saved for them before applies again.
Set project access
When you invite someone, choosing project access is required. See Invite people.
For an existing member:
- Open the Users list and select the member.
- Under Project access, choose All projects or Specific projects, and pick the projects.
- Save.
The Projects column in the Users list shows each member's access at a glance: All projects, or how many projects they have.
What a limited member sees
- The project switcher lists only their projects.
- Studio and the API behave as though the other projects don't exist.
- If you take a project away while they're working in it, their next action in that project is refused and Studio moves them to a project they can still open.
- If they have no projects left, they see a No projects yet screen asking them to contact an admin. From there they can check again, switch to another organization or open their account.
- A project they create is added to their list automatically.
Project templates are not affected: whether someone can open a template depends only on their role.
API tokens
A member limited to specific projects can only create API tokens for one of their projects, not organization-wide tokens. Limiting someone later doesn't change tokens they already created. Review those under your organization's API tokens.
When projects are deleted or trashed
- Trashing a project leaves everyone's lists alone. If you restore it, the same members can open it again.
- Permanently deleting a project removes it from every list. A member whose only project it was is left with no projects until you give them another.