Clients & portal
On Pro, Caddi gives every client a portal. Magic-link login, scoped to their projects. White-labelled. Optional approval gates.
Why a portal
- Clients aren’t paying for a Caddi seat. They are paying you.
- But you still want them to file requests, see the staging deploy, approve releases, and upload brand assets.
- The portal gives them exactly that surface, nothing more.
The pieces
- Auth — magic links, 7-day sessions. No passwords.
- Requests inbox — clients file, you respond. Pinpoint payloads land here too.
- Approval — optional, per-project. Clients click “Approve” to allow
staging → productionpromotions. - Brand assets — logos, fonts, brand guides. R2-backed.
- Submissions — read-only access to that client’s form submissions.
Pages in this section
The deeper concept piece
See Customer portal for the model — roles, isolation, what clients can and cannot do.