Landlord Portal Decision Real-Time Notifications

Introduced in: v0.1.279

Overview

When a landlord reviews a portal invite and makes a decision — either approving it or requesting changes — the sending agent and all organisation admins are now notified immediately, both in-app and by email.

This replaces the previous behaviour where notifications were batched and delivered by the landlord-portal-invite-sweep daily cron, meaning recipients could wait up to 24 hours to learn of a decision.

How It Works

Trigger

The notification is event-driven. It fires when the decidedAt field is set on a landlordPortalInvite record, signalling that the landlord has made a decision.

Decision outcome	Trigger fires?
`approved`	✅ Yes
`changes_requested`	✅ Yes
Pending (no decision yet)	❌ No

Who Is Notified

The agent who sent the landlord portal invite.
All organisation admins in the sending agent's organisation.

Notification Channels

In-app notification — appears immediately in the platform UI.
Email — sent immediately to the relevant recipients.

Affected Entities

Entity	Role
`landlordPortalInvites`	Source record; `decidedAt` field triggers the event
`depositReleases`	Associated deposit release linked to the invite
`notifications`	In-app notification records created on trigger
`auditLog`	Event is written to the audit log for traceability

Before vs. After

	Before v0.1.279	From v0.1.279
Delivery mechanism	Daily cron (`landlord-portal-invite-sweep`)	Event-driven trigger
Maximum notification delay	Up to 24 hours	Immediate
Channels	Email only (via cron)	In-app + Email
Recipients	Sending agent	Sending agent + all org admins

Notes

The daily landlord-portal-invite-sweep cron continues to run for other sweep responsibilities unrelated to decision notifications.
No configuration is required — the event trigger is active automatically for all organisations.
All notification events are written to the auditLog for compliance purposes.