This documentation is out of date. For up-to-date information, see Manage Rovo connectors.
Note that some connectors may be unavailable until you upgrade from beta.
To find out what’s new in Rovo or how to upgrade, see recent changes to Rovo beta.
Rovo connectors enable you to connect products outside Atlassian to enhance Rovo Agents, Search and Chat. More about Rovo connectors
Before connecting third-party products, you need to:
activate Rovo for a site
have organization admin permissions for your site. Learn about permissions
Limitation on connectors on a single site
Connectors can only be set up with one Atlassian site - for example, yoursite.atlassian.com. Your admin chooses which site this is.
If your organization has multiple sites with Atlassian, you can still use Rovo on all your sites. But data from connected third-party products will only be available on the site your Admin selects.
Connect third-party products with Rovo
To connect:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Settings, then Rovo.
Go to the Connected products tab and select the product you want to connect.
If you are picking your first connector, you’ll need to choose which site you want to connect.
Then:
For Google Drive, follow the steps below
For Microsoft SharePoint, follow the steps below.
Check permissions before you add third-party products
Rovo relies on permissions that are set in your third-party products. Content that isn’t restricted may appear in search results, or used by Agents or Chat.
Google Drive
You need Google administrator permissions to connect a Google workspace to Rovo. During beta, only Google Docs, Sheets and Slides are available to Rovo.
To connect Google Drive:
Log in to your Google Admin Console, navigate to Menu > Security > Access and data control > API controls > Manage Domain Wide Delegation.
Select Add new.
Copy the client ID from the Atlassian Administration Google Drive setup screen and paste it into the Client ID field in your Google Admin Console.
Copy the OAuth scope URL from the Atlassian Administration Google Drive setup screen and paste it into the OAuth scopes (comma-delimited) field in your Google Admin Console.
In your Google Admin Console, select Authorize.
Next, go back to Atlassian Administration:
Enter a nickname for your Google Drive connection.
Enter an email address for the Google workspace administrator.
Review and agree to the data usage information.
Select Confirm.
SharePoint
You need Sharepoint global admin permissions to connect SharePoint to Rovo. During beta, only Microsoft Excel, PowerPoint, and Word are available to Rovo.
In the Azure portal:
Log in to your Azure portal and navigate to Microsoft Entra ID.
In the side navigation, under Manage, select App registrations, then New registration.
On the Register an application page in the Azure portal, name the connection to Rovo (for example, “Atlassian Rovo”), select Accounts in this organizational directory only, and then select Register.
In the side navigation, under Manage, select API permissions.
Select Add a permission on the API permissions page, then Microsoft Graph.
Select Application permissions and add these permissions:
User.Read.All
Group.Read.All
GroupMember.Read.All
Directory.Read.All
Files.Read.All
Reports.Read.All
Sites.Read.All
AuditLogsQuery-SharePoint.Read.AllSelect Add permissions.
In the side navigation, under Security, select Permissions.
Select Grant admin consent for <workspaceName>.
Once this is done, back on the Manage > API permissions screen, in the Status column of the table, you should see green ticks and Granted for <workspace> (except the permission User.Read, which doesn't require Admin consent).
Go to Overview and copy the following details back into the Atlassian Administration modal:
SharePoint domain name.
Your application ID.
The directory ID.
Next, we need to setup Sharepoint permissions:
Navigate to
<your-sharepoint-domain>-admin.sharepoint.com/_layouts/15/appinv.aspxUsing the application ID from above, paste the value in the App ID field and select Lookup.
Fill in the next two fields with whatever you would like (these will not be used)
Fill in the App Domain with
www.localhost.comRedirect URL with
https://www.localhost.com/
Paste the following into the App's Permission request XML:
<AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="FullControl" /> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" /> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" /></AppPermissionRequests>
5. Select Create, and on the next screen read the permissions and select Trust it.
Next, back in the Azure portal create a client secret:
Back in your created app in Azure, in the side navigation, under Manage, select Certificates & secrets.
Select New client secret.
Enter a description for the secret, select an expiry time, and then select Add.
Copy the client secret Value into the Client secret field in the Atlassian Administration modal.
Review and agree to the data usage information.
Select Confirm.
Newer Sharepoint tenants
If your Sharepoint tenant was recently created (post-2019), you also need to enable apps to use ACS app-only access tokens.
In Powershell:
1. Install PnP Powershell Module by running:
Install-Module PnP.PowerShell -Scope CurrentUser
2. Connect to your SharePoint admin domain:
Connect-PnPOnline -Url https://<your-sharepoint-domain>-admin.sharepoint.com
3. If not already registered, register PnP Azure App:
Register-PnPAzureADApp -Interactive
4. Disable enable app authentication:
Set-PnPTenant -DisableCustomAppAuthentication $false
What’s next
After connecting a product, it might take a while for its results to appear in Search and Rovo. Depending on the amount of content, the time needed can vary from a few minutes to an entire day.
Meanwhile, you and your team will need to authorize the third-party products from within Confluence to start using their content with Rovo.