Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers IT Glue. Required configuration fields: ITGLUE_API_URL, ITGLUE_API_KEY Current availability: Authorization check only — ingestion pending.

Before you start. A dedicated, read-only organization-owned API identity with the vendor’s required permissions.

Step 1. Create an IT Glue API key with only the approved organization scope.

Step 2. Choose the correct region-specific HTTPS API base URL from IT Glue documentation.

Step 3. Save ITGLUE_API_URL and ITGLUE_API_KEY in protected configuration, then run the organization-list authorization check.

Step 4. Do not assume documents, passwords or configurations were imported: synchronization is not implemented. Keep credential data within its approved vault boundary.

Now verify the result. The provider read check succeeds with only the intended tenant’s records. The UI reports authorization-only status and does not claim completed synchronization.

If you get stuck. A 403 usually needs a permission, license or administrator-consent correction. Do not grant broad write permissions to make a read-only check pass.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.