Manage your team

Invite members, assign seats, enroll agents, and inspect per-member usage.

Use Team → Members to manage people and their agent access. Start with the team rollout if you are onboarding an organization.

Local demonstration with fictional members and illustrative usage data.

Invite and give access

1. Click Invite member, enter their email, and choose a role.
2. Have them accept the invitation with the same email.
3. Assign an available seat. Use Manage seats to purchase more seats for your team.
4. Use Set up coding agent on their row, or have them follow the CLI quickstart.
5. Have them launch an agent and make a model request. Check that usage appears under the expected member.

Roles and access

Choose a role when inviting a member. Use the member row’s Manage menu to change it later.

Role	Access
Admin	Manage organization settings, members, billing, provider keys, integrations, and plugins
Member	Use agents and the usage views and controls available to that member
Read-only	View permitted information without administrative editing; Strategies is unavailable

Roles control permissions. Seats give members access to paid agent features; assigning a seat does not grant administrator permissions. Access to request payloads also depends on the feature’s permissions.

Organization and squad settings can still enforce an agent’s configuration. See Organization.

Read the member table

Choose a time range before comparing members. The table shows agents, squad, spending limit, cost, requests, tokens, savings, activity, and seat status. Sort the available metric columns to find the largest consumers.

A member with no recent request can have a seat and configured credentials without showing usage for the selected period. Check Sessions and widen the time range before re-enrolling them.

Manage a member or agent

Use the member row’s Manage menu for membership and role actions. Click an enrolled agent’s badge to open its agent settings for compression, routing, BYOK, or Debug. An organization or squad can enforce a setting; a disabled control does not necessarily indicate an error. See Gateway settings.

Use Set limit for a hard spending limit. To change models as spending grows, use a routing strategy. A scope with an assigned strategy cannot also carry a hard usage limit; use the strategy’s Block at 100% behavior when appropriate.

Local demonstration with fictional data.

Organize and offboard

• Use Squads to group members and apply shared settings. See Squads.
• Review a member’s seat before revoking it; seat access and organization membership are separate.
• When offboarding, remove organization access and revoke credentials that should stop working. Also review any shared application or provider credentials.

Verify a rollout

Open one pilot member’s session, check the served model and provider in its request ledger, then compare the member’s costs with the same period in Team. For repository and PR attribution, connect GitHub and attach session metadata.