Learn about Atlassian organizations
New to administering Atlassian cloud products? Learn about Atlassian organizations and what it means to be an organization admin.
Rovo connectors enable you to connect third-party products outside Atlassian to enhance Rovo Agents, Search, and Chat.
To setup Rovo connectors, you need to:
activate Rovo for a site
have organization admin permissions for your site. Learn about permissions
Check permissions
Rovo relies on and respects the permissions that are set in your third-party products. Content that isn’t restricted may appear for all users in search results, or can be used by Agents or Chat.
On each site with Rovo, most connectors can only be used to connect to a single workspace. This means that:
On a single Rovo site (for example, yoursite.atlassian.net), you can only connect each product once (Google Drive)
Each different site with Rovo can connect to a different product workspace (your company's Google Drive) using its own connector.
The only connector that can be setup multiple times on a single Rovo site is the Custom website connector.
To connect your third-party product, see:
If you’d like to disconnect a product, see Disconnect a product from Rovo.
Figma and Rovo
Figma’s integration with Rovo is based on the individual user’s permissions, without needing to set up a connector. See How Rovo shows Figma results for more information.
Once you’ve setup the connector, each user must connect to the external product to ensure they see only the data they have permission to access. They might not have to perform this step if they have previously connected their Atlassian account to the product.
Once the connector is setup and the user has connected it with the product, Rovo can use and show that data in Search, Chat, and Agents.
Once you’ve set up a connector, Rovo sets up a secure sync with the third-party product. When new content is created or removed in that product, the relevant information is synced with Rovo.
This means restricted data in your connected third-party products (for example, a private file or folder in Google Drive) can only be seen and used in Rovo by those users who already have access to that content in such third-party products.
Included below are some scenarios to help you better understand how Rovo handles permissions and changes:
Scenario | Access |
Adding a new document without access restrictions to Google Drive, Confluence or Microsoft SharePoint |
|
Adding a private document (only you have access) to Google Drive, Confluence or SharePoint |
|
Adding a document to Google Drive, Confluence or Sharepoint and giving access to select people |
|
Deleting a document (Google Drive, SharePoint, Confluence) |
|
Adding restrictions to a previously unrestricted document (Google Drive, SharePoint, Confluence) |
|
Removing restrictions from a previously restricted document (Google Drive, SharePoint, Confluence) |
|
A Jira project is made private and only accessible by a team |
|
Connect custom website to Rovo
How to index and crawl your custom website with Rovo.
Connect Github to Rovo
How to setup and connect GitHub to Rovo.
Connect Google Drive to Rovo
How to setup and connect your Google Drive workspace to Rovo.
Connect Microsoft Teams to Rovo
How to setup and connect Microsoft Teams to Rovo.
Connect SharePoint to Rovo
How to setup and connect your SharePoint workspace to Rovo.
Connect Slack to Rovo
How to setup and connect your Slack workspace to Rovo.
Manage connector details
Managing and editing connector details for a Rovo-activated site.
Disconnect a product from Rovo
How to disconnect a third-party product from Rovo.
Was this helpful?