Web & dev studio portal

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 hubs

Describe 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

My change requests

My change requests

Powered by Pory

In plain English

What is a web & dev studio portal?

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. It follows the Client hubs pattern: one shared space per client: deliverables, documents, milestones. Pory generates it from a plain-English description, with a login for each role (client and developer) that shows only what that role should see, and flat pricing with unlimited clients.

What it does

01

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 bit". 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
02

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, labelled with its project, and the team drags it through Triaged and In progress to Done, or Declined when it's out of scope. Clients see the same status without asking.

Board by statusDone by: Developer
03

Handoff files stay with the project instead of an expiring link

Handoff meant a download link that expired a week before the client needed the brand fonts again. The studio uploads design files, brand assets and how-to guides to the client's project in Pory, and they stay there. Nobody emails at 9pm asking where the logo went.

File attachmentsDone by: Developer
04

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

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, in its detail view, 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.

Detail view with related items

Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.

Notices & info pages

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

Counts, totals & averages

Live figures over the records a viewer is allowed to see.

Control

Who sees which records

Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up 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.

Frequently asked questions

Your web & dev studio portal, live today.

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