Know exactly what a leaver still has access to.
One place for IT and HR to see who holds which software seat, revoke all of them on the leaving date, and stop answering the same handbook question every week.
Licences and access
- A real seat count. Register each tool with how many seats you pay for. Assigning past the limit is refused, so you find out before the invoice does.
- Joiners. Onboard a person once and assign their seats from one screen instead of five admin panels.
- Leavers. Offboarding releases every seat that person held, in one action, and records what was released.
- A nightly safety net. A daily sweep catches seats still assigned to people who have already been offboarded — because somebody always gets missed.
- A report you can hand to finance. Seats paid for versus seats actually assigned, per tool.
Handbook answers, inside Teams
Upload your policies once. Staff ask in a Teams channel and get an answer with the section it came from, so they can check it themselves.
Search that works without AI
Handbooks are split into passages and indexed. Even with no AI configured, a question returns the most relevant passages and the documents they came from. This part is always on and costs nothing.
A written answer, if you want one
Add an API key for any OpenAI-compatible model and the top passages get turned into a short written answer that cites its sources. If the model is slow or fails, it quietly falls back to the passages — it never blocks the reply.
No bot registration needed
It runs on a Teams outgoing webhook, so there is no Azure Bot resource to provision and nothing to pay for. Every request is verified with the security token Teams issues.
Answers stay inside your documents
The model is instructed to answer only from the passages it is given and to cite them. If your handbook does not cover something, it says so rather than inventing a policy.
What it does not do
- It is the tracking and audit record, not a provisioning robot. It does not reach into Google Workspace, Slack or GitHub to delete the account for you — each of those needs its own integration, and we have not built them.
- Handbook upload takes pasted text or Markdown today. PDF and Word parsing is not in yet.
- Teams outgoing webhooks only work in channels, with an @mention. No one-to-one chats.
- If you turn on the AI answer, handbook passages are sent to whichever model provider you configure. Read their data terms first — we will point you at them.
Free while we are in early access
Useful from about ten people upwards. Setup is a form and a Teams webhook.