Egnyte

Connect Egnyte to collect cloud storage provider evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Egnyte:

   1. Using the email address of an active Egnyte domain administrator (not a service account), register for a developer account on the Egnyte Developer Portal (developers.egnyte.com) and click the confirmation link in the email.
   2. Sign in to the developer portal, click the drop-down arrow next to your email and click Apps.
   3. Click New APP.
   4. Fill in App Name, Description and Egnyte Domain (only the part before .egnyte.com). For Type, select Internal Application (for your own company's internal use).
   5. Under APIs, click Request next to Prod Collaborate, then click Save.
   6. Open the app to see the API Key and Secret. The key starts as Pending Approval and becomes Active after Egnyte verifies the request.
   7. Exchange the key for an access token with the Resource Owner Password Credentials flow: send POST https://{domain}.egnyte.com/puboauth/token (form-encoded) with client_id = the API key, client_secret = the secret, username and password of the domain administrator, grant_type=password and scope=Egnyte.user.
   8. Copy access_token from the response. It is valid for 30 days and is revoked immediately if the user changes their password.
   9. Scope the token to Egnyte.user (User Management API) by passing scope=Egnyte.user in the token request. Without a scope parameter the token has global access to all APIs.

   Where to find the other values:

   • Domain: Your Egnyte web address is yourdomain.egnyte.com; the Domain is the yourdomain part (the same value entered in Egnyte Domain when creating the app).

   API keys are only issued to Egnyte domain administrators on eligible plans; Trial, Legacy Office and Team plans are not supported. Keys are reviewed by Egnyte (Pending Approval, then Active). The access token comes from an OAuth API call, not from the UI; it expires after 30 days (a refresh token is returned alongside it). The developer portal (developers.egnyte.com) serves its docs from us-partner-integrations.egnyte.com/integration/cfs/api-docs/. Egnyte migrated from Mashery to Apigee on 1 Oct 2025; old Mashery accounts must re-register with the same email. Verification 2026-10-07: Egnyte's Getting Started page shows the API key and secret on the app page after saving but does not say whether they can be viewed again later, so one_time_display is unknown.

   Source: us-partner-integrations.egnyte.com, us-partner-integrations.egnyte.com, developers.egnyte.com, checked 2026-10-07.

   The permissions Safeguard needs: Egnyte.user. Egnyte shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. Safeguard's compliance tests for Egnyte need the credential on the API token tab: an OAuth connection cannot read everything they check.

2. On Compliance › Connectors, open Egnyte, click Connect, choose API token and fill in:

   Field	What to enter
   Domain	Required. The part before .egnyte.com in your address.
   Access token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://mcp-server.egnyte.com/sse is filled in. Sign in to Egnyte when asked. It lets Griffin AI search Egnyte; the compliance evidence comes from the API token connection.

Frameworks

Safeguard's automated tests read Egnyte and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Storage Provider connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks