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

# Egnyte

## After this article

You will be able to connect Egnyte to Lumos to sync users, their roles, and their groups, and to suspend or deprovision Egnyte users from Lumos workflows.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | User accounts. Only users with `userType=standard` are shown, other user types are business partners and are excluded |
| Roles | Permission | Yes | No | The `role` field on each Egnyte user |
| Groups | Permission | Yes | No | Egnyte group memberships |

| Deprovisioning Action | Type | Description |
| - | - | - |
| Suspend | User | Disables the user in Egnyte (sets `active` to false), preventing login and reclaiming a license. Lumos account status becomes **Suspended** |
| Deprovision | User | Permanently removes the user **and their data** from Egnyte and reclaims the license. Lumos account status becomes **Deprovisioned** |

Egnyte user status maps to Lumos account status: `active` → Active, `inactive` → Suspended, deleted (Egnyte no longer returns the user) → Deprovisioned. **Last Login** in Lumos comes from the user's `lastActiveDate` field.

## Required plan and roles

* **Lumos plan:** no minimum plan is required.
* **Egnyte role:** the connecting Egnyte user must be an **Admin**.
* **OAuth scope:** `Egnyte.user` (User management), the only scope the integration requests. It covers user, role, and group sync as well as the suspend and deprovision actions, so it is required in full. There is no read-only subset.

## Read-only access vs provisioning

**Is read-only possible?** No. Egnyte's `Egnyte.user` scope is the only scope this integration requests, and it covers user, role, and group sync together with the suspend and deprovision actions. There's no read-only subset of it.

**What full provisioning requires.** An Egnyte Admin account authorizing the OAuth flow with the `Egnyte.user` scope, using the subdomain from your Egnyte URL. Follow the steps below to connect.

**Watch out for.** Because `Egnyte.user` is a single all-or-nothing scope, you can't set up a visibility-only connection. Suspend disables the account and reclaims a license without touching the user's data, while Deprovision permanently deletes the user and their data, so pick the action deliberately during offboarding.

## Instructions

**Phase 1: Get your Egnyte subdomain**

1. Log in to Egnyte as an Admin.
2. Copy the subdomain from your Egnyte URL (`subdomain.egnyte.com`) and save it.

**Phase 2: Connect in Lumos**

1. Find the Egnyte card in your Lumos integrations (reconnect an existing card or add a new one).
2. Paste the subdomain into the **Subdomain** field.
3. Click **Connect**.
4. Accept the requested scopes in Egnyte to finish the OAuth flow.

## 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

**Some Egnyte users don't appear in Lumos.** Lumos only displays users whose `userType` is `standard`. Other user types are treated as business partners and are intentionally excluded from sync.

**OAuth connection fails.** Confirm the user completing the flow is an Egnyte Admin and that the `Egnyte.user` scope was accepted on the consent screen. Also verify the subdomain was entered exactly as it appears in `subdomain.egnyte.com` (no `https://` or trailing path).

**Deprovision removed more than expected.** Deprovisioning is a permanent Egnyte user deletion that also removes the user's data. If you only want to block login and reclaim the license while preserving data, use **Suspend** instead.