Get started
Overview
Abode is a property operations platform organized around the work a management company actually runs every day: portfolio modeling, maintenance execution, leasing, communication, payments, accounting, trust compliance, and reporting.
Surfaces
Management dashboard, owner portal, tenant portal, vendor portal
Portfolio scope
Rentals and associations in the same org
Workflow spine
Properties → operations → accounting → reporting
Context
The management dashboard stays operationally centered: each area feeds the next one.
Choose the right operating surface
Different users belong in different Abode surfaces. That separation keeps permissions, navigation, and outputs clean.
| Surface | Primary users | What it owns |
|---|---|---|
| Management dashboard | Property managers, accounting teams, admins | Portfolio control, maintenance, leasing, communication, accounting, and reports |
| Owner portal | Landlord clients and portfolio owners | Statements, distributions, property visibility, and portfolio totals |
| Tenant portal | Residents | Payments, balances, maintenance requests, and documents |
| Vendor portal | Assigned service providers | Work orders, quotes, schedule updates, and payment visibility |
Why the split matters
Abode is not a single dashboard with role flags sprinkled in. Each surface is intentionally scoped so portfolio data can stay shared while actions remain role-specific.
Stand up the portfolio model first
Most downstream issues come from weak portfolio records, not from the workflows that sit on top of them.
- 1Create properties, units, and owners before enabling operational workflows.
- 2Decide whether the org manages only rentals, only associations, or a mixed portfolio.
- 3Confirm who belongs in management, owner, tenant, and vendor roles before sending invites.
- 4Connect banking and collection rails only after the structural records are correct.
- 5Use reports and statements last, after operating data is flowing cleanly.
What the platform expects to be true
The strongest Abode implementations keep the data model explicit and predictable.
- A property or association should exist before leases, violations, or communications get attached to it.
- Tenant balances, owner statements, and trust ledgers only stay credible when payment and expense events are tied back to the right portfolio record.
- Operational messages are most useful when they stay attached to a work order, lease, property, or portal-visible object.
- Recurring reporting becomes valuable only after saved views and delivery patterns are standardized.