Getting StartedRoles and access

Roles and access

Admin vs viewer roles, invite-only access, and what each role can do across Atlas.

Invite-only workspace

Settings Team Members section for inviting admins and viewers
Settings Team Members section for inviting admins and viewers

Atlas does not offer public self-signup. Every user must be added by an organization admin in Settings → Team Members before they can sign in.

Full write access across the organization.

  • Complete onboarding and submit assessments
  • Create and edit tasks, risks, policies, vendors, and evidence
  • Connect, sync, and disconnect Integrations
  • Invite and remove teammates; change roles
  • Rename the organization
  • View Audit Log

Who becomes admin

The first person to sign in to a new Atlas instance becomes the organization admin. That person should invite the rest of the team and assign additional admins if needed.

Add emails before login

In Settings → Team Members, add each teammate's work email and choose Admin or Viewer.

Same email at sign-in

Users must sign in with the exact email that was invited. A mismatch shows Account not set up yet.

Promote when ready

Promote trusted operators to Admin when they need to manage integrations or evidence.

Page-level permissions

AreaAdminViewer
Dashboard, Security 360, Executive ViewRead + write contextRead
Assessment submitYesNo
Roadmap / TasksEdit status, owners, evidenceRead
InventoryEdit manual rows; sync via integrationsRead
Frameworks & PoliciesEdit controls, policies, evidenceRead
AI GovernanceChange approval statusRead
Risk Register & TPRMCreate/edit risks and vendorsRead
IntegrationsConnect, sync, disconnectStatus only
Settings & Audit LogFullSettings read; audit log admin-only

Common access issues

Access is scoped to one organization. There are no per-project or per-team workspaces inside Atlas today.