> ## 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.

# Organisation and branches

> How the property hierarchy is structured — organisation, branch, block, unit — and why branch scope matters everywhere.

**Organization → `/organization`** · **Admin → Blocks → `/blocks`**

Everything in Nyumba Zetu sits in a hierarchy. Understanding it explains most "why can't I see
this?" questions.

```
Organisation
 └── Branch (property / scheme / region)
      └── Block (building or estate)
           └── Unit
                └── Lease
                     └── Resident
```

## The levels

| Level            | What it is                                                                                             | Where it is managed                |
| ---------------- | ------------------------------------------------------------------------------------------------------ | ---------------------------------- |
| **Organisation** | Your company on the platform. Owns branding, settings, users, the chart of accounts, and every branch. | Settings                           |
| **Branch**       | An operating unit — a property, scheme, region or office. The scope for lists, KPIs and reports.       | Organization / Settings → Property |
| **Block**        | A building or estate holding units.                                                                    | Admin → Blocks                     |
| **Unit**         | The billable physical space.                                                                           | Admin → Units                      |

<Warning>
  **Branch scope is not a filter.** Data outside your active branch is not returned to you at all.
  When something "disappears", check your branch before anything else.
</Warning>

## The organisation landing page

`/organization` gives an organisation-level view above branch scope: headline KPIs for the current
month, and cards for properties, owners, portfolios, units, tenants and leases. It is the starting
point for someone who works across branches rather than inside one.

## Branches

A branch is where operational reality lives. Each branch has:

* its own units, leases, residents and money;
* its own settings overrides, where they differ from the organisation default;
* its own feature flags — a module can be live in one branch and off in another;
* its own users, or shared users scoped to several branches.

### Switching branch

The branch you are working in is named at the top of the sidebar. Switch it before you start a
task, not halfway through.

## Blocks

A block groups units within a branch — usually one building or one estate.

<Steps>
  <Step title="Create the block">
    **Admin → Blocks → Add.** Name, address, and the branch it belongs to.
  </Step>

  <Step title="Add units to it">
    See [Units](/guides/units).
  </Step>

  <Step title="Use it for reporting">
    Most financial reports can group by block, which is usually the level a manager actually
    thinks in.
  </Step>
</Steps>

## Portfolios

Portfolios cut across the hierarchy: a set of units or blocks grouped for reporting, assignment or
owner purposes, without changing where they physically sit. See [Portfolios](/guides/portfolios).

## Settings inheritance

Configuration resolves down the hierarchy, most specific wins:

```
lease → unit → block → branch → organisation → platform default
```

This is how one scheme can run a stricter collections ladder, a different late-fee policy or a
different billing day without duplicating every other setting. See [Settings](/guides/settings).

## Multi-tenancy and branding

The platform is white-label. Each organisation sets its own primary colour, logo and product name,
which are applied at runtime across the app and outgoing documents. Financial status colours —
green paid, red arrears, orange due soon, blue informational — are fixed for every organisation so
numbers read the same way everywhere.

## Organisation settings

Under **Settings**, administrators manage:

| Area               | Contents                                                                             |
| ------------------ | ------------------------------------------------------------------------------------ |
| **Account**        | Organisation identity and contact details.                                           |
| **Property**       | Branch and property configuration.                                                   |
| **Team / Roles**   | Users, roles and branch assignments. See [Users and roles](/guides/users-and-roles). |
| **Notifications**  | What the platform sends, and to whom.                                                |
| **Security**       | Access and session controls.                                                         |
| **Plan & billing** | Subscription details.                                                                |
| **Jobs**           | Scheduled background processes. See [Scheduled tasks](/guides/scheduled-tasks).      |
| **Notice**         | Organisation-wide notices.                                                           |
| **Version**        | The running release.                                                                 |

## Super Admin surfaces

Platform staff have cross-organisation tooling: **Companies** (all organisations),
**Properties**, **User Sessions**, and [Platform Health](/guides/platform-health). These are not
visible to organisation administrators.

## Common problems

| Symptom                                            | Cause                                                                                 |
| -------------------------------------------------- | ------------------------------------------------------------------------------------- |
| A lease, invoice or payment is missing from a list | Wrong branch.                                                                         |
| A report total is lower than expected              | The report is branch-scoped and you are in one branch of several.                     |
| A module is missing for one branch only            | Feature flag set per branch. See [Feature flags](/guides/feature-flags).              |
| A setting change had no effect                     | A more specific scope is overriding it. Check block, branch and unit-level overrides. |