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

# Amplitude

## After this article

You will be able to connect Amplitude to Lumos to sync Amplitude users and their statuses, and to deprovision users from Lumos during offboarding, Access Reviews, and license management.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| :- | :- | :- | :- | :- |
| Users | Account | Yes | Yes | User accounts, with deprovisioning supported (see below) |

| Deprovisioning Action | Type | Description |
| :- | :- | :- |
| Delete | User | Fully deletes the user's Amplitude account and reclaims a license. For pending users, revokes the invitation |

**Status mapping:**

* Amplitude `active` → Lumos **Active**.
* `inactive` → **Deprovisioned**.
* Deleted (Amplitude no longer returns the user) → **Deprovisioned**. Lumos reads the SCIM `active` field to determine status.

## Required plan and roles

* **Amplitude plan:** the **Enterprise** plan is required to connect this integration.
* **Amplitude role:** your Amplitude user must be an **Admin** to connect.
* **Prerequisites:** the **User Management API** must be enabled on your Amplitude account and you need access to **SCIM provisioning**. Contact your Amplitude Customer Success Manager if either is not enabled, then follow Amplitude's documentation to enable SCIM on your account.
* **Permission scoping:** the SCIM token grants both read (list users) and write (delete users) access, and there is no read-only token variant. Lumos uses the write access only when you trigger a deprovision.

## Read-only access vs provisioning

**Is read-only possible?** No. The connection authenticates with a single SCIM token, and that token grants Lumos both read access (listing users) and write access (deleting users) together. Amplitude does not document a narrower read-only token.

**What full provisioning requires.** A SCIM token generated in Amplitude by an Admin on the Enterprise plan, with the User Management API and SCIM provisioning enabled (your Amplitude Customer Success Manager can enable these if they aren't already). Follow the steps below. Provisioning here is a single Delete action, which fully removes the user (or revokes a pending invite) and reclaims the license.

**Watch out for.** Because one token carries both permissions, you cannot connect Amplitude read-only by choosing a different credential. There is no separate deactivate or suspend action, Delete is the only deprovisioning action and it is not reversible from Lumos.

## Instructions

**Phase 1: Generate a SCIM token in Amplitude**

1. With the User Management API and SCIM provisioning enabled on your account, generate a **SCIM token** following Amplitude's instructions.
2. Copy the token.

**Phase 2: Connect in Lumos**

1. Find the Amplitude card in your Lumos integrations (reconnect an existing card or add a new one).
2. Choose a unique identifier for the integration (e.g. `lumos-amplitude-1`) and enter it in the **App Instance Identifier** field.
3. Paste the SCIM token into the **API Key** field.
4. Click **Connect Amplitude**.

## API Endpoints Used

<Note>
  The API endpoints this integration uses are available to logged-in Lumos customers. [Log in](/login) to view them.
</Note>

## Troubleshooting

**Connection fails with a valid-looking token**. Confirm the User Management API and SCIM provisioning are enabled on your Amplitude account. Both may require your Amplitude Customer Success Manager to activate them.

**A user shows as Deprovisioned but still exists in Amplitude**. Users marked `inactive` in Amplitude map to **Deprovisioned** in Lumos, the same as deleted users.

**Deprovisioned a pending user**. If the user had not accepted their invite, the deprovision revoked the invitation rather than deleting an active account. Either way the license is reclaimed.