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

# Coda

## After this article

You will be able to connect Coda to Lumos to sync organization users and to suspend or permanently remove users in Coda for offboarding, Access Reviews, and license management.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | Organization users. Lumos can suspend and deprovision (no account creation) |

User status mapping: Coda `active` → Lumos **Active**. Coda `inactive` → Lumos **Suspended**. User deleted (Coda no longer returns the user) → Lumos **Deprovisioned**.

| Deprovisioning Action | Type | Description |
| - | - | - |
| Suspend | User | Deactivates the user in Coda, preventing login and reclaiming a license. Lumos status becomes Suspended. Available in Offboarding, Access Reviews, and License Management (not AppStore) |
| Deprovision | User | Permanently removes the user from Coda and reclaims a license. Lumos status becomes Deprovisioned. Available in Offboarding, Access Reviews, and License Management (not AppStore) |

## Required plan and roles

* **Coda plan:** your organization must be on the **Coda Enterprise** plan.
* **Coda role:** your Coda user must be an **Org Admin**.
* **Prerequisites:** both **SSO** and **SCIM** must be enabled in Coda before connecting.
* **Authentication:** a Coda SCIM bearer token. The token grants Lumos the access it needs to list users and to deactivate/remove them. Lumos requires this write access for its suspend and deprovision actions, and there is no read-only variant documented.

## Read-only access vs provisioning

**Is read-only possible?** No. Coda authenticates with a single SCIM bearer token, and that token is the same credential Lumos uses for its suspend and deprovision actions. No narrower, read-only token is documented for this connector.

**What full provisioning requires.** SSO and SCIM both enabled in your Coda organization (Coda Enterprise plan), an Org Admin to generate the SCIM bearer token, and the Org ID copied from the SCIM Base URL.

**Watch out for.** Because there is only one token type, you cannot scope a connection down to sync-only. Enabling SCIM is a prerequisite you must complete in Coda before a token can even be generated, and that in turn depends on SSO already being enabled.

## Instructions

**Phase 1: Enable SCIM and generate a token in Coda**

1. Enable SSO in Coda if it isn't already.
2. Log into the Coda admin portal.
3. Enable SCIM in Coda if it isn't already.
4. After enabling SCIM, generate a **SCIM bearer token** and save it.
5. Note the **SCIM Base URL** and copy the Org ID from it. For example, if the SCIM Base URL is `https://coda.io/scim/v2/organizations/org-12345`, the Org ID is `org-12345`.

**Phase 2: Connect in Lumos**

1. Find the Coda card in your Lumos integrations (reconnect an existing card or add a new one).
2. Enter the Coda SCIM bearer token in the **API Key** field.
3. Enter the Coda Org ID in the **Org/Tenant Id** field.
4. Click **Connect Coda**.

## 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 SSO and SCIM are both enabled in Coda. The SCIM bearer token can only be generated after SCIM is enabled, and the token must be paired with the correct Org ID from the SCIM Base URL.

**Wrong Org ID format**. The **Org/Tenant Id** field takes only the `org-` prefixed identifier from the SCIM Base URL (e.g. `org-12345`), not the full URL.