Pre-register
Pre-registration & today's visitor list
Visitor management portal
A visitor management portal is where visitors pre-register on a public form before they arrive, reception sees the day's expected visitors in one list, and each host sees who is coming to see them.
Pattern: RequestsDescribe it to Pory
“Visitors to our office should register before they arrive, saying who they're meeting and when. Reception needs today's list, and each host should see their own visitors.”
Viewing as
In plain English
What is a visitor management portal?
A visitor management portal is where visitors pre-register on a public form before they arrive, reception sees the day's expected visitors in one list, and each host sees who is coming to see them. 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 (reception and host) that shows only what that role should see, and flat pricing with unlimited visitors.
What it does
Visitors register before they arrive, naming their host and time
Reception found out about visitors when they walked in, then rang around the building to find whoever they were meeting. In Pory visitors fill in a public form before the day — name, date, arrival time, host and company — without needing an account. The visit is on reception's list before the lift doors open.
Public pages & formsDone by: Reception
Reception starts the day with each expected visitor already listed
The front desk ran on a paper visitor book and whichever calendar invites hosts remembered to forward. In Pory reception sees the day's visits with arrival times, hosts and companies, and marks each visitor On site, Left or Cancelled as the day goes. When the fire warden asks who's in the building, the answer is on screen.
Tables to manage recordsDone by: Reception
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
More workplace portals
All workplace portalsEmployee onboarding portalTasks, documents, equipmentPTO & leave requests portalSubmit → manager approvalExpense reimbursement portalClaim → finance approvalIT help desk portalTicket submit & resolvePerformance reviews portalSelf + manager review cycleApplicant tracking portalApplications & interview stagesTimesheet approval portalSubmit hours → approveOffboarding portalAsset return & access revocationPolicy acknowledgment portalPublish policies & see who hasn't read them
Your visitor management portal, live today.
Describe it in a sentence and send the invite. Unlimited visitors, flat price.