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.
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.
Get your SCIM credentials from Bugsnag
1
Enable SCIM provisioning in Bugsnag
Sign in to Bugsnag as an admin and enable SCIM provisioning in Settings.
2
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.
Bugsnag displays the token only once. Copy and store it securely, and rotate it per your organization’s security policy.
Connect Bugsnag to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the Bugsnag tile.
2
Complete the connection form
Select Continue and fill in the connection form:
3
Save the integration
Select Connect to validate the credentials and save the integration.
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.If Bugsnag rotates your bearer token, update the Authentication token in Oleria by editing the integration.
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
Many teams start with a read-only token for visibility, then grant write access once they’re ready to automate remediation in Bugsnag.

