Inviting your team

Bring teammates into your CloudQuell organization by inviting them by email. Admins and super_admins can send invites; the person you invite gets an email with a one-click link and joins once they accept.

Sending an invite

Invite someone by email and choose the role they’ll start with. Invited users default to the Contributor role unless you pick another one. Admins can invite at the viewer or contributor role; only a super_admin can invite someone as admin or super_admin.

You can also send an invite through the MCP server with the send_invite tool: it takes the person’s email, an optional role, and an optional message. Like every write tool, it requires the admin:write scope and confirm: true — an agent with the default read-only connection can’t invite anyone.

Note

A pending invite reserves a seat. Both current members and outstanding invites count toward your plan’s seat cap, so sending an invite holds a seat right away — you can’t invite more people than you have seats left, even before anyone accepts. For example, on Free (2 seats) an organization with 1 member can have 1 pending invite; the next invite is blocked until a seat frees up. If you’re at your cap, cancel a pending invite, remove a member, or upgrade before inviting. See Seats & limits.

Accepting an invite

The invited person receives an email with a one-click link. When they follow it and sign in with that email address, they’re added to the organization immediately and appear in the roster with the role you assigned.

One email address can belong to several CloudQuell organizations, with a different role in each — so someone can accept your invite even if they already use CloudQuell elsewhere. They switch between organizations with the org picker.

Canceling a pending invite

If you invited the wrong address or no longer need to add someone, revoke the invitation before it’s accepted. Once canceled, the invite link can no longer be used.

Over MCP this is the cancel_invite tool — pass the invite_id and confirm: true. It’s a destructive write, so it also requires the admin:write scope.

Roles and permissions

The role you assign controls what a new teammate can see and change. Review the four roles in Roles & permissions before inviting, and grant the least privilege that fits.