Teams and permissions
Atlas orgs have teams inside them. Envelopes and templates belong to a team. Members see only their assigned teams unless they are org admins.
Admin vs member
| Admin | Member | |
|---|---|---|
| Sees | All teams in the org | Assigned teams only |
| Can send | Yes, on any team | On assigned teams |
| Can invite | Yes | No |
| Can create teams | Yes | No |
| Audit log | Yes | No |
Invite a teammate
- Team → Members (admins only).
- Enter email, first name, last name, role, and team assignments.
- Atlas sends an invite email.
- They sign up or log in, accept, and land on the dashboard.
You can change role and teams later on the members page.
Teams and visibility
- Create teams under Team → Teams (Sales, Legal, General).
- Assign each member to one or more teams.
- New envelopes land on the member's default team.
Admins see all teams. Members cannot read other teams' envelopes.
Teams vs connected accounts
| Concept | Who uses it |
|---|---|
| Team | People at one company sharing a dashboard |
| Connected account | Platform partners provisioning separate client orgs via API |
A connected account can have its own teams. Platform partners usually start with one General team per client.
Domain auto-join and SSO
- Domain auto-join: claim your email domain under Team → Settings so matching signups can join automatically.
- SSO: optional SAML for dashboard users. Password login still works outside SSO domains.
Delete a team
Admins delete teams from Team → Teams. Members on that team move to General. Envelopes stay on the team they were created on.
API team scoping
When a user belongs to multiple teams, pass team_id on create. Omit it when the account has a single team.