---
title: 'Members and permissions'
description: 'Understand invitations, project roles, and space assignments.'
---

# Members and permissions

Team membership and project membership answer different questions. A team role governs administration; a project role governs access to project data and settings. Spaces further restrict resources within a project.



## Invite and manage members

1. Select the team or project, then open **Members**.
2. Inspect **Team Members** or **Project Members** and **Pending Invitations** before inviting someone again.
3. Use **Add Member**, enter the intended email, and choose the appropriate role.
4. After acceptance, inspect the member in the active members list. Give the user your hosted Studio URL.
5. For project spaces, open **Manage Access** on the member after the developer deploys the space definitions.

## Role purposes

| Project role | Intended access                                                        |
| ------------ | ---------------------------------------------------------------------- |
| Owner        | Data read/write and full project administration; access to all spaces. |
| Developer    | Data read/write and developer settings.                                |
| Editor       | Data read/write and limited settings.                                  |
| Contributor  | Data read/write without project settings.                              |
| Viewer       | Read access and limited settings; no data mutations.                   |

Team roles are **Owner**, **Member**, **Billing**, and **Viewer**. Billing is a team administration role, not a project data role. Team owners can administer their projects without relying on an ordinary project-member seat.

## Space access

Spaces are defined in code and assigned through Dashboard. A resource bound to several spaces is accessible through membership in any listed space. Owners have all-space access. Use a non-owner account when checking restricted behavior; an Owner test cannot demonstrate that restrictions work.

Removing a space grant and changing a role are separate actions. A role that permits writing does not grant access to every space-bound field. See [spaces](/docs/schema/spaces) and [API credentials](/docs/api/tokens).

## Troubleshoot invitations

Check the email/account, whether the invitation targets the team or the project, and pending status. For an accepted member who sees no data, inspect the configured project ID and spaces before issuing another invitation. Preserve administrative ownership when changing or removing members.


---

[View full sitemap](/docs/sitemap.md)