Leaving tasks
Leaving tasks
1 of 4 done- Add a task
Offboarding portal
An offboarding portal is where IT and managers work through each leaver's checklist — revoking access, wiping laptops, handing over accounts — and every piece of company equipment stays on a list until it's back.
Pattern: ChecklistsDescribe it to Pory
“When someone leaves, IT and their manager each have tasks to finish, like revoking access and collecting the laptop. We need a checklist per leaver and a list of the equipment still to come back.”
Viewing as
In plain English
What is an offboarding portal?
An offboarding portal is where IT and managers work through each leaver's checklist — revoking access, wiping laptops, handing over accounts — and every piece of company equipment stays on a list until it's back. It follows the Checklists pattern: the same task list, worked through again and again. Pory generates it from a plain-English description, with a login for each role (IT and people team) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
IT ticks off each leaver's access removals from one list
Offboarding lived in an email chain that opened with "Sofia's last day is Friday" and ended with her still in Salesforce a month later. In Pory each leaver gets their own copy of the leaving checklist, and IT sees the tasks assigned to them — revoke access, wipe the laptop — and ticks each one as it's done. Nobody finds a former colleague still signed in to the CRM.
ChecklistsDone by: IT
Each leaver's laptop and phone stays on the list until it's back
Getting kit back from leavers relied on someone remembering what was issued two years ago. In Pory each item sits against the leaver with its asset tag, a return-by date and a status — Due back, Returned, Wiped or Lost — and IT updates it as the courier bag arrives. The phone that walked out the door is spotted before the leaving drinks.
Tables to manage recordsDone by: IT
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 → approvePolicy acknowledgment portalPublish policies & see who hasn't read themVisitor management portalPre-registration & today's visitor list
Your offboarding portal, live today.
Describe it in a sentence and send the invite. Unlimited employees, flat price.