Architecture & interior design portal

An architecture and interior design client portal is where clients approve each design phase and open the drawings behind it, and the practice shares drawings with every client from one place.

Pattern: Client hubs

Describe it to Pory

“We're an eight-person residential architecture practice. Each client should see only their project, open the drawings we issue, and approve each phase before we start the next.”

Viewing as

Drawings

Drawings

Add
DrawingPhaseSheet typeFileClient
Ground floor planDeveloped design, Almeida extensionPlans1 fileBeatriz Almeida
Rear and side elevationsDeveloped design, Almeida extensionElevations2 filesBeatriz Almeida
Long section through the roof lightDeveloped design, Almeida extensionSections1 fileBeatriz Almeida
Kitchen joinery and finishesConcept design, Almeida kitchenFinishes schedule3 filesBeatriz Almeida
Stair and balustrade detailsTechnical drawings, Wren StreetDetails4 filesGeorge Whitfield
Site planConcept design, Kowhai BayPlans1 fileMere Parata

Showing 1–6 of 6

Powered by Pory

In plain English

What is an architecture & interior design portal?

An architecture and interior design client portal is where clients approve each design phase and open the drawings behind it, and the practice shares drawings with every client from one place. 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 architect) that shows only what that role should see, and flat pricing with unlimited clients.

What it does

01

Drawing sets reach the client sorted into plans, elevations and details

Drawings went out as zip files that clients opened on a phone and couldn't read. The architect uploads each sheet to the phase it belongs to, labelled plans, elevations, sections or details, and the client opens them from their project. When the builder asks which drawing, there's one place to look.

File attachmentsDone by: Architect
02

Clients approve concept design before anyone draws the next phase

Phase approvals used to be "yep, go ahead" in a text, which is hard to point to when the client later wants the kitchen on the other side of the house. In Pory the client opens the phase, looks through its drawings, and marks it Approved or Changes requested. The decision sits on the phase before a single technical drawing starts.

Approve / reject with a reasonDone by: Client
03

Each homeowner sees their own project and its drawings only

Practices share drawings by email because a shared folder per client is a job in itself. Each client signs in to Pory and sees only their project, its phases and its drawings. Two neighbours renovating on the same street never see each other's plans.

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 architecture & interior design portal, live today.

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