> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endprompt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Management

> Add team members and manage access roles

Collaborate with your team by adding members and assigning appropriate roles.

## Adding Team Members

<Steps>
  <Step title="Navigate to Team">
    Click your **profile avatar** in the top-right, then select **Team** from the dropdown.
  </Step>

  <Step title="Click Invite Member">
    Click the **Invite Member** button.
  </Step>

  <Step title="Enter Email">
    Enter the team member's email address.
  </Step>

  <Step title="Select Role">
    Choose an appropriate role (see roles below).
  </Step>

  <Step title="Send Invitation">
    Click **Send Invite**. They'll receive an email to join.
  </Step>
</Steps>

<Note>
  Team management is only available to Admin and Owner roles.
</Note>

## Roles and Permissions

| Permission              | Reader | Developer | Admin | Owner |
| ----------------------- | ------ | --------- | ----- | ----- |
| View endpoints          | ✅      | ✅         | ✅     | ✅     |
| View prompts            | ✅      | ✅         | ✅     | ✅     |
| View logs               | ✅      | ✅         | ✅     | ✅     |
| Create/edit endpoints   | ❌      | ✅         | ✅     | ✅     |
| Create/edit prompts     | ❌      | ✅         | ✅     | ✅     |
| Promote prompts to Live | ❌      | ✅         | ✅     | ✅     |
| Manage API keys         | ❌      | ❌         | ✅     | ✅     |
| Manage team members     | ❌      | ❌         | ✅     | ✅     |
| Manage billing          | ❌      | ❌         | ❌     | ✅     |
| Delete tenant           | ❌      | ❌         | ❌     | ✅     |

### Role Descriptions

<AccordionGroup>
  <Accordion title="Reader" icon="eye">
    **View-only access**

    Can view endpoints, prompts, and logs but cannot make changes. Ideal for stakeholders who need visibility without edit access.
  </Accordion>

  <Accordion title="Developer" icon="code">
    **Build and deploy**

    Can create and modify endpoints, prompts, and snippets. Can promote prompts to Live. Cannot manage team or billing.
  </Accordion>

  <Accordion title="Admin" icon="user-gear">
    **Full operational control**

    All Developer permissions plus team management and API key management. Cannot access billing.
  </Accordion>

  <Accordion title="Owner" icon="crown">
    **Complete control**

    Full access to everything including billing, subscription, and account deletion. Typically the account creator.
  </Accordion>
</AccordionGroup>

## Managing Existing Members

### Changing Roles

1. Go to **Team** (via the profile dropdown)
2. Find the team member
3. Click **⋯** → **Change Role**
4. Select the new role
5. Save

<Warning>
  Demoting an Admin to Developer removes their ability to manage team members and API keys immediately.
</Warning>

### Removing Members

1. Go to **Team** (via the profile dropdown)
2. Find the team member
3. Click **⋯** → **Remove**
4. Confirm removal

<Note>
  Removed members lose access immediately. Any API keys they created remain active until revoked.
</Note>

## Pending Invitations

View and manage pending invites:

* **Resend** — Send the invitation email again
* **Cancel** — Revoke the invitation before it's accepted

Invitations expire after 7 days.

## Best Practices

<CardGroup cols={2}>
  <Card title="Principle of Least Privilege" icon="shield-check">
    Assign the minimum role needed for each person's job
  </Card>

  <Card title="Use Descriptive API Key Names" icon="key">
    When multiple people create keys, include their name
  </Card>

  <Card title="Regular Audits" icon="magnifying-glass">
    Periodically review who has access and remove unused accounts
  </Card>

  <Card title="Document Ownership" icon="file-lines">
    Ensure more than one person has Admin/Owner access
  </Card>
</CardGroup>

## Common Scenarios

### Onboarding a New Developer

1. Invite with **Developer** role
2. Share relevant documentation
3. Have them create a personal API key for development
4. Add them to your internal communication channels

### External Contractor Access

1. Invite with **Developer** role
2. Set expectations about endpoint ownership
3. Plan to remove access when contract ends
4. Consider creating a separate API key for their work

### Stakeholder Visibility

1. Invite with **Reader** role
2. They can view dashboards and logs
3. Cannot accidentally modify configurations

## Transferring Ownership

To transfer account ownership:

1. Current Owner goes to **Team** (via the profile dropdown)
2. Find the new owner (must be Admin)
3. Click **⋯** → **Transfer Ownership**
4. Confirm the transfer

<Warning>
  Ownership transfer is permanent. The previous owner becomes an Admin.
</Warning>

## Next Steps

<CardGroup cols={2}>
  <Card title="Billing" icon="credit-card" href="/guides/billing">
    Manage your subscription
  </Card>

  <Card title="API Authentication" icon="key" href="/api/authentication">
    Set up API keys for your team
  </Card>
</CardGroup>