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

LevelWhat it isWhere it is managed
OrganisationYour company on the platform. Owns branding, settings, users, the chart of accounts, and every branch.Settings
BranchAn operating unit — a property, scheme, region or office. The scope for lists, KPIs and reports.Organization / Settings → Property
BlockA building or estate holding units.Admin → Blocks
UnitThe billable physical space.Admin → Units

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.

  1. Create the block

    Admin → Blocks → Add. Name, address, and the branch it belongs to.

  2. Add units to it

    See Units.

  3. Use it for reporting

    Most financial reports can group by block, which is usually the level a manager actually thinks in.

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.

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.

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:

AreaContents
AccountOrganisation identity and contact details.
PropertyBranch and property configuration.
Team / RolesUsers, roles and branch assignments. See Users and roles.
NotificationsWhat the platform sends, and to whom.
SecurityAccess and session controls.
Plan & billingSubscription details.
JobsScheduled background processes. See Scheduled tasks.
NoticeOrganisation-wide notices.
VersionThe running release.

Super Admin surfaces

Platform staff have cross-organisation tooling: Companies (all organisations), Properties, User Sessions, and Platform Health. These are not visible to organisation administrators.

Common problems

SymptomCause
A lease, invoice or payment is missing from a listWrong branch.
A report total is lower than expectedThe report is branch-scoped and you are in one branch of several.
A module is missing for one branch onlyFeature flag set per branch. See Feature flags.
A setting change had no effectA more specific scope is overriding it. Check block, branch and unit-level overrides.