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.
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.
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.
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.
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.1
Open your account settings
Sign in to Coda as an organization admin and open Account settings.
2
Generate the token
Go to API connections and, under API tokens, create a new API token. In New API token, set:
- Name: a name such as
Oleria. - Permission: Read and write, which Oleria’s remediation actions need. Coda selects Read only by default.
- Scopes: add your organization. Coda lists it with the other resources you can add, such as Packs and the Docs MCP, and shows it only to Enterprise organization admins.
3
Copy the token
Your new token appears at the top of the list. Select Copy token right away, since you may not be able to see it again, and store the token securely until you’ve finished connecting.
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 exampleorg-1AbcdeFgh1 (Acme Corp). Copy the one you want into Organization ID.
Connect Coda to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the Coda tile.
2
Complete the connection form
Fill in the connection form:
3
Save the integration
Select Authenticate. Oleria checks that the token can read your organization’s users, workspaces, groups, and API tokens, and that its owner is an organization admin, then saves the integration.
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 once the initial sync completes.To rotate the API token, edit the integration and enter a new token created the same way, with Permission set to Read and write and your organization under Scopes. 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.
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, and needs a token whose Permission is Read and write. Coda doesn’t tell Oleria a token’s Permission, so with a Read only token the actions are still listed, but Coda refuses them when they run and Oleria reports the likely cause.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.

