When an add-on reads from a shared workspace through a connector, teams should review the connector’s access settings and validate them individually. Broad permissions, such as granting access to Everyone, can lead to oversharing of sensitive content.
How to check the connection
- Review connector access permissions. Check whether each permission grants access more broadly than intended.
- Look for broad access grants. Access for Everyone is one example of an incorrect permission setting that can expose sensitive content.
- Validate each connector in the admin center. Access permissions can be reviewed from the connection details pane for each connector.
What teams must still confirm
The permission review shows how each connector is configured, but it does not establish whether those settings are appropriate for a particular workspace. Teams must still compare the configured access with their intended users, shared content, and internal access decisions. The documentation does not provide a universal permission setting that would be correct for every workspace.