Real Estate — Screen Workflows

End-to-end flows across the Real Estate add-on screens, including the four real cross-screen automation triggers.

Onboard the Real Estate team

Admin activates real-estate

→

Open Roles (seed 4 templates)

→

Open Staff

→

Assign roles to staff

Day-to-day brokerage flow

Add property to Catalog

→

Add client to Directory

→

Run financial/legal/marketing services

→

Publish or lease the listing

The four cross-screen automation triggers

Real Estate is not four isolated master-data screens plus twelve isolated operational screens — several screens write real records into each other on a specific status transition. Every trigger below fires on save, only on the transition into the named status (never on a no-op re-save of an already-transitioned record), and is implemented as an explicit helper call in the source, not a hidden side effect.

Source screen	Trigger	Effect
Mortgage Advisory	Status → Approved	Writes a new Authorization Agreement draft into Agreements & Listing Templates
Property Valuation	Status → Approved	Writes the certified value back onto the source property’s market value field in the Catalog
Legal Advisory & Contracts	Status enters or leaves Litigation Active	Locks/unlocks the source property as non-listable and sets/clears its Legal Hold badge in the Catalog
Virtual Tour & Drone Filming	Status → Approved & Linked	Publishes the Matterport tour URL and drone video URL onto the matching property in the Catalog
Periodic Maintenance & Repair	Status → Billed	Pushes a real vendor bill into the Finance module’s Accounts Payable

Same pattern, five places

All five triggers share one implementation pattern: compare the record’s new status against its status before the edit, and only call the cross-screen helper on the exact transition. This means re-saving an already-approved mortgage, or an already-billed work order, never creates a duplicate draft agreement or a duplicate vendor bill.

Who can do what

Action	Required capability	Typical role
Add/edit a property in the Catalog	realestate:property:manage	Real Estate Agent, Portfolio Manager
Add/edit a client or investor	realestate:client:manage	Real Estate Agent, Field Agent
Edit an agreement or listing template	realestate:agreement:manage	Real Estate Agent
Edit the services/valuation catalog	realestate:service:manage	Portfolio Manager
Give final listing sign-off	realestate:listing:approve	Broker, Portfolio Manager

Entitlement / paywall flow

Tenant lacks real-estate package

→

ModuleGuard shows Level-1 paywall

→

Admin activates package

→

Screens unlock for role-holders

Every one of the 18 Real Estate screens is wrapped in <ModuleGuard>: it needs both the tenant-level real-estate package entitlement and the signed-in user holding a REALESTATE domain role. Missing either gate blocks the screen, even for a tenant admin.

Frequently Asked Questions

What gates each step?

Each action needs its specific capability; users without it are blocked even inside the add-on, and the whole add-on additionally needs the tenant-level package entitlement.

Do the cross-screen triggers require a specific role?

No — the trigger fires for whoever has permission to save that record's status change. The write target (Agreements, Property Catalog, or Accounts Payable) doesn’t re-check the saving user’s capability on the target screen.

Where do I set up the master data used here?

On the Operational Setup screens.

Can roles be customized?

Yes — define custom Real Estate roles from the Roles screen (only REALESTATE + GLOBAL capabilities are selectable).