> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nyumbazetu.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Admin console
> The super-admin control center — platform-wide operational, audit and configuration streams across every organisation.
**Administration → Control Center → `/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 control center is restricted to super administrators. Its lists contain data from every
organisation on the platform, including names, amounts and contact details. Access is a
platform-level grant, not an organisation role — see [Role grants](#role-grants).
## The three sections
| Section | Question it answers |
| -------------------- | --------------------------------------------------------------- |
| **Operations** | Did the background work run, and what did it produce? |
| **Audit & Security** | Who did what, who was signed in, and who holds elevated access? |
| **Configuration** | What is configured, where it is overridden, and what ages out. |
## Operations
Every run-log the platform produces, in one place.
| Stream | What it shows |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Allocation Runs** | Allocation-engine runs including previews — what was allocated or reverted, when, by whom. See [Allocations](/guides/allocations). |
| **TPS Generation Runs** | Schedule and invoice generation runs, with correlation ids and per-action counts. |
| **Scheduled Task Runs** | Job execution history platform-wide. See [Scheduled tasks](/guides/scheduled-tasks). |
| **Upload Runs** | Every bulk-upload run: what was imported, what it produced, and any failure. See [Bulk upload](/guides/bulk-upload). |
| **Retention Sweeps** | Every retention run, and in shadow mode what it *would* have removed. See [Data retention](/guides/data-retention). |
| **IoT Billing Runs** | Utility billing batches and their per-unit results. |
| **Integration Jobs** | The outbound provider-submission queue: every job, its retries, and its failures. |
| **Tax Documents** | Every tax submission: fiscalisation state, retries, and the receipt returned. See [Tax and eTIMS](/guides/tax-and-etims). |
| **Broadcasts** | Every bulk message run: audience, channel, and delivery outcome. |
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
| Stream | What it shows |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| **Audit Events** | The append-only record of who changed what, where, and why. See [Activity log](/guides/activity-log). |
| **Auth Events** | Sign-ins, failures, impersonation and session revocations. |
| **User Sessions** | Active and historical sessions. See [Users and roles](/guides/users-and-roles). |
| **Impersonation** | Every "View as…" session: which operator viewed which workspace, why, and for how long. |
| **Role Grants** | Every admin-tier grant: who holds it, on which node, and since when. |
### 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.
Review it on a cadence. A grant with no current owner — someone who has left, or a temporary
escalation never withdrawn — is the most common finding.
## Configuration
| Stream | What it shows |
| ----------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Setting Definitions** | The catalog of configurable settings. See [Settings](/guides/settings). |
| **Setting Overrides** | Where a setting is overridden, at which scope, and to what value. |
| **Retention Policies** | What ages out of which table, after how long, and whether armed. See [Data retention](/guides/data-retention). |
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
The console's value is the cross-tenant view. If you already know the organisation, work inside it.
Missing runs matter more than failed ones — failures are already surfaced locally.
Most streams are read-only by design. Fix the cause in the owning module.
Both are access questions, and both drift quietly.
## Common problems
| Symptom | Cause |
| ------------------------------------- | ------------------------------------------------------------------------------------ |
| A page is empty or bounces | You are not a super administrator; the console needs a platform-level grant. |
| A run is missing for one organisation | The job's per-organisation switch is off, or fairness rotation did not reach it. |
| Integration jobs pile up | Provider credentials or mappings are wrong for that organisation, not a queue fault. |
| A setting behaves unexpectedly | An override at a narrower scope is winning. Check the override list. |
| Retention sweeps remove nothing | Shadow mode — see [Data retention](/guides/data-retention). |
## Related
The audit trail in depth.
Policies, sweeps, and the arming model.
Automated detection of data problems.
Definitions, overrides, and the scope chain.