Review staff, property and stakeholder access after the merger
Retain least-privilege roles and verify record relationships after an upgrade.
Before you start
Retain least-privilege roles and verify record relationships after an upgrade. A matching display name does not establish ownership.
Follow these steps
- Review existing property, owner, agent, broker, request, tenant, reporting and compliance grants.
- Grant Property Maintenance and Property Payouts capabilities only to the relevant staff.
- Check explicit tenant creation/deletion privileges where needed.
- Verify authoritative property-client and staff ownership/assignment relationships.
- Test a permitted property and an out-of-scope record using the intended staff account.
- Review client contact access separately from staff permissions.
Check it worked
Each person can perform the intended action on the intended records and cannot infer access solely from a name or old link.
If something does not look right
Records without an authoritative relationship can be hidden from scoped staff. Repair the relationship using the normal module controls instead of widening access globally.
Questions and answers
Does the merger grant new permissions automatically?
Existing grants are retained; new maintenance, payout and tenant capabilities require an explicit role decision.
Is an owner record the same as a portal account?
No. Check the linked CRM customer/contact identity and property relationship.
Does Flow permission replace these grants?
No. Flow intersects its permissions with native domain and object access.