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

# Outreach

## After this article

You will be able to connect Outreach to Lumos to sync users, view their roles and last login, and suspend access.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | User account records |
| Roles | Permission | Yes | No | Work roles associated with the user (from the `duties` field) |

| Deprovisioning Action | Type | Description |
| - | - | - |
| Suspend | User | Locks the user in Outreach. This removes their licenses and prevents login. Locked users do not count against your seats. Marks the Lumos Account Status as Suspended and reclaims a license. |

Suspend is available for Offboarding, Access Reviews, and License Management. It is not available for the AppStore.

**User status mapping.** `active` maps to Active, `locked` maps to Suspended, and a deleted user (no longer returned by Outreach) maps to Deprovisioned.

**Last login.** The Last Login value is the last time the user signed into Outreach, read from the `currentSignInAt` value.

## Required plan and roles

* **Outreach plan:** no minimum plan is required.
* **Outreach role:** the connecting user must be an **Admin** with an active account.
* **OAuth scope:** the integration requests `users.all` during setup, which lets Lumos view and manage users.

## Read-only access vs provisioning

**Is read-only possible?** No. The integration authenticates with the single `users.all` OAuth scope, which the article describes as letting Lumos both view and manage users, and no narrower or read-only scope is offered during setup.

**What full provisioning requires.** An Admin with an active Outreach account completing the OAuth flow and accepting the `users.all` scope, as described below.

**Watch out for.** Suspend locks the user and removes their license but is only available for Offboarding, Access Reviews, and License Management, not the AppStore. If an Outreach SCIM provisioning connection gets merged with this standard integration, the merged connection can enter an error state that isn't resolvable from the UI, so contact Lumos support if that happens.

## Instructions

**Phase 1: Connect in Lumos**

1. Find the Outreach card in your Lumos integrations (reconnect an existing card or add a new one).
2. Click **Connect Outreach**.
3. Accept the scopes in Outreach to complete the connection.

## API Endpoints Used

<Note>
  The API endpoints this integration uses are available to logged-in Lumos customers. [Log in](/login) to view them.
</Note>

## Troubleshooting

**Can't connect the integration.** Make sure you are logged into Outreach with an active Admin account.

**A merged Outreach SCIM connection is stuck in an error state.** When an Outreach SCIM provisioning integration is merged with the standard Outreach integration, the merged integration can enter an error state that an admin cannot resolve from the UI. Contact Lumos support to clear it.