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 Organization access for workspace settings (General, Integrations, Members, Projects, Billing).
4. Select project access.
5. For each selected project, set feature/settings permissions.

​

Start with a permission preset

In Organization access, choose No access, Viewer, Billing manager, or Full access. Use Custom for a tailored combination. These presets apply to organization settings; they do not assign project access. For each selected project, choose Guest, Viewer, Editor, Content writer, Project admin, or No access, then adjust individual permissions if needed. Guest grants view access to Google search, AI search, and Attribution. Custom reflects a tailored combination. Applying a preset replaces that section’s permissions, so review the final scopes before sending the invitation. An Admin role grants full workspace and project access; presets do not restrict an administrator. Use Member when you need granular limits.

​

Accept or decline an invitation

Sign in with the invited email address and open the workspace. If the invitation is still pending, Atomic shows Join followed by the workspace name. Project pages remain unavailable until you accept.

• Select Accept invitation to join. Atomic returns you to Home, where you can open your assigned projects.
• Select Decline to reject the invitation. You return to Home; if you have no accessible workspace, the app opens the join flow.
• If the response fails, the invitation stays on screen with an error. Try again when the connection is available.

Accepting an invitation does not grant access beyond the role and project permissions assigned by the workspace administrator. If you cannot find an expected project after accepting, ask an administrator to check your project access.

​

Edit permissions flow

Use the Edit permissions action in the members table to change an existing member. The action uses a pencil icon.

​

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.

​

Allow a client to review social posts

For the intended project, give the reviewer View only access to Workflows and Full access to Social post approval. This lets them inspect saved posts and approve or request changes without granting draft-editing access. Draft authors need Full access to Workflows; that permission alone does not grant social-post approval. Admins bypass granular restrictions. Approval applies to the current draft revision and does not publish or schedule it. See Social post review states before granting access. Keep integrations, members, and billing permissions limited to the person’s actual responsibilities.

​

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