One source of truth across HR, Google and Entra

Most access problems aren't malicious — they're drift. A person changes teams, an account lingers, a spreadsheet goes stale. The fix is to make one system authoritative and let everything follow it. The problem Before: identity lived in three places. HR had one version of a person, Google another, Entra a third — and Atlassian did its own thing. Every mismatch was a small risk and a recurring support ticket. The design * One authoritative record per person (HR / Entra) * Automated sync t

Published on

Most access problems aren't malicious — they're drift. A person changes teams, an account lingers, a spreadsheet goes stale. The fix is to make one system authoritative and let everything follow it.

The problem

Before: identity lived in three places. HR had one version of a person, Google another, Entra a third — and Atlassian did its own thing. Every mismatch was a small risk and a recurring support ticket.

The design

  • One authoritative record per person (HR / Entra)
  • Automated sync to Google Workspace and Atlassian
  • Role-based groups that drive access everywhere
  • Zapier workflows to reconcile changes and flag exceptions

The result

Now a change happens once and propagates. No orphaned accounts, no "which system is right?", and access that maps cleanly to roles — which makes audits boring, in the best way.