Every creator gets a self-service portal and every client a branded cockpit — profiles, deliverables, offers, documents and complaints, in one secure place.
Guided tour
On /creator a due deliverable prompts for the live post URL and an insights screenshot — submit and the status advances to In Review on its own.
Spring Launch — IG Reel #1
@lena.marlow · due today
Paste your live post URL
instagram.com/p/Czk8mM2
+ insights screenshot → becomes an asset
What you get
A /creator dashboard resolved from get_my_creator(): an agency news feed with an unread badge, quick-links to SetCard, deliverables, earnings and profile, plus open tickets, active deliverables, current campaigns and read-only provider orders.
Submit deliverable proof (live post URL + insights → an asset), edit the SetCard and media kit, self-report digital product keys, file expense reports with receipts, read a travel itinerary and browse the shared wiki.
A /portal with targeted, pinned, unread News, a real chat inbox, a complaint form that returns a written verdict, the wiki, one-click rebooking and the marketplace catalog.
The client Docs section shows only the contracts, invoices and settlements they are a party to — the scope is enforced, never hand-filtered.
A per-object /portal/<token> link exposes only the public ticket thread — never internal notes or SLA timers. A reply reopens the ticket, a CSAT survey arms once solved, and an inline KB search offers self-service.
Every portal surface carries the agency’s own logo and brand color — creator, client and token pages included.
Facts, not promises
FAQ
No — /portal sign-in is passwordless. A client signs in with a magic-link or a one-time code, and their identity comes from portal grants claimed by email. There is no password to manage or reset.
A /portal/<token> link is anonymous and scoped to one object — it shows only the public ticket thread, never internal notes or SLA timers. A reply reopens the ticket, a CSAT survey arms once it is solved, and an inline knowledge-base search is offered for self-service. It is a link, not an account.
Only the contracts, invoices and settlements the client is actually a party to. The Docs scope is enforced by the grant, not filtered by hand — a client never sees another party’s paperwork.
They still get their operational pages — SetCard, deliverables, expenses, the wiki. The relationship spine (news, tickets, portal invites) is simply empty until an email exists. It is a graceful empty state, never an error.
Turn on portals and every creator, every client and every complaint lands where it belongs.
No credit card · EU-hosted · GDPR & GoBD-ready