> ## 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.

# Drift

## After this article

You will be able to connect the Drift integration to Lumos, understand how Lumos reads users and roles from Drift, and resolve common connection issues.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | Drift user accounts |
| Role | Permission | Yes | No | The user's role(s) in Drift |

| Deprovisioning Action | Type | Description |
| - | - | - |
| Deprovision | User | Deletes the user from your Drift tenant (following the SCIM protocol for deletes) and reclaims a license |

Deprovisioning is available for Offboarding, Access Reviews, and License Management. It is not available through the AppStore. In Lumos, deprovisioning marks the account status as Deprovisioned.

User status mapping:

| Drift user status | Lumos account status |
| - | - |
| active | Active |
| not active | Suspended |
| deleted (Drift no longer returns the user) | Deprovisioned |

## Required plan and roles

* **Drift plan:** you need the **Drift Premium** plan to connect this integration.
* **Drift role:** your Drift user must be an **Admin** to authorize the connection.

## Read-only access vs provisioning

**Is read-only possible?** No. All three OAuth scopes Lumos requests, including `user_write`, are required to connect.

**What full provisioning requires.** This connector's write capability is the SCIM-style Deprovision action, which deletes the user from your Drift tenant and reclaims their license Your Drift user must be an Admin on a Premium plan to authorize the connection.

**Watch out for.** Deprovisioning here follows the SCIM delete protocol, so the user is removed from your Drift tenant entirely rather than just being disabled. There's no partial or reversible suspend state. Deprovisioning is available through Offboarding, Access Reviews, and License Management, but not through the AppStore.

## Instructions

1. Find the Drift card in your Lumos integrations ([reconnect](https://app.lumosidentity.com/integrations?tab=connected) an existing card or [add a new one](https://app.lumosidentity.com/integrations?tab=can_integrate)).
2. Click **Connect Drift**.
3. Accept the requested scopes and complete the OAuth flow to connect the integration.

### Scopes

Lumos requests the following scopes over OAuth. More detail is in Drift's documentation.

| Scope | Required | Description |
| - | - | - |
| `user_read` | Yes | Read user data |
| `user_write` | Yes | Modify user data |
| `account_read` | Yes | Read account data |

## 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

**Can't connect the integration.** Confirm your Drift account is on the Premium plan and that the user authorizing the OAuth flow is a Drift Admin. All three scopes (`user_read`, `user_write`, `account_read`) must be accepted.

**A deprovisioned user is gone from Drift entirely.** That is expected. Deprovisioning follows the SCIM delete protocol, which removes the user from your Drift tenant and reclaims the license.