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

# Intercom Integration

Oleria provides identity security and access management teams with visibility and intelligence into who has access to what, where they got that access, how they use it, and whether they should even have it. As part of that promise, we integrate your Intercom workspace into the Oleria platform. Follow these steps to integrate Intercom with your Oleria workspace.

## Prerequisites

1. Administrator permission on the Oleria workspace
2. Access to your Intercom workspace's **Developer Hub**

<Warning>Oleria's Intercom integration supports workspaces on Intercom's US data region only. EU and Australia region workspaces aren't supported - connecting one fails at authentication.</Warning>

## Create a Private App Access Token in Intercom

<Steps>
  <Step title="Open the Developer Hub">
    Sign in to Intercom and go to the **Developer Hub**, then open (or create) an app for this integration.
  </Step>

  <Step title="Grant scopes">
    Under **Configure** → **Authentication**, grant the app the following scopes:

    * `read_admins`
    * `read_admin_activity_logs`
  </Step>

  <Step title="Create the Access Token">
    From the same Authentication page, create an **Access Token**. Copy it now - Intercom shows it only once.
  </Step>
</Steps>

## Connect Intercom to Oleria

<Steps>
  <Step title="Open the integration">
    Log in to your Oleria workspace, navigate to **Integrations**, and select **Intercom**.
  </Step>

  <Step title="Complete the connection form">
    Paste the **Access Token** you created in the Developer Hub.
  </Step>

  <Step title="Authenticate">
    Select **Authenticate** to complete the connection.
  </Step>

  <Step title="Verify the connection">
    Verify the Intercom integration status from the connected integrations page.
  </Step>
</Steps>

## What Oleria syncs

* **Users** - Intercom admins (teammates), from the admin list
* **Roles** - the role catalog, derived from each admin's assigned role
* **Teams** - Intercom teams, mapped as groups, and each admin's team memberships
* **Activity** - admin activity-log events (audit trail of admin actions in the workspace)

## Known limitations

* **US region only** - Oleria's Intercom integration supports workspaces on Intercom's US data region. EU and Australia region workspaces aren't supported; connecting one fails at authentication.
* Intercom exposes no dedicated roles endpoint, so the role catalog is derived from the roles observed on admin accounts rather than fetched directly.
* **No governance actions.** Intercom's API has no admin create, disable, suspend, or role/team-change operation. Oleria doesn't perform any account or access changes for this integration - teammate lifecycle, roles, and team membership are all managed in Intercom's own admin console.
* Contacts and Companies in Intercom aren't synced as resources - this integration covers workspace access (admins, roles, teams) and admin activity only.

## Contact us

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