Client
Sees only their own change requests.
- Pages
- Home, My change requests, My projects, Files, Invoices, Support
- Can start
- Log a change request, New change request, Upload content
My change requests
Client portal for web design & development studios
A web and dev studio portal is where clients log change requests against their project and collect handoff files, and the studio triages every request on one board instead of an inbox.
Pattern: Client hubsDescribe it to Pory
“We're a small web studio. Each client should see their own project, log bugs and change requests from staging, and download handoff files; our developers triage requests on a board.”
Viewing as
In plain English
How Pory sets it up
Pory gives every client and developer a sign-in of their own. Each client sees only their own change requests. It covers handoff, staging feedback and change requests. Change requests, projects, handoff files, content requests, milestones, invoices and studio team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Clients log staging bugs with the page and project attached
Staging feedback used to arrive as a screenshot in a text with the caption "this part". In Pory the client picks their project, says whether it's a bug, a content change or a new feature, names the page and describes what's wrong. Developers get a request they can reproduce without a follow-up call.
Forms to submit a recordDone by: Client
Every request lands in New, and developers drag it to Done
Requests lived across three inboxes and a to-do list only one developer could read. Each one lands on the board as New, labeled with its project, and the team drags it through Triaged and In progress to Ready to test, then Done, or Declined when it's out of scope. Clients see the same status without asking.
Board by statusDone by: Developer
Each client sees their own build stage and staging address
Clients asked for updates on calls because the studio had no single place to point them. Each client signs in and sees only their project: the stage it's in, the staging address and the launch date. Other clients' work never appears, even when two sites are being built side by side.
Client-only accessDone by: Client
Who sees what in a web & dev studio portal
Every person signs in to their own view. This is what each role in the demo gets.
Developer
Sees every change request in the portal.
- Pages
- Home, Change requests, Handoff files, Projects, Launch calendar, Invoices
- Can start
- Share a file
What’s in the web & dev studio portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Change requests
- Request (text)
- Project (link)
- Type (choice: Bug, Content change, New feature)
- Page (text)
- Details (long text)
- Client (link)
- Status (choice: New, Triaged, In progress, Ready to test, Done, Declined)
- Logged (date)
- Developer (link)
Projects
- Project (text)
- Stage (choice: Discovery, Design, Build, Staging, Launched)
- Launch date (date)
- Staging address (text)
- What happens next (text)
- Client (link)
- Project lead (link)
Handoff files
- Name (text)
- Client (link)
- Project (link)
- Kind (choice: Design files, Brand assets, How-to guide, Hosting notes)
- Shared (date)
- File (file)
Content requests
- What we need (text)
- Project (link)
- Needed by (date)
- Kind (choice: Copy, Photos, Access, Decision)
- File (file)
- Client (link)
- Status (choice: Requested, Uploaded, Checked)
Milestones
- Milestone (text)
- Project (link)
- Date (date)
- Kind (choice: Staging review, Meeting, Training, Launch)
- Client (link)
- Status (choice: Upcoming, Done)
Invoices
- Invoice (text)
- Project (link)
- What it covers (text)
- Issued (date)
- Due (date)
- Amount ($) (number)
- Client (link)
- Status (choice: Issued, Paid, Overdue)
Studio team
- Name (text)
- Role (text)
- Direct line (text)
The parts behind this portal
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
Collect
2 partsForms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
File attachments
Upload and view files on the record they belong to, not in a folder named FINAL v2.
Decide
1 partBoard by status
Cards in columns. Drag a record to move it along.
Control
3 partsWho sees which records
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.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A client signs in with a link sent to their email and lands on Home. They see Home, My change requests, My projects, Files, Invoices and Support, and only the change requests that are theirs. From there they can use “Log a change request”, “New change request” and “Upload content”.
You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.
More professional services portals
All professional services portalsDesign & creative agency portalDeliverable review & approvalMarketing agency portalCampaign requests & reportingFreelancer hub portalBrief intake → milestones → invoicesLaw firm portalClient intake, case status, document requestsAccounting & bookkeeping portalDocument collection & return statusManagement consulting portalDeliverables, notes & action itemsArchitecture & interior design portalPhases, drawings, approvalsPR firm portalCoverage tracker & release approvalsTranslation & localization portalJob submission & deliveryStaffing agency portalRoles, candidates, placements
Build your web & dev studio portal with Pory
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.