How the OwnerTabs dashboard works

The dashboard is for action. It’s the fastest way to go from “something needs attention” to the correct property context — without digging through email threads or folder trees.

Who this is for

Anyone logging in to do work (log an issue, upload a doc, update a property).
Teams who need a consistent starting point for property ops.
Portfolio managers who switch properties all day.

How to use it

Use the dashboard to pick the next action (don’t store info there).
If you know the property, click into it first — then create incidents/records/files inside that context.
Close loops: when something is resolved, write the one-line outcome so it’s searchable later.

Key workflow

Step 1 — Scan: what’s open / in progress (incidents, recent activity, quick actions).
Step 2 — Enter context: choose the right property/unit before you attach anything.
Step 3 — Do the work: incident (event), record (knowledge), file (artifact), contact (vendor).
Step 4 — Finish: update status + add the resolution (so “done” is documented).

How to think about property context

The dashboard is a launchpad. The property is the workspace. If you attach work before picking the property, things drift into the wrong place (or nowhere).

A good default: property first, then action.

Practical example (30 seconds)

A guest reports a leak at one unit:

Dashboard → open the property/unit.
Create an incident → add photos, timeline, and who you contacted.
Attach invoice/photo as files.
Close the incident + add a record: “what fixed it.”

Result: next time it happens, you can find the full story in seconds.

Rule of thumb

If you can’t answer “which property is this for?” you’re not ready to create the incident/record/file yet.

Next guide

Next, see how this exact system scales from 1 property to 100+.

OwnerTabs for any size portfolio