Property & Compliance Management

Review Real Estate stored tables

Understand that separate tables store properties, owners, client links, requests, onboarding, maintenance, suppliers, invoices, payouts and notifications.

Reviewed 27 October 2026Merged module 2.1.3
Where to goDatabase-backed module workspaces

Before you start

Use the account and administrative authority appropriate to the data. Retention and legal holds are separate from routine record editing.

Follow these steps

  1. Identify the account, record type and evidence affected by this task.
  2. Understand that separate tables store properties, owners, client links, requests, onboarding, maintenance, suppliers, invoices, payouts and notifications.
  3. Access through supported UI/lifecycle; do not edit tables directly for normal operations.
  4. The relevant access, retention or evidence control has a verified result.

Fields, rules and limits

  • Access through supported UI/lifecycle; do not edit tables directly for normal operations.

Check it worked

The relevant access, retention or evidence control has a verified result.

If something does not look right

If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.

Questions and answers

What should I verify for this task?

Access through supported UI/lifecycle; do not edit tables directly for normal operations.

Why is the record or action unavailable?

Use the account and administrative authority appropriate to the data. Retention and legal holds are separate from routine record editing. Check the current company and record relationship before requesting additional access.