Team membership is how Atmos Pro decides who can review plans, approve changes, and act on workflow alerts in a workspace. Anyone who pushes code to a connected repository is visible to Atmos Pro as a committer, but only people who have been invited and accepted are members — and only members can take action inside the app.

Three concepts to keep straight:

Seats determine whose commits Atmos Pro acts on. Only commits authored by seat-assigned members trigger workflow runs, drift detection, and plan reviews — commits from committers who haven't been invited are still visible in the workspace, but they don't drive any processing. Bot commits are exempt from this rule and are always processed. This is the economic link between seats and your plan: your seat count is the cap on how many human committers Atmos Pro will act on.

When Atmos Pro detects committers on your repos who aren't yet members, it surfaces them in the workspace Recommendations panel as a nudge to invite them. The recommendation clears automatically once they're invited or excluded.

Every member has one of three workspace roles:

Workspace roles control what someone can do in Atmos Pro. They are separate from repository permissions, which control which workflows, branches, and environments are authorized to interact with the workspace. See Repository Permissions for the per-repo authorization model.

Owners and Admins can invite teammates from the Team page in workspace settings.

Invitations are delivered by email and are GitHub-authenticated — the invitee signs in with GitHub, and the email on their GitHub account must match the address you invited. This match acts as a second factor: someone who intercepts an invitation link cannot accept it unless their GitHub account already controls the invited email. There are no separate passwords to manage.

Pending invitations remain valid until accepted, revoked, or expired. You can resend or cancel them from the Team page.

Owners and Admins can change a member's role at any time from the Team page. Promotions and demotions take effect immediately on the member's next page load. A workspace must retain at least one Owner — the last Owner cannot demote themselves until another Owner is in place.

To remove a teammate, open the Team page, find the member, and choose Remove. Removing a member:

A removed member can be re-invited later. If they were the last Owner, you must promote another member to Owner first.

The "Invite N committers to Atmos Pro" recommendation appears whenever Atmos Pro sees commits from users on connected repos who aren't yet members. The card lists who they are, links to the Team page so you can invite them, and disappears once everyone listed has been invited or excluded. It's a low-priority suggestion, not a warning — you can ignore it indefinitely if those committers shouldn't have access to the app itself.