Collaboration

Egnyte

Browse your Egnyte Connect content and directory from Dex - folders, file metadata, and users for one tenant.

Dex connects to Egnyte Connect through the Public API so admins can explore one {domain}.egnyte.com tenant conversationally - confirm the connected token identity, list folder contents and file metadata under the Shared and Private namespaces, and look up users in the directory. This is a read-focused surface: Dex browses userinfo, the file system, and users, but does not upload, move, or change permissions. Egnyte is a per-tenant app - each Dex connection stores its own OAuth token for a single Egnyte domain, so there is no shared MSP master credential.

Start free →See Dex Live

What Dex does with Egnyte

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Confirm the connected Egnyte token identity via userinfo
List folder contents and read file metadata under the Shared and Private namespaces
List users in the Egnyte directory, paging at 100 per request
Look up a single user by numeric id, resolving a name or email to an id with a filter first
Stay inside Egnyte rate limits - 2 calls/second and 1,000 calls/day per access token

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Whose Egnyte token is this connection using?
>List the contents of the Shared folder in Egnyte
>Show me the file metadata for Shared/Projects Q1
>Find the Egnyte user with the email ops@example.com
>How many users are in the Egnyte directory?

Policy actions

Every action Dex can take on Egnyte is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`egnyte_get_userinfo`	Read Egnyte userinfo for the connected OAuth token	—
`egnyte_list_fs`	List Egnyte folder contents or read file metadata via GET /pubapi/v1/fs/{path}	—
`egnyte_list_users`	List Egnyte users via GET /pubapi/v2/users	—
`egnyte_get_user`	Read one Egnyte user by numeric id	—

How to configure Egnyte

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
Create an OAuth application at developers.egnyte.com to obtain a client id for your {domain}.egnyte.com tenant.
2
Complete the Egnyte OAuth flow once to obtain a refresh token (plus client id) - this is preferred, so Dex mints a fresh access token on every connection build and you never re-paste.
3
In Dex, enable the Egnyte integration and paste the domain label (e.g. acme), client id, and refresh token. A pasted access token on its own works as a fallback.
4
Dex validates the credentials with a live call to GET /pubapi/v1/userinfo before saving.
5
Run the Egnyte - Token Keep-Alive automation once by hand, confirm a second run also succeeds, then schedule it weekly so an idle connection never goes stale.

Credentials required

domain: Egnyte subdomain label only, e.g. acme for https://acme.egnyte.com (non-secret)
client_id: Client id of the admin Egnyte OAuth app - required to redeem a refresh token (non-secret)
client_secret: Only for a confidential OAuth app; leave blank for a public one (secret)
refresh_token: Preferred long-lived credential - with client id, Dex mints a fresh access token on every build (secret)
access_token: Optional fallback when a refresh is refused, or usable on its own without registering an OAuth app (secret)

Requirements

•An Egnyte Connect tenant and an OAuth token carrying the Egnyte.filesystem and/or Egnyte.user scopes
•Egnyte has no read-only scope - the issued token carries write access even though this app only reads
•Egnyte access tokens expire 30 days after issue; a refresh token plus client id keeps the connection minting fresh tokens automatically
•Per-tenant app - one OAuth token per Egnyte domain, with no shared MSP master credential or tenant-id scoping