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

# Overview

> Manage Enterprise Team members programmatically using OAuth 2.0 Client Credentials

<sup>Questions or issues? Contact us at [api-support@manus.ai](mailto:api-support@manus.ai).</sup>

# Team User Management (v1)

Lets enterprise tenant administrators **provision, update, and offboard team members** from external identity systems such as SailPoint, Okta, or custom integrations. v1 splits the surface across two endpoints families:

| Family                 | Path prefix                        | Purpose                                                                | Auth                                               |
| ---------------------- | ---------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------- |
| Credential management  | `/team.v1.TeamManagementService/*` | Create / list / delete API credentials (`client_id` + `client_secret`) | Browser session token (Bearer)                     |
| User management (REST) | `/api/user/manage/v1/*`            | OAuth token + CRUD on team members                                     | OAuth 2.0 Client Credentials access token (Bearer) |

<Tip>
  v2 of this API ([User Management v2](/enterprise/v2/user-management-overview)) consolidates everything behind a single `X-API-Key` and adds the **Profile Migration** workflow (delegate / reclaim / rename). Prefer v2 for new integrations. Already on v1? See [Migrating from v1](/enterprise/v2/user-management-migration) for the field/enum/auth diff and a step-by-step cutover.
</Tip>

## Endpoints

### Credential management (RPC, session token)

<CardGroup cols={3}>
  <Card title="Create credential" icon="key" href="/enterprise/v1/team.credential.create">
    Issue a `client_id` + `client_secret` pair for an integration
  </Card>

  <Card title="List credentials" icon="list" href="/enterprise/v1/team.credential.list">
    Inspect existing credentials and last-used timestamps
  </Card>

  <Card title="Delete credential" icon="trash" href="/enterprise/v1/team.credential.delete">
    Permanently revoke a credential
  </Card>
</CardGroup>

### User management (REST, OAuth access token)

<CardGroup cols={2}>
  <Card title="Obtain access token" icon="lock" href="/enterprise/v1/oauth.token">
    Exchange `client_id` + `client_secret` for a 1-hour Bearer token
  </Card>

  <Card title="List users" icon="users" href="/enterprise/v1/users.list">
    Page through team members with offset-based pagination
  </Card>

  <Card title="Get user" icon="user" href="/enterprise/v1/users.detail">
    Look up a single team member by email
  </Card>

  <Card title="Create user" icon="user-plus" href="/enterprise/v1/users.create">
    Add a new member; auto-creates the personal account if needed
  </Card>

  <Card title="Update user" icon="user-pen" href="/enterprise/v1/users.update">
    Change a member's status (`active` / `inactive`) and/or role
  </Card>
</CardGroup>

## Quickstart

See [Quickstart](/enterprise/v1/user-management-quickstart) for an end-to-end SailPoint-style flow: create a credential, mint an access token, list members.

## Operational notes

* **Token caching:** Cache the access token and reuse it for the full hour. Re-mint only when expired.
* **Pagination:** `limit` defaults to 100 and is capped at 1000.
* **URL encoding:** Always URL-encode emails in path parameters (`john.doe%40example.com`).
* **Roles:** `owner` is read-only via API. `admin`, `member`, and `super_admin` can be set on create/update.
* **Audit logging:** All operations are logged for security review, including the body of create/update calls (with `client_secret` redacted).