IT Glue
IT Glue
IT Glue is a documentation source, an alternative to Hudu for MSPs already running it. Hal reads it so an alert that names a client or a device lands against the documented record rather than a bare identifier.
What Hal reads:
- Organizations, the client records
- Configurations, the documented assets, searchable by name, IP, or serial
- Contacts, locations and domains
- Expirations
- Flexible assets and their types, the custom documentation your team keeps per client
- Users and groups
- The reference lists behind them: configuration types and statuses, organization types and statuses, contact types, platforms, manufacturers, models, operating systems, regions and countries
- The activity log: IT Glue’s own record of who viewed or changed what inside IT Glue, and of failed sign-ins and account lockouts
A Credit Card flexible asset shows only that it exists, with its name, never its traits, and a card’s expiration carries no date.
Hal uses the key read-only: every call is a read, and he never touches the IT Glue password vault.
Who can read the activity log. IT Glue’s activity log records who viewed which password and when each person signed in, so in chat Hal gives the log only to a Hal admin: the portal owner or anyone on the portal’s admin list. He checks the identity the sign-in verified: your web chat sign-in, the email Slack returns for you (which needs the Slack app’s users:read.email scope, see Slack), or a Zendesk note’s author. Anyone else is refused and told to ask a Hal admin, and without a verified email Hal points you to the portal’s web chat. Hal’s own investigations still read the log when an incident calls for it, and one that a watch or a sentry opens names on its report who opened the watch or put the person under sentry.
How to connect
In the Hal portal, add an IT Glue API key for your account. An IT Glue key is not read-only; its one restriction is the optional Password Access setting, which decides whether the Passwords API returns values. Leave it off. Hal only ever reads with the key, and the password endpoints are outside what he can query in any case. Hal tests connectivity before the source goes live. Setup walkthroughs are in Getting Started.
A deployment uses one documentation source at a time, Hudu or IT Glue, whichever you run.
The marketing overview, what IT Glue gives Hal and why, is at /integrations/itglue/.
See what Hal surfaces on your own clients.
No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.
- 01You ask us your questions. No deck, no demo dataset.
- 02You sign a short evaluation agreement, and we stand up your own instance.
- 03You connect one tenant from your own admin console. Hal watches it for 14 days.
- 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.