A design and creative agency portal is where clients submit briefs and approve or send back each deliverable, and the studio keeps every project, file and change note in one place.
Pattern: RequestsDescribe it to Pory
“We're a 12-person design studio. Clients should submit briefs, see only their own projects, and approve each deliverable or send it back with change notes.”
My projects
In plain English
Pory gives every client and studio a sign-in of their own. Each client sees only their own deliverables. It covers deliverable review & approval. Projects, deliverables, change notes, asset requests, milestones, invoices, shared files and studio team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Briefs used to turn up as a voice memo, a mood board and a forwarded email from someone's boss. In Pory the client fills in one brief: what they need, the due date, the budget and the details, and it lands as a new project the studio can scope. Nobody reassembles the request from four inboxes.
Approvals used to hide in replies such as "looks good, maybe bigger?" that nobody could act on. The client opens the deliverable, looks through the attached files, and marks it Approved or Changes requested. The studio sees the decision on the card instead of three replies down an email chain.
Feedback arrived in fragments: a call, a text, a PDF with circles scribbled on it. Now the client files a change note against the deliverable, saying what to change and why, and it appears whenever anyone opens that deliverable. Designers stop hunting for which message had the final word.
Sharing work meant a folder link per client and hoping nobody forwarded the wrong one. In Pory each client signs in and sees only the projects that name them, with their briefs, deliverables, invoices and files. One portal holds the whole client list, and no client ever sees another brand's unreleased packaging.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own deliverables.
Sees every deliverable in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
A reviewer's score, a coach's feedback, a clinician's note, kept on the record it belongs to.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited clients.
