Manual

Manual token setup, documented step by step: the app registration and permissions Hal needs in a Microsoft 365 tenant, and the domain-wide delegation he needs in a Google Workspace, as you would build them in the customer’s admin consoles by hand.

Note

Manual is how you connect a tenant with a registration you build. Build it as these pages describe, tell Hal in chat that you built it, and paste its credential into the box he opens on Settings; he checks it with Microsoft or Google and stores it only after you confirm. The same pages document, permission by permission, what Hal-assisted onboarding creates, so you can also audit it in the customer’s console. Script builds the Microsoft 365 registration as PowerShell you can read and run.

Pick a platform

Google Workspace

Walks you through creating the GCP service account and granting domain-wide delegation Hal needs to monitor Google Workspace audit logs and Alert Center notifications.

Open

Microsoft 365

Walks you through creating the Microsoft Entra app registration and API credentials Hal needs to monitor Microsoft 365 audit logs and Entra ID sign-in events.

Open

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.

Book a walkthrough Pricing

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.