Connect Aha to Rovo

Before you begin

• You will need to be an Aha! Admin to connect to Rovo.

• Only features are available to Rovo.

• Rovo will always respect permissions. Users will only ever see Aha! features that they already have access to.

Setting up Aha! OAuth

1. Log into Aha!, take note of your organization’s subdomain. For example, if your site is vitafleet.aha.io, you’ll need the vitafleet later.

2. Select the Settings icon () in the top right. Select Personal.

3. From the left navigation, select Personal > Developer.

4. Select the OAuth applications tab, then select the Register OAuth Application button at the top right of the screen.

5. From here, you fill out the details of a new OAuth connection:

   1. Name: Can be anything (‘Atlassian Rovo')

   2. Redirect URI: Set to https://id.atlassian.com/outboundAuth/finish

6. On the next screen, you’ll see a number of new values for your application. You’ll need Client ID / Application ID and Client Secret later.

Connecting to Aha!

Once you’ve setup OAuth in Aha!, you can connect.

1. In a new tab (you’ll need to copy values from your Aha! tab), go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Settings > Rovo.

3. Under Activated sites, next to the site you want to connect, select More actions () and select Add connector.

4. Select Aha! and press Next.

5. Enter a name for your Aha! connection. This doesn’t need to match anything.

6. Enter the subdomain for your Aha! site. If your full Aha! URL is vitafleet.aha.io, you only need to enter vitafleet.

7. Enter the Client ID / Application ID and the Client Secret you generated in the steps above.

8. Review the disclaimer.

9. Select Authorize Aha!.

10. A new tab will open to step you through Aha! authorization. Read through the details and select Authorize.

Next steps

After you’ve finished connecting Aha!:

1. Aha! Features will start to show in Search incrementally over the next few hours.

2. Your team members will see Aha! show up as a filter option in Search. If they haven’t connected to Aha! from their Atlassian account, they may be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see features that they already have access to.

3. Depending on the number of features in Aha!, it may take some time for all your features to be indexed and appear in Search.