Design & creative agency portal

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: Requests

Describe 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.”

Viewing as

My projects

My projects

Powered by Pory

In plain English

What is a design & creative agency portal?

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. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (client and studio) that shows only what that role should see, and flat pricing with unlimited clients.

What it does

01

Briefs arrive with the budget and deadline already filled in

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.

Forms to submit a recordDone by: Client
02

Clients approve each deliverable or send it back in one click

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.

Approve / reject with a reasonDone by: Client
03

Change notes sit on the deliverable they're about, not in Slack

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.

Notes & scores on a recordDone by: Client
04

Each client signs in to their own projects and nobody else's

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 and deliverables. One portal holds the whole client list, and no client ever sees another brand's unreleased packaging.

Client-only accessDone by: Client

The parts every portal is built from

Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.

Collect

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Record pop-up & linked records

A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the rows a viewer is allowed to read.

Control

Role & row access

Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.

No-Password Doors

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

On purpose

Four things Pory won’t do

A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.

Take payments

Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.

Book time slots

Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.

Host the conversation

No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.

Plan routes

Pory keeps the service record, not the map.

Frequently asked questions

Your design & creative agency portal, live today.

Describe it in a sentence and send the invite. Unlimited clients, flat price.