---
title: "Outreach integration permissions"
slug: "outreach-integration-permissions"
description: "A breakdown of the four OAuth permissions Opensense requests when connecting to Outreach, including what each permission accesses and why it is needed."
updated: 2026-03-19T16:59:22.000Z
canonical: "https://help.opensense.com/docs/outreach-integration-permissions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.opensense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outreach integration permissions

## Overview

When you [connect Opensense to Outreach](https://help.opensense.com/docs/outreach-integration), 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.

## Required permissions

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

<div class="kb-deployment-compare kb-deployment-compare--plain">
  <div class="kb-deployment-compare__viewport" role="region" aria-label="Outreach OAuth permissions" tabindex="0">
    <table>
      <colgroup><col class="kb-deployment-compare__feature-col"></colgroup>
      <thead>
        <tr>
          <th scope="col">Permission</th>
          <th scope="col"><span class="kb-deployment-compare__method">What it accesses</span></th>
          <th scope="col"><span class="kb-deployment-compare__method">Why Opensense needs it</span></th>
        </tr>
      </thead>
      <tbody>
        <tr><th scope="row"><code>users.all</code></th><td>Outreach user records</td><td>Reads user profile data (name, title, email, phone) to fill in and sync Opensense signature fields for each sender.</td></tr>
        <tr><th scope="row"><code>teams.read</code></th><td>Team structures and membership</td><td>Reads team and group membership, to assign users to the correct Opensense groups during sync.</td></tr>
        <tr><th scope="row"><code>mailboxes.all</code></th><td>Outreach mailbox configurations</td><td>Reads and writes Outreach mailbox settings, to push the Opensense signature block to each user. This permission applies to <strong>Outreach mailbox records only</strong>. It doesn't grant access to the underlying email accounts (Microsoft 365, Google Workspace, or otherwise).</td></tr>
        <tr><th scope="row"><code>prospects.read</code></th><td>Outreach prospect records</td><td>Reads 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.</td></tr>
      </tbody>
    </table>
  </div>
</div>

## Scope of access

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.

:::caution[The only write access]
`mailboxes.all` is the only permission that includes write access. It's limited to Outreach's internal mailbox configuration, **not your organization's email accounts**. Opensense uses it only to write signature content to Outreach sender profiles.
:::

## Revoking access

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**.


## What's next

- [Connecting Outreach to Opensense](https://help.opensense.com/docs/outreach-integration)

For further help, contact Opensense Support at [help@opensense.com](mailto:help@opensense.com).