Rovo connectors enable you to connect data sources outside Atlassian to enhance Rovo Search, Chat and Agents.
Authenticating and authorizing third-party products
Once an admin has authenticated with 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.
Each user must also authorize with the third-party product to ensure they see only the data they have permission to access.
Once the admin and the user have authenticated with a product, Rovo can use and show that data in Search, Chat and Agents.
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.
Permissions in Rovo
The sync between Rovo and your third-party products enables us to enforce your permissions in those products.
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 usually have access to that content in such third-party products.
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 that you give access to select people to Google Drive, Confluence or SharePoint |
|
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 |
|