Living Consent: one approval as a shared state
Not “owning a PDF”, but sharing the same state: status + history, without an account for the other person. Ideal when uses can change (portfolio, social media, advertising) and you don’t want to guess later what applies.
Shared state
History instead of versions
No account needed
Link shareable/rotatable
What does “Living Consent” mean?
In everyday language this is often called “consent” or “release form”. At its core it’s something simple: both sides should always see the same, current state.
- Status: active / restricted / revoked / pending
- Scope: e.g., portfolio, social media, advertising
- History: what changed when (without “PDF_version_7_final_final”)
The aha: file vs reference point
Today (typical)
- PDF/chat screenshot is stored somewhere
- Changes happen “on the side”
- Later unclear: which version applies, for what exactly?
Living Consent
- One link = one shared state
- Changes are visible and documented in history
- You always know what applies — without guessing
How it works (in ~60 seconds)
1
Start an approval
Choose a template (e.g., photo shoot/event/social media) — you can adjust later.
2
Share the link
The person opens it in the browser. No account needed.
3
Check the state & (if needed) adjust
Changes are visible immediately — and traceable in the history.
Mini example (how it feels)
Before
Portfolio: allowed · Social: restricted · Advertising: not allowed
Portfolio: Allowed
Social: Restricted
Advertising: Not allowed
After
Social becomes allowed → both sides see the same new state
Portfolio: Allowed
Social: Allowed
Advertising: Not allowed
Important: you don’t have to “document more”. The history is created automatically — as a shared, calm reference.
Get started
If you want: start an approval and send the link to the person. Afterwards you’ll know in seconds whether everything is “all good”.