/admin
Every other page in Nyumba Zetu is scoped to your organisation and branch. The control center is not:
it reads across the whole platform, in one list, with no branch or unit picker. It exists to answer
operational questions that stop at no single tenant — did that job run everywhere?, who has admin
anywhere?, which submissions are stuck?
The three sections
Operations
Every run-log the platform produces, in one place.
The useful pattern here is absence, not error. A job that failed is visible in its own module. A
job that never ran for one organisation out of a hundred is only visible from a platform-wide list.
Integration jobs
The submission queue that carries documents to external providers. A job that keeps retrying is usually a credential or mapping problem at the organisation level rather than a transient outage — check the failure reason before requeuing, and fix the mapping rather than the job.Audit & security
Auth events
Sign-in outcomes across the platform. Read it for patterns, not individual lines: repeated failures against one account, successful sign-ins from an unexpected location, or a burst of revocations.Impersonation
Support work sometimes needs an operator to see exactly what a user sees. Every such session is recorded with its operator, its target workspace, its stated reason and its duration. Impersonation is a normal support tool; an impersonation session with no reason, or one that runs unusually long, is the thing to ask about.Role grants
This is the definitive answer to “who has admin?”. Organisation-level user lists show roles inside one
organisation; only this stream shows elevated grants across every node on the platform.
Configuration
Overrides are where unexplained behaviour usually hides: a value set at branch or unit scope years ago
that still wins over the organisation default. The override list shows the scope chain resolved, so
you can see which level actually applies.
Using the console well
1
Start from the stream, not the organisation
The console’s value is the cross-tenant view. If you already know the organisation, work inside it.
2
Look for gaps
Missing runs matter more than failed ones — failures are already surfaced locally.
3
Read before you act
Most streams are read-only by design. Fix the cause in the owning module.
4
Review grants and impersonation on a schedule
Both are access questions, and both drift quietly.
Common problems
Related
Activity log
The audit trail in depth.
Data retention
Policies, sweeps, and the arming model.
Platform health
Automated detection of data problems.
Settings
Definitions, overrides, and the scope chain.