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

# Aha!

> Connect your Aha! workspace to Oleria to continuously discover user and workspace access across your product roadmap platform.

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.

<Note>
  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.
</Note>

## Get your SCIM credentials from Aha!

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

  <Step title="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.

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

## Connect Aha! to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations**, then select the **Aha!** 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, `aha-prod`). |
    | SCIM Base URL        | Required. The HTTPS SCIM endpoint copied from Aha!.                                |
    | Authentication token | Required. The bearer token issued by Aha!.                                         |
  </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 and groups from Aha! on the standard SCIM provisioning schedule once the initial sync completes.

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

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

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

## Contact us

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