Skip to main content
Connect Trello to Oleria to see who can access each board in your organization, including board-only guests and anyone who can reach a public board. A single Oleria connection covers one Trello organization (workspace) - Oleria discovers every member, board, and role in that organization.

​
What Oleria discovers

​
Prerequisites

  • A Trello organization (workspace) you administer.
  • Your organization’s Organization ID - a 24-character hexadecimal Trello ID. Find it in Trello under Workspace settings -> the ID appears in the page URL or the workspace’s admin details.
  • For the API Key and Token method only: a Trello account with admin access to the organization, to generate a personal API key and token.
  • Optional, for member email addresses and two-step verification status: an Atlassian organization that your Trello members also belong to, and an Atlassian organization API key - unscoped, or scoped with read:directories:admin and read:accounts:admin.

​
Set up the integration

Trello supports two authentication methods. OAuth uses Oleria’s own registered Power-Up - there is nothing to register on your side, and access is revocable from Trello at any time. The API Key and Token method issues a long-lived credential tied to one Trello account. If OAuth doesn’t work in your environment, fall back to API Key and Token.
1

Find your Organization ID

In Trello, go to your workspace and open Workspace settings. Copy the Organization ID - a 24-character hexadecimal value. You need this regardless of which authentication method you use.
2

Generate an API key and token (API Key and Token method only)

If you’re using the API Key and Token method instead of OAuth, go to trello.com/app-key while signed in as an organization admin. Copy your API Key, then generate and copy a Token scoped to your account.
Skip this step if you’re using OAuth - Trello issues the credential automatically during the connect flow.
3

Create an Atlassian organization API key (optional)

Trello’s API never returns another member’s email address, so without this step Oleria knows only the email of the account that authorized the connection. If your Trello members also have accounts in an Atlassian organization (for example through Jira or Confluence), Oleria can look up their email addresses and two-step verification status there.In Atlassian Administration, select your organization, go to Settings -> API keys, and create an API key. An unscoped key works; if you create an API key with scopes, grant read:directories:admin and read:accounts:admin. Copy the Organization ID and the API key.
Oleria matches each Trello member to an Atlassian account by the member’s Atlassian account ID. Members who have no account in that Atlassian organization keep no email address.

​
Connect Trello to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations -> select Trello.
2

Complete the connection form

Under OAuth, selecting Connect redirects you to Trello (via Atlassian’s shared sign-in) to authorize Oleria against the organization you entered. Under API Key and Token, the connection is created directly.
3

Complete the connection

Oleria validates the connection and begins the first sync.

​
Verify the integration

Confirm Trello appears on the Connected tab of your Oleria Integrations page. After the first sync completes, you can review the discovered members, roles, boards, and access in your Oleria workspace.

​
Remediation actions

Oleria refuses to deactivate, or remove admin from, the Trello member whose credential the connection uses, because that would cut the connection off.

​
Known limitations

  • Oleria can’t grant roles. Trello’s API only lets an integration set a member to normal, so Oleria can remove the admin role but can’t grant admin or observer.
  • Member email addresses need the optional Atlassian key. Without it, only the email of the account that authorized the connection is known.
  • Enterprise-tier admins are not enumerated. If your organization sits under a Trello Enterprise, upper-tier Enterprise admins aren’t visible to this connection.
  • Card-content activity is excluded by design - comments and card edits aren’t access-control-relevant and aren’t collected.
  • Workspace-visible board access is shown as read-only. Trello doesn’t report the default permission level for boards visible to the whole workspace, so Oleria shows workspace members’ access to these boards as read-only.

​
Contact us

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