Share consent via link (no account)
You share a link via chat, email or as a QR code — and the other person confirms directly in the browser. No app, no account. In the project, consent is documented as received. The exportable proof is created only when you finalize.
When is this useful?
- Before publishing (social, website, advertising)
- On-site (show the link or as QR)
- Teams (one consistent flow instead of “everyone does it differently”)
How to share the link
- Create a project (or open an existing one).
- Open “Share approval”.
- Copy the link and send it (chat/email).
- The person opens the link and confirms in the browser.
- In the project, consent appears as received.
- If you need it: finalize → proof (PDF + protocol) is created and becomes exportable.
The key difference (file vs process)
Many people think of “consent” as a PDF. That works — until you later need to explain what exactly was approved and which version applies. With a project flow, it’s clear: context, timing, mapping — and a conscious closure.
Does the other person need an account?
No. The link opens a browser page; confirmation happens without an account.
Can I also share via QR?
Yes. You can show the same link as a QR (on-site) or send it directly.
When is it exportable?
Only after you finalize. That’s when the proof (PDF + protocol) is created.
What if someone confirms incorrectly?
You can document the status in the project (e.g., revoked) and keep the history traceable.
What’s better: PDF or link?
For simple cases, a PDF is often enough. If you later need clean mapping/explanation, a project flow helps more than just a file.