Help
Short answers, no screenshots to go stale. Can't find it? Ask a human — we read everything.
Your first scan, in about 4 minutes
Sign up, connect your directory, pick your stack — and get the report that says what's leaking.
Why Google Workspace or Microsoft 365 connects first
Your directory is the source of truth. Every tool's seats are checked against it — never the other way around.
Ghosts, dormant seats and unused licenses, explained
What each finding type means, how the euro amounts are estimated, and when we honestly say 'unknown'.
Which tools Stackleaks scans, and what each needs
OAuth consent, an admin API key, or a CSV — the connection method per tool, and who needs to click.
The CSV routes: no OAuth, still a real report
Upload a users export instead of connecting — for the cautious, and for tools without an API (looking at you, Claude Team).
Snoozing and ignoring findings
Service accounts and deliberate seats aren't leaks. Teach the report once; your verdicts stick across every re-scan.
The free Scan vs Monitor
The report is free and complete. Monitor adds the watching: nightly re-scans, same-week ghost alerts, and history.
How billing works
Priced by team size measured from your directory, never per seat. Band changes come with a heads-up and a month of grace.
Disconnecting, and what happens to your data
Disconnect = deletion, immediately. What we revoke, what we delete, how long backups linger, and how to ask for more.
Connection troubleshooting
Needs-attention states, wrong key types, admin requirements, partner-managed portals — the greatest hits and their fixes.
Atlassian: creating the API key, step by step
Organization settings → API keys, the one scope to tick, and where your org ID hides.
Zoom: adding, using and removing the app
The full lifecycle guide for the Zoom integration.
What we can and cannot see
Every connector's exact read-only scopes, generated from the code itself so it can't drift.
Nothing matches — try another word, or ask support.