Why approvals are magic links, not another login
Every publishing tool eventually sells to an agency, and every agency hits the same wall: the client wants to approve posts before they go out, but will not install your app, will not remember a password, and will not join your 'workspace'. If your approval flow requires a login, the workflow silently moves back to email.
The shape of the link
Each approval request mints a single-use-scoped URL: /approve/{token}. The token maps to one post, one workspace, one expiry. The reviewer opens it and sees the post exactly as it will render — target accounts, schedule, full text — plus approve and reject buttons and an optional note field. No session, no password, no app.
Server-side discipline
The approval decision is a real status transition, not a UI gesture. approve/reject writes through the same endpoint the dashboard uses, which means an agent can hold a post in review, a human can clear it from a link, and both end up in the same state machine: pending → approved → scheduled → published.
What we deliberately didn't build
No public comment threads, no per-reviewer identity, no 'sign in to see why'. The link IS the authority — if you have it, you can decide. That keeps the page fast, the security model obvious, and the agency demo about thirty seconds long.