Build a multi-asset review hub with guided Automation — Needs Review Work Queue, Decision writeback, company tenancy, and preference-gated notifications. No power-user JSON.
Shipped 9 Aug 2026 Uses guided Workflow controls from the 9 Aug 2026 Release.
A Needs Review Work Queue spanning multiple asset sheets.
A Decision screen with Approve / Reject / Request changes → Notion statuses (+ optional attachments).
Company tenancy so two users at Company A never see Company B.
Preference-gated notifications into Notification Center.
Private OTP app; Users sheet with Role and a Client (or company) relation.
Asset databases with the Status options you want to write.
Workflow + Messaging entitlements.
Open App audience & notification prefs:
Tenant mode → Relation → users-sheet Client.
Role field → Role.
Add a notification category (for example reviews).
Save.
Details: Configure App Audience and Notification Prefs.
Add a Work Queue; name it Needs Review.
Listen scope: Entire app (or the workflow that opens decisions).
Include sheets → select your asset sheets.
Put it first in the drawer for Client roles.
Add a Decision screen.
Map outcomes to Status (for example approved → Approved by Client).
Optionally require a reason and enable file attachments.
Bind Submission review / overview fields when helpful.
Fastest path: Workflow templates → Send to Needs Review (status-changed → publish Decision/Task → wait on reply topics → branches). Remap Change status fields to your Status options.
Use role pool or audience routing — never pin persona emails in live steps.
Move an asset to the “ready for client” status as staff.
Log in as the client → Needs Review shows the item.
Open Decision → Approve (attach a file if enabled) → Notion Status updates.
Confirm a second company’s client cannot see the item.
