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
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives.
Read-only today
This adapter pulls data into Vectis but doesn’t write back into Egnyte. Rules can still react to the synced data — for example, a Pax8 subscription change can open a ConnectWise ticket or a HaloPSA action. The write-back lands in the PSA, not in Egnyte.
How it correlates
Vectis is about Egnyte joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
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 token plus your Egnyte subdomain (the `<x>` in `<x>.egnyte.com`) and the absolute path to your clients root folder (e.g. /Shared/Work/Acme/Clients). Vectis tests by calling /pubapi/v1/userinfo and listing the configured root before saving. File contents are never persisted — the customer hub fetches recent file metadata live on demand and audits every read.
Full setup guideavailable after signup
14-day free trial. Connect Egnyte at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.