Thirty-one consoles deprovisioned in one run

How does an offboarding sweep run?

You give the companion the checklist and the departing account’s email.

It works through each console in your browser session, finds the user, stages the removal, and stops on an approval card per system showing what is about to be revoked. Systems where the user does not exist get marked clean. Okta, Google Admin and Intune are driven the same way, which suits them: they are admin interfaces, and interfaces are a companion’s home turf.

Can AI assemble an incident timeline?

This is where the native observability integrations earn their place. After an incident a companion pulls the alert sequence from PagerDuty, the metric anomalies from Datadog, the error spikes from Sentry and the deploy history from GitHub, then drafts the timeline with timestamps aligned. The tedious half of the postmortem is done before the meeting starts. The write-up pattern lives at incident postmortems, and the analysis of why it happened stays yours.

Run the license audit quarterly

A companion visits each vendor’s billing or members page in your session, records seat counts and last-active dates where the vendor shows them, and writes the lot into one sheet: paid seats, active seats, delta. The SaaS audit playbook covers the full version. The sheet flags; you cancel, because cancellation is a decision and decisions get approval cards.

What stays on the admin’s keyboard

Access approvals themselves: the judgment of whether someone should hold a permission, as distinct from the clicking that grants it. Security response past timeline assembly. Anything that changes production infrastructure state. A companion holds exactly your permissions, which on an admin account is a lot of reach, so Ask Always mode in Settings → AI permissions puts every single action behind a card. The safety model is written for readers with your instincts.

Frequently asked questions