We're interested in connecting Google Drive, Slack, etc connectors to Rovo but unsure what data will be pulled into Rovo and how it will be protected and shared with end user.
I.e. If I integrate Slack with Rovo, would all public and private channel data be visible to Rovo and users that use Rovo?
Also, if guests are invite to a confluence page, would they have access to data available through the connector, ie. will they be able to see data from Slack channels?
Hi @Rob Sung
Rovo respects permissions. So a customer will only see what he should see and nothing else. Here https://support.atlassian.com/organization-administration/docs/connect-slack-to-rovo/ you will see what kind of data it draws.
Hope the above helps.
Hi @Rob Sung
You should check out: Rovo data, privacy, and usage guidelines
When you connect tools like Slack or Google Drive to Rovo, Rovo does not create a new pool of data that everyone can see. It works on a permission-aware model and respects the access controls of each connected system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The answers above appear to be partially correct. Some connectors work on the specific user level permission (e.g. user x will only get what user x see on slack and user y cannot see slack for user x.).
However, Google Drive appears to works differently. If a doc is shared with org and marked as searchable, it'll be discoverable by other users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I.e. you need to look at each connector instead of assuming a blanket statement.
also, the question about the guest account was not answered. it appears that guest accounts are not yet supported by rovo... but if/when the are, would guest be able to search on contents that are restricted to internal employees?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.