Questions, answered plainly

Both, in that order. Estate and facility operations are what an estate adopts on day one. The residential record accumulates as a result — generated by normal operational work rather than by separate data entry.

Estates run day-to-day operations in the facility portal. Residents get a dedicated mobile app, and gate personnel get a focused security client that exposes only what a visit check requires.

No. Estates typically start with residents, properties and collections, then turn on visitor access and issue reporting. The modules share one estate record, so adding one later does not require re-entering anything.

Estates onboard first and invite their residents, so your invitation comes from your facility manager. If your estate is not on the platform, point whoever runs it our way.

It stays with the resident. An estate has a membership relationship with a resident for a period of time; it does not own that person's housing history. Moving creates a new tenancy on the same residential profile rather than starting a new identity.

Every record carries the source that supports it, and that source is always visible — as an icon and a label, never as colour alone. A landlord-confirmed tenancy, a document-backed one, a platform-recorded payment and a resident declaration each look different, deliberately.

Not automatically. Estate roles are scoped to the estate. History from other estates sits outside that boundary unless the resident explicitly shares it.

The Passport assembles verified tenancy and payment records into a summary a resident chooses to share. It is generated from source records rather than maintained separately, so it cannot drift from the evidence behind it.

No. Rental payment data is not shared with credit bureaus, and nothing in the product is a credit score. Any future arrangement would involve a licensed partner and the resident's explicit consent.

In private storage behind authorization. Documents are never published to permanent public links, and access is checked on the server rather than assumed from the client.

Users get role assignments with a scope — an estate, a set of properties, or a platform-level function — and permissions are calculated from that rather than from one global role field. What the interface shows is a convenience; the server enforces the real boundary.

Pricing is set per estate, based on unit count and the modules you turn on. We quote against your actual structure rather than a generic table, so it comes up in the first conversation.