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

# Coda

> Connect your Coda Enterprise organization to Oleria for visibility into users, workspaces, groups, roles, API tokens, and audit log activity, and to manage workspace access.

Coda (now Superhuman Docs) is a collaborative docs platform. Connect your Coda Enterprise organization to Oleria to see who has access across it: every user, the workspaces and groups they belong to, the role they hold in each workspace, the API tokens they've created, and what they've done recently. Oleria reads this data from the Coda Admin API.

## What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your Coda organization:

* **Accounts** - every user in your organization's domains, active and deactivated, with email, workspace roles, license level, and last activity. Workspace members from outside your organization's domains appear as external accounts.
* **Groups** - Coda workspaces and the groups provisioned from your identity provider, with their members.
* **Roles** - an **Admin**, **Doc Maker**, and **Editor** role for each workspace, and an **Organization Admin** role, with the accounts that hold each one.
* **Non-human identities** - API tokens created by your users, with their owner, creation date, and last use.
* **Activity** - events from the Coda audit log, such as sign-ins, role and permission changes, and API token changes.

Oleria uses this data for dormant account detection, access reviews, and non-human identity discovery, refreshed on Oleria's [regular sync schedule](/integrations/overview#sync-model).

<Note>
  This integration doesn't read docs, folders, or doc sharing, so it doesn't populate resource-level Access Graph or Access Inventory data. Coda's API doesn't list organization admins, so the **Organization Admin** role shows only the admin whose API token you connect. Coda doesn't expose MFA or SSO settings, custom agents, or Pack connections through its API. Oleria reads at most the last 12 months of Coda audit log activity.
</Note>

## Prerequisites

* A Coda organization on the **Enterprise** plan. Coda's Admin API, and the workspace and user data this integration reads, aren't available to workspaces outside an Enterprise organization.
* A Coda **organization admin** to create the API token below.
* Admin access on the Oleria platform to add a new integration.

<Note>
  The exact location of these settings can change over time. If the steps below don't match what you see, refer to Coda's own API documentation.
</Note>

## Create a Coda API token

Oleria connects with an API token created by one of your organization admins. The token acts with that admin's permissions.

<Steps>
  <Step title="Open your account settings">
    Sign in to Coda as an organization admin and open **Account settings**.
  </Step>

  <Step title="Generate the token">
    Under **API settings**, select **Generate API token**. Give it a name such as `Oleria`.

    <Warning>
      Don't restrict the token to specific docs or tables. A restricted token can't use the Admin API, and Oleria rejects it when you connect.
    </Warning>
  </Step>

  <Step title="Copy the token">
    Copy the token. Coda shows it only once, so store it securely until you've finished connecting.
  </Step>
</Steps>

<Tip>
  Create the token from a dedicated admin account if you can. Oleria won't deactivate the admin whose token it uses, or revoke that token, because either action would disconnect the integration.
</Tip>

## Find your organization ID (optional)

You only need an organization ID if the admin who created the token administers more than one Coda organization. Otherwise, Oleria finds the organization automatically.

If you need it and don't know it, select **Authenticate** with the field blank. Oleria's error message lists each organization the token can administer with its ID, for example `org-1AbcdeFgh1 (Acme Corp)`. Copy the one you want into **Organization ID**.

## Connect Coda to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations**, then select the **Coda** tile.
  </Step>

  <Step title="Complete the connection form">
    Fill in the connection form:

    | Field | Notes |
    | :- | :- |
    | API Token | Required. The token you created in [Create a Coda API token](#create-a-coda-api-token). |
    | Organization ID | Optional. Only needed if the token's owner administers more than one Coda organization. |
  </Step>

  <Step title="Save the integration">
    Select **Authenticate**. Oleria checks that the token is unrestricted, that its owner is an organization admin, and that it can read users, workspaces, groups, and API tokens, then saves the integration.
  </Step>
</Steps>

## Verify the integration

Confirm the new instance appears on the **Connected** tab of your Oleria **Integrations** page with a status of **Healthy**. Oleria syncs users, workspaces, groups, roles, API tokens, and activity from Coda on its [regular sync schedule](/integrations/overview#sync-model) once the initial sync completes.

<Note>
  To rotate the API token, edit the integration and enter the new token. Leave the field blank to keep the token already stored. The organization ID can't be changed after you connect; to connect a different organization, add a new integration.
</Note>

## Remediation actions

Beyond discovery, Oleria can act on Coda access to remediate risk. Every action uses the organization admin permissions of the connected API token.

| Action | What it does | Revert |
| :- | :- | :- |
| Disable user accounts | Deactivates the user in Coda. Works even when SCIM provisioning is turned on. Not available for external accounts or for the admin whose token is connected. | Supported - reactivates the user. |
| Enable user accounts | Reactivates a deactivated user. | Supported - deactivates the user again. |
| Add user to group | Adds the user to a Coda workspace as an **Editor**. If they're already a member, nothing changes. | Supported - removes the user from the workspace. |
| Remove user from group | Removes the user from a Coda workspace. They keep their Coda account and access to other workspaces. | Supported - re-adds the user with their previous workspace role. |
| Add user to role | Gives a workspace member the selected workspace role. A user who already holds that role or a higher one keeps it. | Supported - restores the previous role. |
| Remove user from role | Moves the user down one level in that workspace: **Admin** to **Doc Maker**, or **Doc Maker** to **Editor**. To remove an **Editor**, remove the user from the workspace instead. | Supported - restores the previous role. |
| Disable NHI accounts | Revokes an API token. Oleria won't revoke the token the integration itself uses. | Not supported - a revoked token can't be restored, so its owner creates a new one. |

<Note>
  Groups provisioned from your identity provider can't be changed through Coda, so add or remove those members in your identity provider. The **Organization Admin** role has no Coda API for changes, so Oleria shows it but can't assign or remove it.
</Note>

<Warning>
  If your identity provider still assigns a user that Oleria deactivates, it may reactivate them on its next SCIM sync. Deprovision the user in your identity provider too.
</Warning>

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.