Skip to content
Gate

Teams and roles

Invite teammates and give each the right level of access. Roles are set per organization, so the same person can be an admin in one organization and a member in another.

Invite a teammate

Go to Team, click Invite member, enter an email address, and pick a role. They get an email with a link; when they sign in, or sign up if they are new to Gate, they join your organization with that role. You can invite someone who has not signed up yet: the invitation stays pending until they create an account, and you can review or revoke pending invitations on the same page.

Inviting and removing members is limited to owners and admins.

On the Pro plan you pay for a set number of seats. Both active members and pending invitations count against that number, so to invite someone you need a free seat. Inviting past your current seats adds one, prorated for the rest of the billing period. Removing a member frees the seat but does not lower your bill until the next renewal, and you can re-fill it before then at no extra charge. See Plans for how seats are billed.

Change a member’s role

Go to Team, open the member’s row, and choose a new role. The change applies right away. Only owners can change roles: admins can invite and remove people, but cannot promote or demote anyone.

The three roles

Each role can do everything the role below it can, plus more.

RoleWhat they can do
MemberUse the gateway and manage their own API keys and connections. The day-to-day role for building on Gate.
AdminEverything a member can do, plus invite and remove teammates, manage security policies and billing, and see the organization’s usage, activity, and audit trail. Cannot change roles or delete the organization.
OwnerEverything, plus change members’ roles, manage the plan, delete the organization, and transfer ownership.

Billing is owner and admin only: members have no billing access, and changing the plan or deleting the organization is owner-only.

Visibility

Owners and admins see the whole organization’s usage: the spend and token charts, the activity KPIs, and the top-users leaderboard. Members see only their own usage.

Individual request and response contents, conversations, and security events stay private to the member who made them. Even owners and admins cannot read another member’s prompts, replies, or flagged events. Organization-wide views show aggregate usage and cost, never the contents of other people’s requests.