My leave requests
PTO & leave requests portal
A PTO and leave request portal is where employees ask for time off, managers approve or decline each request with a reason, and HR sees everyone's leave on one calendar.
Pattern: RequestsDescribe it to Pory
“Our 40-person company needs a place where employees request time off, their manager approves or declines, and HR sees everyone's leave.”
Viewing as
In plain English
What is a PTO & leave requests portal?
A PTO and leave request portal is where employees ask for time off, managers approve or decline each request with a reason, and HR sees everyone's leave on one calendar. 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 (employee, manager and HR) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
Employees ask for time off in a form, not a Slack message
Leave requests used to arrive as DMs, emails and hallway asks, and someone copied them into a spreadsheet. In Pory an employee picks the type and the dates, adds a reason, and the request lands as Pending. They can see where every request they've made stands, so nobody has to ask twice.
Forms to submit a recordDone by: Employee
Managers decide in one click, with the reason kept on the request
A manager opens the request, reads the dates and the reason, and approves or declines. A decline carries a note on the request itself, so the employee knows why and what to try instead. No more "did you see my email about Friday?"
Approve / reject with a reasonDone by: Manager
HR sees who's out, when, on one calendar
Planning cover meant cross-checking three people's inboxes. Every request sits on a month view, coloured by leave type, so HR can spot a clash before it's approved. Click any entry to open the request behind it.
CalendarDone by: HR
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, equipmentExpense 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 themVisitor management portalPre-registration & today's visitor list
Your PTO & leave requests portal, live today.
Describe it in a sentence and send the invite. Unlimited employees, flat price.