Documentation integration
Documentation from IT Glue on the customer hub alongside tickets, alerts, and backups — without ever syncing password secrets.
What Vectis syncs
IT Glue organizations map onto Vectis customer accounts on first sync, and from there Vectis pulls documents (titles plus folders — bodies fetched on demand and never cached), configurations with hostname, IP, serial, and asset tag, plus flexible assets grouped by flexible-asset type with password-like traits scrubbed at the adapter boundary. Password metadata syncs (name, category, username, last-rotated) — never the secret value itself. IT Glue remains the source of truth for the secret; Vectis links out for the reveal.
What you can do
IT Glue is a read-only adapter here — documents and configurations from IT Glue land on the customer hub alongside tickets, alerts, and backups so a dispatcher doesn't have to swap tabs to find a runbook. If you run Hudu somewhere and IT Glue somewhere else (common during a migration), both sources land in the same documentation table per customer, source-tagged, so every runbook surfaces regardless of which platform stores it.
Honest about the limits
Passwords are never synced into Vectis — by deliberate design, the adapter refuses to call show_password=true or the singular /passwords/:id endpoint under any code path. The UI links out to IT Glue when a tech needs the secret, with the audit-log entry recorded on the IT Glue side, not Vectis. Region matters: US, EU, and AU each have a separate API host, and the wrong region returns empty data rather than an authentication error, so Vectis tests with a /organizations probe on save to catch that explicitly.
How it correlates
IT Glue on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
A dispatcher opens a customer and sees IT Glue documents + configurations in-page — no 'one sec, let me open IT Glue in another tab' while the customer waits. IT Glue remains the source of truth; Vectis links back for passwords and rich rendering.
If you run Hudu somewhere and IT Glue somewhere else (common during a migration), both sources land in the same documentation table per customer — source-tagged. The hub shows you every runbook regardless of which platform stores it.
Setup snapshot
In IT Glue, open Account → Settings → API Keys and mint a dedicated key for Vectis under a role that can View Organizations, Documents, Configurations, Flexible Assets, and Password metadata (read-only access to the categories above is sufficient — Vectis does not call write endpoints). Paste the key into Vectis and pick your region: US, EU, or AU. The region must match the IT Glue URL you log in at; the wrong region returns empty data rather than an error, so Vectis tests with a single-row /organizations probe before saving. Password values are never synced — only metadata — and the adapter refuses show_password=true or singular /passwords/:id calls under any code path.
# In the Vectis hub, add the connector:
category Documentation
vendor IT Glue
status Read-onlyPricing
IT Glue is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp
