Employee
Sees only their own leave requests.
- Pages
- Home, My leave requests, My paperwork, Team calendar, Leave policy
- Can start
- Request leave, New leave request, Upload a form
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.”
My leave requests
In plain English
Pory gives every employee, manager and HR a sign-in of their own. Each employee sees only their own leave requests. It covers submit → manager approval. Leave requests, leave paperwork, key dates and team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
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.
A manager opens the request, reads the dates, the reason and who covers, 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?"
Planning coverage meant cross-checking three people's inboxes. Every request sits on a month view, colored by whether it's pending, approved or taken, so HR can spot a clash before it's approved. Click any entry to open the request behind it.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own leave requests.
Sees every leave request in the portal.
Sees every leave request in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
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
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Records on a month or week view, by date.
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.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
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 employees.