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

# Bugsnag

> Connect your Bugsnag organization to Oleria to continuously discover user access across your error monitoring platform.

Bugsnag is an error monitoring platform for tracking application stability. Connect your Bugsnag organization to Oleria to bring user access into your identity and access graph, without a dedicated Bugsnag-specific integration.

## What Oleria discovers

User accounts and profile attributes synced from Bugsnag's directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Bugsnag's standard SCIM provisioning schedule.

## Prerequisites

* Admin access in Bugsnag with permission to enable SCIM provisioning and generate a bearer token.
* 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 Bugsnag's own SCIM provisioning documentation.
</Note>

## Get your SCIM credentials from Bugsnag

<Steps>
  <Step title="Enable SCIM provisioning in Bugsnag">
    Sign in to Bugsnag as an admin and enable SCIM provisioning in **Settings**.
  </Step>

  <Step title="Copy your SCIM Base URL and Authentication token">
    Bugsnag generates a SCIM base URL and a bearer token when you enable provisioning. Copy both values before you leave the page - you'll paste them into Oleria in the next section:

    * **SCIM Base URL** - the HTTPS SCIM endpoint for your Bugsnag organization.
    * **Authentication token** - the bearer token Bugsnag generates for provisioning.

    <Note>
      Bugsnag displays the token only once. Copy and store it securely, and rotate it per your organization's security policy.
    </Note>
  </Step>
</Steps>

## Connect Bugsnag to Oleria

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

  <Step title="Complete the connection form">
    Select **Continue** and fill in the connection form:

    | Field                | Notes                                                                                  |
    | :------------------- | :------------------------------------------------------------------------------------- |
    | Instance name        | Optional. Short, recognizable label for this connection (for example, `bugsnag-prod`). |
    | SCIM Base URL        | Required. The HTTPS SCIM endpoint copied from Bugsnag.                                 |
    | Authentication token | Required. The bearer token issued by Bugsnag.                                          |
  </Step>

  <Step title="Save the integration">
    Select **Connect** to validate the credentials and save the integration.
  </Step>
</Steps>

## Verify the integration

Confirm the new instance appears in your Oleria workspace under **Connected Integrations** with a status of **Healthy**. Oleria syncs users from Bugsnag on the standard SCIM provisioning schedule once the initial sync completes.

<Note>
  If Bugsnag rotates your bearer token, update the Authentication token in Oleria by editing the integration.
</Note>

## Governance actions

Oleria can also invoke lifecycle actions in Bugsnag when the token you provide has write access:

* Enable or disable a user account
* Create a new user

<Note>
  Many teams start with a read-only token for visibility, then grant write access once they're ready to automate remediation in Bugsnag.
</Note>

## Contact us

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