Properties
Rentals and associations
Abode can support straight rental operations, straight association operations, or a mixed portfolio. The important part is using the right entity model so dues, violations, architectural requests, and owner-facing outputs stay coherent.
Rental workflows
Leases, maintenance, balances, rent collection
Association workflows
Dues, violations, architectural requests, committees
Mixed portfolio benefit
One operating system instead of parallel tools
Choose the right entity type
Rental and association operations overlap, but not enough to justify forcing them into the same shape.
| Use case | Use a property | Use an association |
|---|---|---|
| Residential rental with leases and tenant balances | Yes | No |
| Community dues and HOA compliance | No | Yes |
| Board committees and architectural reviews | No | Yes |
| Owner distributions tied to rental income | Yes | No |
Association-specific operational APIs
Violations and architectural requests are first-class association workflows, not afterthought notes on a property record.
/api/dashboard/associations/all-violationsCreates and manages violation records across association entities.
- Authentication
- Management dashboard session with association write access
- Constraint 1
- The app also supports association-specific routes scoped to a single association.
- Constraint 2
- Violations can carry fine amounts, deadlines, and stage updates.
- Constraint 3
- Architectural requests follow a parallel CRUD pattern for review workflows.
Request examples
{
"associationId": "assoc_01J8V2WQZP6M1N1K52HZ0ZB9B8",
"unitId": "assoc_unit_204",
"title": "Exterior paint change without approval",
"description": "Owner repainted the front door without ARC approval.",
"fineAmount": 150,
"deadline": "2026-04-30"
}Response examples
{
"id": "viol_01J8V31P8Y9S10MCMZ3Y6K4V0T",
"stage": "OPEN",
"title": "Exterior paint change without approval",
"fineAmount": 150,
"deadline": "2026-04-30"
}- Use associations when compliance history needs to be visible over time.
- Keep architectural requests separate from violations so approvals and enforcement do not collapse into one queue.
- Expose only the participant-facing actions that belong in the association portal.