Tenant Portal

Give tenants one place for rent, maintenance, documents, notices, building updates, and account details. This example brings Home and Payments together so property teams can find the next task without losing context.

It includes representative records such as October rent due and Leak repair scheduled. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Tenant Portal
Use this template in Figr

Template facts

Screen

Workspace

Primary action

New request

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new request while keeping next rent, open requests and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Home gives users an obvious place to start.
  • Supporting view: Payments keeps the related context close.
  • Primary action: New request stays visible when people need it.
  • First signal: Next rent shows a useful value (2,450).
  • Second signal: Open requests gives additional context (2).
  • Sample record: October rent due.
  • Next record: Leak repair scheduled.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Home → Payments → New request → Review outcome

Patterns used

Workspace, Home, Payments, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to home and payments. People need to distinguish October rent due from Leak repair scheduled. Keep next rent visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “New request”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Maintenance Requests, Property Manager Dashboard, Lease Management.

Start from this in Figr

Design a tenant portal screen inside our existing product. Use our current components, tokens and content language. Include Home and Payments views, credible records like October rent due, and a clear “New request” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr