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

# Tenant portal

> What residents can do for themselves — bills, payments, requests, documents and profile.

**`/tenant-portal`** (resident-facing)

The tenant portal is the resident's view of their own tenancy. Residents never see the operator
app; they see their units, their money, and their requests.

<Note>
  Everything a resident does in the portal lands in the same records your team works from. A service
  request raised in the portal appears in your [service requests](/guides/service-requests) list; a
  payment appears in [Payments](/guides/payments-receive-pay). There is no separate inbox to watch.
</Note>

## What residents see

| Area                         | Contents                                                                                                      |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Home**                     | Balance due (or *no balance due*), recent activity, and quick actions.                                        |
| **Pay**                      | Payment methods and the payment flow.                                                                         |
| **Invoice / statement view** | Bills with allocation details — tapping a line shows how a payment was applied.                               |
| **Requests**                 | Raise and track service requests.                                                                             |
| **Documents**                | *My documents* — anything shared with them, plus their own uploads.                                           |
| **Profile**                  | *My profile* — personal details, phone, email, emergency contacts, ID verification, notification preferences. |
| **Readings**                 | Submit meter readings, where the property uses resident-submitted readings.                                   |
| **Switch unit**              | Residents holding more than one unit move between them.                                                       |

## Balances and allocation transparency

The portal shows the resident's balance and, crucially, **how their money was applied**. A payment
that settled three invoices shows all three. This single feature removes most "I paid, why do you
say I owe" conversations before they reach your team.

Transaction types the resident sees include invoices, payments, credits, adjustments and refunds —
each with its date, amount and effect on the balance.

## Raising a service request

Residents choose a **category** and **subcategory** and describe the problem. Categories cover the
common cases directly — plumbing (leak, blocked drain, no hot water), electrical (power outage,
lighting), HVAC (no cooling), appliances (fridge), doors, cleaning, pest, noise, safety concerns,
inspections and general.

Structured categories matter: they route the work and make maintenance reporting meaningful in a
way that a free-text box never does.

<Steps>
  <Step title="Resident submits">
    With category, description and photos.
  </Step>

  <Step title="It lands in your queue">
    Triage and assign it like any other request.
  </Step>

  <Step title="Keep them updated">
    Status changes and closure should reach the resident. See
    [Communications](/guides/communications).
  </Step>
</Steps>

## Payments

Residents pay through the portal against the accounts you have exposed to payers. Which bank
accounts appear as payment destinations is your configuration — review it whenever you add an
account. See [Bank accounts](/guides/bank-accounts).

<Warning>
  A payment received is not a settled invoice until it is
  [allocated](/guides/allocations). A resident who paid and still sees a balance is usually looking
  at an unallocated payment, not a system error.
</Warning>

## Notices, polls and amenities

Where enabled, residents also see published [notices](/guides/notices-and-polls), vote in polls,
and book [amenities](/guides/amenities) within the access policy you set.

## Giving a resident access

Portal access follows the [resident record](/guides/residents) and the units it is associated with.
A resident with two units sees both and can switch between them.

<Steps>
  <Step title="Check the resident record">
    A valid email is required; the phone number drives SMS notifications.
  </Step>

  <Step title="Confirm the unit associations">
    Access is derived from them. Stale associations show units the resident no longer holds.
  </Step>

  <Step title="Invite them">
    Then confirm they can sign in and see the right units.
  </Step>
</Steps>

## Supporting portal users

| Resident says                         | Check                                                                          |
| ------------------------------------- | ------------------------------------------------------------------------------ |
| "I can't sign in"                     | Email on the resident record; whether the record is active.                    |
| "I paid but it still shows a balance" | Whether the payment is allocated.                                              |
| "I see a unit I moved out of"         | The association's end date.                                                    |
| "I never got my invoice"              | [Delivery Tracker](/guides/communications) — sent is not delivered.            |
| "My request was never actioned"       | The request in your queue — usually unassigned rather than lost.               |
| "I can't see my statement"            | Whether statements exist for the period, and the resident's unit associations. |

## Public surfaces

Two resident-facing flows sit outside the portal login:

* **Apply** (`/apply`) — the public lease application form. See
  [Lease applications](/guides/applications).
* **Acknowledgement and signature links** — secure single-use links for acknowledging a letter or
  signing a document, sent by email. See
  [Documents and templates](/guides/documents-and-templates).