> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Egnyte OAuth 2.0 (Public Application) connector profile – StackOne setup guide > Set up the OAuth 2.0 (Public Application) connector profile for Egnyte in StackOne. One-time admin setup required before your users can link Egnyte accounts via Hub. You need an Egnyte developer account tied to an active Egnyte Domain Admin. The Egnyte plan must be an eligible plan — Trial, Legacy Office, or Team plans are not supported. API keys requested by a non-admin will be declined.
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions...
Dynamic Guide URL
Scopes Selected

          

            
Separator

Register a new App on the Egnyte Developer Portal

To connect Egnyte with StackOne you need to create an App with OAuth 2.0 authentication in the Egnyte Developer Portal. This will generate the API Key and API Secret required for integration, which map to `client_id` and `client_secret` in OAuth requests.

Open your browser and navigate to the Egnyte Developer Portal. Click Sign In in the top-right corner, then enter your Email and Password and click SIGN IN. Use an account tied to an active Egnyte Domain Admin.

Egnyte Developer Portal sign-in form with Email and Password fields

Click your account email in the top-right corner to open the account dropdown, then click Apps. You land on the My Apps page.

Account dropdown showing the Apps menu item on the Egnyte Developer Portal

On the My Apps page, click + NEW APP in the top-right corner to open the New App form.

My Apps page with the + NEW APP button in the top-right

Complete the Overview section of the New App form.

  • App Name — a display name for the app (for example, `StackOne Integration`).
  • Description — a short description of the integration.
  • Egnyte Domain — the customer's Egnyte subdomain, without the `.egnyte.com` suffix. For example, from `https://acme.egnyte.com` enter `acme`. Trial domains are not eligible for API keys.
  • App Icon URL (optional) — URL to an image file (PNG, max 100px by 100px).
  • Type — choose Publicly Available Application.
  • Leave Current User Base and Platform at their defaults, or set them to values that match your integration.
Egnyte New App form showing App Name, Description and Additional Information fields

In the Registered OAuth Redirect URI field, enter the StackOne callback so Egnyte can redirect users back to StackOne after authentication.

  • Paste `https://api.stackone.com/connect/oauth2/egnyte/callback` into Registered OAuth Redirect URI.
Registered OAuth Redirect URI field on the New App form
Enables actions: Add Comment, Chunked Upload By File ID, Create Group, Create Link (v1), Create User, Delete Comment, Delete File Or Folder (v2), Delete File Or Folder By ID, Delete Group, Delete Link (v1), Delete User, Download File Content By ID, Download File Content By Path, File Or Folder Operation (v2), File Or Folder Operation By ID, Get Comment, Get Effective Permissions For User, Get Events Cursor, Get File Or Folder Metadata (v2), Get File Or Folder Metadata By ID, Get Folder Statistics By ID, Get Group, Get Link (v1), Get User, Get User Info, List Comments, List Events (v2), List Groups, List Links (v2), List Trash Contents (v2), List Users, Modify Folder Options, Partially Update Group, Replace Group, Restore Or Purge Trash Items, Search Files And Folders (v2), Update User, Upload File Content By Path

Scroll to the APIs section. A locked padlock indicates approval is required before access to the API is granted. Click Request on the row for Prod Collaborate — this API grouping covers filesystem, comments, links, permissions, users, groups, search, trash, and events. Enable the scopes required for your use case:

APIs section on the New App form showing Prod Collaborate with the Request button

Click SAVE at the bottom-right of the form. The app is submitted and its API key is issued in Inactive status. Egnyte reviews the request; once the requested APIs move from Pending approval to approved, the key status flips to Active and you can use it.

Once approved, open the app from My Apps and scroll to the API Keys section on the app profile.

  • In the Key column, click the copy icon (Copy API key) to copy the API Key. This value maps to `client_id` in OAuth requests.
  • In the Secret column, click Show secret to reveal the API Secret, then click the copy icon (Copy secret) to copy it. This value maps to `client_secret` in OAuth requests.
  • The API Secret is masked by default; click Show secret to reveal it whenever you need to view or re-copy it. Treat it as a password and store it securely.
  • Paste the API Key into the API Key field in the StackOne Connector profile.
  • Paste the API Secret into the API Secret field in the StackOne Connector profile.
  • Leave OAuth Scopes in the StackOne Connector profile blank to use the connector defaults (`Egnyte.filesystem Egnyte.permission Egnyte.link Egnyte.user Egnyte.group`), or enter a space-separated subset if you want to restrict access.
App profile API Keys section with Copy API key and Show secret controls
## Creating the StackOne Connector Profile To create the Connector Profile in StackOne for Egnyte: Login to StackOne and navigate to [Connector Profiles](https://app.stackone.com/connector_profiles)
  • Click + Connector Profile
  • Search for and select Egnyte
  • Select Type as OAuth 2.0 (Public Application)
  • Fill out the fields using details retrieved from your provider:
    • API Key
    • API Secret
    • OAuth Scopes (Optional)
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
 Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Egnyte.