Skip to main content
Connect monday.com to Oleria to gain continuous visibility into who has access to your monday.com account and what they can do. Oleria reads identity, membership, and audit data from the monday.com API. It maps every user, team, role, and non-human identity in one place, so you can find dormant or over-privileged access and act on it directly from Oleria.

​
What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your monday.com account:
  • Accounts - every user, whether active, deactivated, or invited but not yet joined. That includes admins, members, viewers, guests, and portal users. Non-human identities appear as their own accounts:
    • Service users - API-only accounts, along with when their token was last used and who created them.
    • AI agents - agent users in your account.
    • Platform API users - accounts that monday.com itself creates and uses internally.
  • Teams - all teams and their members, including guest teams, and each team’s owners.
  • Departments - on Enterprise plans, each department with its members and owners.
  • Roles - the four built-in account roles (Admin, Member, Viewer, Guest) and any custom roles on Enterprise plans, with each user’s assigned role.
  • Service-user API tokens - whether each service user has an active API token. Oleria never reads the token value itself.
  • Audit activity - account audit log events such as logins, role changes, deactivations, team changes, and data exports, attributed to the user who performed them. The audit log is available on Enterprise plans only.
Oleria refreshes this data on its regular sync schedule.

​
Prerequisites

  • A monday.com account admin to generate the API token. The token carries its owner’s permissions, and Oleria is supported with an admin’s token:
    • Remediation actions and the audit log require an admin’s token.
    • The audit log also requires an Enterprise plan.
  • Admin access on the Oleria platform to add a new integration.
Generate the token from a dedicated admin account that isn’t tied to an employee, so the integration keeps working if that person leaves or loses admin rights. This account takes a paid monday.com seat.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to monday.com’s API authentication documentation.

​
Connect monday.com to Oleria

1

Copy an API token from monday.com

Sign in to monday.com as the dedicated admin account. Select your profile picture, go to Developers -> My access tokens, select Show, and copy your API token.Admins can also find personal API tokens under Administration -> Connections -> API.
Treat the token like a password. Anyone who has it can act in monday.com with the permissions of the account that owns it.
2

Find monday.com in Oleria

Go to your Oleria workspace, select Integrations, select the Available tab, and search for Monday.com.
3

Connect in Oleria

Select the Monday.com card, paste the token into API token, then select Authenticate. Oleria checks the token against monday.com before saving the integration.

​
Verify the integration

Confirm the new instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, you can review the discovered accounts, teams, roles, and activity in your Oleria workspace.
If you regenerate the API token in monday.com, the old token stops working. Update the integration in Oleria with the new token by editing the integration.

​
Remediation actions

Beyond discovery, Oleria can act on monday.com access to remediate risk. All remediation actions require the token to belong to a monday.com account admin. Oleria checks this before running any action.
A token from a non-admin account can still connect, but every remediation action fails validation.
A few safeguards apply to every action:
  • Oleria won’t deactivate the account that owns the integration’s token, change its role, or revoke its own service-user token. Doing so would disconnect the integration.
  • Team membership actions apply to teams only. Department membership is read-only.
  • A reversal only undoes the change Oleria made. If someone changed the same user in monday.com in the meantime, Oleria leaves it as is.

​
Upgrading from the previous monday.com integration

Earlier monday.com connections in Oleria used a SCIM-based setup. Existing connections switch to the new integration automatically and keep syncing when their saved token is a monday.com API token. If an existing connection reports an error asking you to reconnect, edit the integration in Oleria and enter a monday.com API token from the steps above. The token must come from the same monday.com account the integration was originally connected to. To connect a different account, add a new monday.com integration instead.

​
Known limitations

  • Boards, workspaces, and docs aren’t discovered. This integration covers identities, membership, roles, and activity, not access to individual boards or workspaces.
  • MFA and SSO status isn’t available. The monday.com API doesn’t expose two-factor or single sign-on settings, so Oleria reports these fields as unavailable, not as disabled.
  • Nested teams aren’t shown. monday.com doesn’t expose which teams contain other teams, so each team’s own members appear but the nesting doesn’t.
  • Audit activity, departments, and custom roles require an Enterprise plan. On other plans the audit log returns no events, so no activity appears in Oleria.
  • AI agents and platform API users can’t be deactivated from Oleria. monday.com offers no API to disable them. Only service users can be remediated, by revoking their tokens.
  • Installed apps aren’t discovered. monday.com doesn’t make app installations available to API tokens.

​
Contact us

For questions about this integration, contact us at support@oleria.com.