LinkedIn · Thu 10:00Three things we learned running our launch calendar on one desk.Two people. Every post.
Editors request approval; a different person approves, rejects or asks for changes. The server enforces it: you cannot approve your own request, and a decision once made is final.
Plan & approve
AREditor asked for approval · version 3
LinkedIn · Thu 10:00Three things we learned running our launch calendar on one desk.ApproveRequest changesReject
✕ The editor cannot approve their own request
How it works
Three steps.
STEP 01
Request
The editor sends a version for approval.
STEP 02
Decide
A different team member approves, rejects or asks for changes.
STEP 03
Locked to the version
Edit after approval and it needs approving again.
Features
What you get.
From the Reach dashboard, as it works today.
No self-approval
The person who asked cannot approve. The server refuses it.
Approve, reject or request changes
Three clear decisions, each recorded with who made it.
Final decisions
A decided approval cannot be decided again.
Tied to the exact version
Publishing checks that the approval matches the current text and media.
Roles
Viewer, editor, admin and owner, set per organisation.
Inbox
Every pending request in one list, with version and requester.
A closer look
In the dashboard.
An illustration of the screen, with sample content.
Approval requestIllustration
AREditor asked for approval · version 3
LinkedIn · Thu 10:00Three things we learned running our launch calendar on one desk. A short thread on drafting with AI and approving as a team.ApproveRequest changesReject
✕ The editor cannot approve their own request
More of Reach
The other screens.
Early access
Your channels, on one calendar.
AI drafts. A person approves. Reach publishes on time and keeps the record.