Registration & invites
How residents onboard and tie accounts to units.
Overview
Residents typically arrive through mobile registration flows exposed under /registration/* on Core (not the admin REST CRUD). Property managers prepare data via admin APIs (users + units), then residents complete signup in the app or portal.
Moving pieces
- Tenant / property / unit exist and
unitLabelmatches what the resident expects. - User row may be pre-created or created during signup (depends on workflow).
- Device registration follows successful login so pushes can reach the handset.
Admin-side prep
Use:
/api/admin/units— ensure correct property linkage and virtual number/api/admin/users— seed or update resident emails / phones
Deep links & email
Marketing or property sites may deep-link into the app with tokens; implementation lives in mobile + portal code under tools/. Coordinate query parameters with product before documenting externally.
Auditing
Use /api/admin/audit to trace administrative changes that affect resident access during disputes or compliance reviews.