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

# 15Five

## After this article

You will be able to connect 15Five to Lumos to sync users, their roles, and last-login activity, and to suspend 15Five users during offboarding and Access Reviews.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| :- | :- | :- | :- | :- |
| Users | Account | Yes | Yes | User accounts. Provisioning is limited to suspending users |
| Roles | Permission | Yes | No | Whether the user is a Reporter, Reviewer, or Company Admin |
| Last Login | Account data | Yes | No | Last time the user logged into 15Five |

| AppStore | Offboarding | Access Reviews | License Management |
| :- | :- | :- | :- |
| No | Yes | Yes | Yes |

| Deprovisioning Action | Type | Description |
| :- | :- | :- |
| Suspend | User | Marks the account **Suspended** in Lumos. In 15Five the user is deactivated (login prevented) and the license is reclaimed |

**Status mapping:**

* `active` → Lumos **Active**,
* `inactive` → **Suspended**,
* User no longer returned by 15Five (deleted) → **Deprovisioned**.

## Required plan and roles

* **15Five plan:** the **Perform** or **Total Platform** plan is required, and **SCIM must be enabled** in your 15Five account.
* **15Five role:** your 15Five user must be an **Account admin** to connect.
* **Permission scoping:** the connection authenticates with the SCIM Access token generated in 15Five. Lumos reads users, roles, and last login, and can also **suspend** users (set `is_active` to false). There is no narrower read-only token option documented.

## Read-only access vs provisioning

**Is read-only possible?** No. 15Five uses a single SCIM Access token for the connection, and that token grants Lumos both read access (users, roles, last login) and write access (suspending users) together. 15Five does not document a narrower read-only token.

**What full provisioning requires.** The same SCIM Access token, generated in 15Five by an Account admin on the Perform or Total Platform plan with SCIM enabled. Follow the steps below to connect. Provisioning here is limited to suspending a user account.

**Watch out for.** Because read and write share one token, you cannot scope this connection down to read-only by choosing a different credential. Suspending a user in Lumos deactivates them in 15Five and reclaims the license, but does not delete the account, and there is no separate reactivate action documented.

## Instructions

**Phase 1: Get the SCIM token from 15Five**

1. Confirm SCIM has been enabled in your 15Five account (Account admin required).
2. Copy and temporarily save the SCIM Access token generated in 15Five.

**Phase 2: Connect in Lumos**

1. Find the 15Five 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-15five-1`) and enter it in the **App Instance Identifier** field.
3. Paste the SCIM token from 15Five into the **API Key** field.
4. Click **Connect**.

## 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.** Confirm your account is on the Perform or Total Platform plan, SCIM is enabled in 15Five, and the token was generated by an Account admin. Regenerate the SCIM token and reconnect if in doubt.

**A user shows as Deprovisioned in Lumos but you never suspended them.** Lumos marks a user Deprovisioned when 15Five no longer returns their account, i.e. the user was deleted in 15Five. Deleted users disappear from the API, while suspended users remain with `inactive` status.

**Suspend action available but user still appears active in 15Five.** Suspension is applied via the 15Five public API (`is_active: false`). Verify the SCIM token still belongs to an active Account admin and retry the action.