Skip to main content
Back to Search AI connectors list The Egnyte connector lets Search AI ingest and index files from your Egnyte account, enabling search across your shared content.
SpecificationDetails
Repository typeCloud
Supported content.doc, .docx, .ppt, .pptx, .pdf, .txt
RACL supportYes
Content filteringNo

Prerequisites

  • An Egnyte account with admin access to the Developer Portal
  • Access to the Search AI application

Step 1: Register Search AI as an OAuth Client in Egnyte

  1. Go to the Egnyte Developer Portal.
  2. Register a new client app to enable communication between Egnyte and Search AI:
    • Set Platform to Web App and Type to Publicly Available Application.
    • Set the Registered OAuth Redirect URI to the URL matching your deployment region:
      • JP Region: https://jp-bots-idp.kore.ai/workflows/callback
      • DE Region: https://de-bots-idp.kore.ai/workflows/callback
      • Prod: https://idp.kore.com/workflows/callback
  3. Ensure a key is generated for the Connect API.
  4. Click Register to generate the client key and secret.

Step 2: Configure the Egnyte Connector in Search AI

  1. In Search AI, go to the Authorization page of the Egnyte connector.
  2. Provide the following fields and click Connect:
    FieldValue
    NameUnique name for the connector
    Authorization TypeOAuth 2.0
    Grant TypeAuthorization Code
    Client IDKey generated in Step 1
    Client SecretSecret generated in Step 1
    Host URLDomain URL for content ingestion (e.g., https://domain.egnyte.com)
  3. Complete the authentication prompt to confirm the connection.

Content Ingestion

After connecting, go to the Configuration tab to set up synchronization:
  • Sync Now — triggers an immediate sync.
  • Schedule Sync — sets up automatic sync on a recurring schedule.
Search AI ingests files from all shared folders in the Egnyte account. Files in private folders are not ingested. The folder path for each file is available as a metadata field.

RACL Support

Search AI enforces permissions at the folder level. Any user or group with access to a folder can access all files in that folder. File-level permissions and link-based sharing are not supported. For nested folders, files inherit permissions from the immediate parent folder. Permissions are stored in the sys_racl field.
  • Individual users: The user’s email address is added to sys_racl.
  • User groups: The group ID is added to sys_racl.
  • Administrators: Admin permissions are explicitly listed in sys_racl.
Example — if a folder is accessible to a specific user and a user group:
"sys_racl": [
    "john.smith@example.com",
    "b141b80a-7406-4c85-1e9435e699",
    "admin-group"
]