Documentation integration
Each customer's Egnyte folder on the same page as their tickets and alerts — recent files live from the Egnyte API, no file content cached.
What Vectis syncs
Vectis stores one pointer per customer-mapped folder under your configured clients root — folder name and Egnyte deep-link, so 'Open in Egnyte' is one click. The folder's last-modified timestamp syncs so the customer hub shows freshness without holding a list of files in Vectis. Recent file metadata is fetched live from Egnyte on demand; nothing is cached server-side.
What you can do
Egnyte is a read-only adapter here — Vectis surfaces the right docs surface per customer without ever caching file contents. If your team uses Egnyte (or moved off IT Glue/Hudu to a cloud file server), the customer hub still shows the docs in the right place. Clicking the customer's folder card fetches the most recently modified files live, with every read audit-logged inside Vectis.
Honest about the limits
File contents are never persisted in Vectis — only folder pointers and on-demand metadata requests. The OAuth token uses Egnyte's password-grant flow, which the vendor still supports for service-account-style integrations; if your Egnyte tenant has disabled password grant, you'll need to mint a token through the alternate authorization-code flow and paste the resulting long-lived token into Vectis manually. Folder mapping is name-normalized against your clients root, with a pin override available when the folder name doesn't match the PSA name (acquisitions, abbreviations).
How it correlates
Egnyte on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
If your team uses Egnyte (or moved off IT Glue/Hudu to a cloud file server), the customer hub still shows you the right docs surface. Click the customer's folder card to fetch the most recently modified files live — never cached, always fresh.
Vectis matches each subfolder under your configured clients root to a customer by normalized name. When the folder name doesn't match the PSA name (acquisitions, abbreviations), pin the customer to a specific folder path and the auto-match yields to the override.
Setup snapshot
In the Egnyte Developer portal (developers.egnyte.com), register an API key and run the password-grant flow once to mint a long-lived access token. Paste the access token plus your Egnyte subdomain (the `<x>` in `<x>.egnyte.com`) and the absolute path to your clients root folder (for example, /Shared/Work/Acme/Clients) into Vectis. The adapter tests by calling /pubapi/v1/userinfo and listing the configured root before saving so a wrong path fails fast. File contents are never persisted on Vectis side — the customer hub fetches recent file metadata live on demand and audit-logs every read.
# In the Vectis hub, add the connector:
category Documentation
vendor Egnyte
status Read-onlyPricing
Egnyte is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp
