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. They sign in to the desktop or web app with the invited address and find the project there.
5. For project spaces, open Manage Access on the member once the spaces exist in the schema.

Role purposes

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 part of the schema (ask the agent to add one, or define it in code) and assigned to members 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 and API credentials.

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, check that they signed in with the invited address and inspect their spaces before issuing another invitation. Preserve administrative ownership when changing or removing members.