Skip to main content
Aha! is a product roadmap platform for planning and prioritizing product strategy. Connect your Aha! workspace to Oleria to bring user and workspace access into your identity and access graph, without a dedicated Aha!-specific integration.

​
What Oleria discovers

  • User accounts and profile attributes synced from Aha!‘s directory.
  • Workspace group membership.
Oleria uses this data for dormant account detection and access reviews, refreshed on Aha!‘s standard SCIM provisioning schedule.

​
Prerequisites

  • Admin access in Aha! 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 Aha!‘s own SCIM provisioning documentation.

​
Get your SCIM credentials from Aha!

1

Enable SCIM provisioning in Aha!

Sign in to Aha! as an admin and enable SCIM provisioning in Settings.
2

Copy your SCIM Base URL and Authentication token

Aha! 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 Aha! workspace.
  • Authentication token - the bearer token Aha! generates for provisioning.
Aha! displays the token only once. Copy and store it securely, and rotate it per your organization’s security policy.

​
Connect Aha! to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the Aha! 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 and groups from Aha! on the standard SCIM provisioning schedule once the initial sync completes.
If Aha! rotates your bearer token, update the Authentication token in Oleria by editing the integration.

​
Governance actions

Oleria can also invoke lifecycle actions in Aha! when the token you provide has write access:
  • Enable or disable a user account
  • Add or remove a user from a group
  • Create a new user or group
Many teams start with a read-only token for visibility, then grant write access once they’re ready to automate remediation in Aha!.

​
Contact us

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