Skip to content

Outreach integration permissions

When you connect Opensense to Outreach, an Outreach administrator must authorize Opensense through OAuth. This article explains the four permissions Opensense requests, what data each permission accesses, and why the integration needs it.

These are the OAuth scopes Opensense requests during the authorization flow:

Permission What it accesses Why Opensense needs it
users.allOutreach user recordsReads user profile data (name, title, email, phone) to fill in and sync Opensense signature fields for each sender.
teams.readTeam structures and membershipReads team and group membership, to assign users to the correct Opensense groups during sync.
mailboxes.allOutreach mailbox configurationsReads and writes Outreach mailbox settings, to push the Opensense signature block to each user. This permission applies to Outreach mailbox records only. It doesn't grant access to the underlying email accounts (Microsoft 365, Google Workspace, or otherwise).
prospects.readOutreach prospect recordsReads prospect data to support recipient-based banner targeting. When a user sends an email through Outreach, Opensense can query prospect records to decide which banner campaign to display, based on the recipient.

Opensense requests only the permissions it needs to sync user data, deliver signatures, and support recipient-based targeting. Opensense doesn’t access sequences, emails, calls, tasks, or any other Outreach data beyond what’s listed above.

To disconnect the integration, revoke Opensense’s OAuth access in Outreach’s connected applications settings, or in the Opensense portal under Manage > Domain Settings > Integrations > Outreach.

For further help, contact Opensense Support at help@opensense.com.

Screenshot preview

Screenshot