Members

Use this page to manage organization access with role-based and feature-based permission control.

​

Questions this page should answer

1. Who currently has access to this organization?
2. How do I invite a new member with the right scope?
3. How do None, View only, and Full actually affect access?

​

Before you use this page

• In the app, open Organization settings and select Members.
• Confirm you have members write access.
• Check seat availability before bulk invites.

​

What this page controls

• Member directory (Email, Role, Project access, Joined at, Actions).
• Invite flow with role + workspace permissions + project permissions.
• Edit permissions flow for existing members.
• Member removal.

​

Invite members flow

Invite members opens a dialog where you define access before sending invites.

​

How to invite correctly

1. Add one or multiple emails.
2. Select role: Admin: full access across workspace and projects. Member: granular permissions are applied.
3. Set Workspace permissions (General, Integrations, Members, Projects, Billing).
4. Select project access.
5. For each selected project, set feature/settings permissions.

​

Edit permissions flow

Use the shield icon in the members table to open Edit permissions for an existing member.

​

What you can edit

• Role (Admin or Member).
• Workspace permission scopes.
• Project access selection.
• Per-project feature + settings permission scopes.

​

Permission scopes explained

The same 3 states are used across workspace and project permission rows:

​

Workspace-level permissions

These control access to organization settings sections:

• General: /settings/organization/general
• Integrations: project-level integration settings
• Members: /settings/organization/members
• Projects: /settings/organization/projects
• Billing: /settings/organization/billing

​

Project feature permissions

These control feature access inside selected projects.

​

Project settings permissions

These control access to project settings tabs:

​

Practical permission patterns

• Client reviewer: View only on reporting features, None on members/billing, limited project scope.
• SEO operator: Full on data/technical/workflows in assigned projects, None on billing.
• Organization admin: Admin role when they need global control.

​

Quick weekly checklist

1. Resolve stale pending invites.
2. Audit members with broad Full scopes.
3. Remove access for users no longer on account.
4. Re-check project assignment breadth for each member.

​

Keep in mind

• Organization members can have different scopes per project.
• Role and permission scopes interact: Admin bypasses granular restrictions.
• Seat limits can block new invites until capacity is increased.

​

Where to go next

• Organization Billing
• Organization Projects
• Project Members