How Rovo connector permissions are kept in sync
Once you’ve set up an admin-managed connector, Rovo sets up a secure sync with the third-party app. When new content is created or removed in that app, the relevant information is synced with Rovo.
This means restricted data in your connected third-party apps (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 apps.
Example scenarios
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 |
|
Was this helpful?