Skip to main content
You add people to an organization by sending an invitation to their email address with a role attached. When they accept and sign in, they join with exactly the role you chose. Managing invitations is an Owner responsibility.

How someone joins

1

The Owner sends an invite

From the members screen, the Owner enters the person’s email address and picks a role. AutoSage emails them an invitation with an accept link.
2

They open the accept link

The invited person receives the email and clicks the link to accept.
3

They sign in — or sign up

They sign in with that email address, or create an account if they don’t have one yet, using the same email the invitation was sent to.
4

They're added with the assigned role

Once signed in, they join the organization with the role from the invitation and can get to work.
The email a person signs in with must match the address the invitation was sent to. If they use a different email, ask the Owner to send a fresh invitation to the address they’ll actually sign in with.

Good to know

An unused invitation expires 7 days after it’s sent. If it lapses, the Owner can simply send a new one.
Because an organization has a single owner, invitations use the Billing admin, Developer, and Viewer roles. To hand over ownership, transfer it from the members screen — see Members & roles.
Inviting someone who already has a pending invitation, or who is already a member, is handled gracefully — you won’t create conflicting entries or duplicate access.
The Owner can revoke a pending invitation at any time before it’s accepted. Once revoked, its accept link no longer works.
Invite each person with the least-privileged role that fits what they need to do — Viewer or Developer is right for most people. You can always raise a member’s role later from the members screen.

Next steps

Members & roles

See what each role can do before you invite.

Teams overview

How organizations, environments, and tenants fit together.

Core concepts

How knowledge bases, agents, chat, and memory relate.

Tenancy for developers

The API-level view of environments and tenants.