L2 internal backoffice

One tool to rule them all.

"It's better to flush one toilet instead of all." - Stanislav Podlesak, Democratic Leader of OpCo

The first screen does one job only: expose system health and require Google OAuth before the rest of the backoffice becomes available. After sign-in, this surface opens user lifecycle management, access control, group handling, and provider sync operations across all connected systems.

Users in database3
Connected syncs1/4
Operators1

System overview

Only the core operational signals belong on the landing page.

Users in DB3

Authoritative internal record count currently tracked by the backoffice.

Healthy syncs1

Integrations currently reporting healthy synchronization posture.

Degraded syncs2

Integrations that need attention but are not fully blocked.

Blocked syncs1

Integrations currently considered unsafe or blocked for write automation.

Integration sync status

Current state of each provider connection visible before login.

Google Workspace

SSO • user lifecycle • aliases • groups • directory sync

Sync activeImplement Auth.js Google provider and directory read sync with admin APIs.

Slack

invite users • deactivate users • channel defaults • profile sync

Sync degradedConnect bot token and map team-specific channels into templates.

Atlassian Cloud

org membership • groups • product access • project roles

Sync degradedModel access templates by team and split Jira versus Confluence permissions.

GoodAccess ZTN

user creation • group assignment • policy visibility

Sync blockedVerify API coverage, then add safe create and revoke operations with audit logging.