My tickets
An IT help desk portal is where employees log laptop, access and software problems as tickets, the IT team triages and resolves them on a board, and each requester can see where their own ticket stands.
Pattern: RequestsDescribe it to Pory
“Our staff need one place to report IT problems. The IT team should triage tickets by priority and mark them resolved, and whoever raised a ticket should be able to see its status.”
My tickets
In plain English
An IT help desk portal is where employees log laptop, access and software problems as tickets, the IT team triages and resolves them on a board, and each requester can see where their own ticket stands. 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 and IT team) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
IT problems arrived by Slack, email, and whoever caught Luis at the coffee machine, so half of them were never written down. In Pory an employee picks the category and priority, names the device, describes what's happening and adds a screenshot. The ticket lands in IT's queue with the details already there, and nobody gets stopped in the corridor.
The IT queue was a shared inbox where urgent and trivial looked identical. The IT team sees every ticket as a card on a board, in New, In progress, Waiting on requester or Resolved, and drags each one along as the work happens. The payroll lockout gets picked up before the printer jam, as it should.
"Any update on my laptop?" was the message IT got most, usually about a ticket already being worked on. In Pory each employee sees their own tickets with a progress bar from New to Resolved, including a Waiting on requester step when IT needs something from them. The update is already there, so the follow-up never gets sent.
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
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
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.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
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.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited employees, flat price.