Team Management

The Team Management page lets you manage all members of your organization. It's divided into two sections based on scope:

• Organization-scope members (top section) — Owner and Admin roles, who have access to all projects automatically
• Project-scope members (bottom section) — Project Manager, Developer, Member, and Viewer roles, who only see projects they've been assigned to

For a detailed explanation of what each role can and cannot do, see Roles & Permissions.

Organization-Scope Members

This section shows the Owner and Admins of your organization. They automatically see all projects and are not restricted by project budgets.

A resource counter in the section header shows how many admins you have relative to your plan limit (e.g., "2/5 Administrators").

Project-Scope Members

This section shows everyone else: Project Managers, Developers, Members, and Viewers. They only see projects they've been assigned to.

Status Indicators

Status indicators are shown on member avatars and described in Inviting a Member above.

Inviting a Member

1. Click the Invite Member button (top-right of the relevant section)
2. Enter the member's email address
3. Select the appropriate role
4. Click Send Invitation

An invitation email with a unique link is sent to the address. The invited person sets up their own account — no temporary password is needed.

INFO

For details on how invitations work from the recipient's perspective (new users, existing users, account setup), see Organizations — Inviting Members.

Member Status

After an invitation is sent, the member appears in the list with one of these statuses:

Status	Indicator	Description
Pending	Dimmed row	Invitation sent but not yet accepted
Active	Green dot	Member has accepted and has normal access
Suspended	Red dot	Access temporarily blocked by an admin

Pending members show a Resend Invite option in the actions menu. Suspended members are sorted to the bottom of the list.

Editing a Member

Click the edit action on any member row to modify their settings:

• Role: Change the member's role. Switching between organization-scope and project-scope roles adjusts their visibility accordingly.
• Projects (project-scope only): Add or remove project assignments. At least one project is required.

INFO

When you change a member's role, their session ends automatically. They'll log in again with updated permissions — no action needed on their part.

Suspending a Member

You can suspend members to temporarily block their access without removing them:

1. Click the actions menu on the member row
2. Select Suspend User
3. The member's status changes to suspended (red dot) and they lose access immediately

To reactivate, click Activate User from the same menu.

TIP

Suspension is useful for temporary access control — for example, when a contractor finishes a project phase but may return later. Their resources and data are preserved.

Member API Keys

You can view and manage API keys associated with each member:

1. Click the actions menu on a member row
2. Select API Keys
3. The dialog shows all API keys owned by that member, including:
   • Key name and partial key hint
   • Creation date and last used date
   • 30-day cost

From this dialog, you can create new API keys for the member or delete existing ones.

Removing a Member

1. Click the actions menu on the member row
2. Select Delete
3. Confirm the removal

WARNING

Removing a member revokes their access immediately and deletes all their API keys in this organization. Resources they created (agents, knowledge bases, etc.) remain in the organization and are accessible to other members.

Role Hierarchy

You can only remove members whose role is lower than yours. For example, an Admin can remove Developers and Viewers, but cannot remove another Admin or the Owner.

Resource Counters and Plan Limits

Both sections display resource counters that reflect your plan limits:

• Administrators: Current admin count vs. plan maximum
• Team per Project: Project-scope members vs. per-project limit

When a limit is reached, the Add Member button becomes disabled and a message explains how to upgrade your plan.

Best Practices

• Use project-scope roles by default — Only promote to Admin when full organization access is truly needed
• Use Project Manager for project leads — They can manage their project's team without needing organization-wide Admin access
• Assign specific projects — Don't add project-scope members to all projects; keep access focused
• Review regularly — Periodically audit the member list and remove inactive accounts
• Suspend instead of delete — When access should be temporary, suspend the member to preserve their data and simplify reactivation

Next Steps

• Roles & Permissions — Understand what each role can do
• Projects & Workspaces — Understand how projects organize resources
• Plan & Subscription — View and manage member limits