.svg)
What an IT self-service portal is
An IT self-service portal is where employees ask IT for things: an app, access to a system, a laptop, a replacement phone, everything a new hire needs. Each item has its own short form and the approvals it needs, and every request shows where it is until it's done.
A week of asking IT for things at Rookwood
Rookwood Hotels runs 18 hotels from a head office in Denver, with 2,400 staff and fifteen people in IT. Tomás manages the front desk at the Santa Fe hotel. He's always hiring, always moving people between shifts, and he has no patience for guessing which form to use.
Monday, 9:15 am: a catalog made for a front desk manager
Tomás signs in with his work login. The portal shows what a hotel manager can request: new starter setup, access to the reservations system, a replacement front desk tablet, a shared mailbox. Head office finance tools aren't in his list, because he'd never need them. His two open requests sit at the top with their status.
10:30 am: he knows what he'll get before he asks
He wonders what laptop a new night auditor gets. The catalog item answers it: the standard front desk laptop, the apps that come with it, how long delivery usually takes to Santa Fe, and IT's equipment policy linked underneath. He doesn't have to write to anyone to find out.
11:45 am: a request he doesn't need to make
Tomás starts to request the shift scheduling app for a newly promoted supervisor. The item page tells him supervisors already get it with their role, and it links the two-step guide for signing in the first time. He sends her the guide instead. She's signed in before her break ends, and IT never sees a request that didn't need to exist.
Tuesday, 2:00 pm: a new starter, set up in one form
Ana joins the front desk next Monday. Tomás opens "new starter setup" and fills in her name, role, hotel and start date. Because she's a front desk agent, the form already lists her laptop, email, reservations access and scheduling app, and he adds a name badge. It goes to his general manager for approval, then to IT, where each part lands in the right queue. Tomás sees every piece on one request: approved, laptop shipped, accounts ready.
Wednesday, 4:20 pm: IT has a question, and asks where he is
The tech preparing Ana's accounts wants to know whether she'll share the lobby workstation. She asks from the request, and the question reaches Tomás in Microsoft Teams, where he spends his day. He answers in Teams, the reply lands on the request, and the work carries on. No one had to call the hotel.
Friday: IT adds what people keep looking for
Rookwood's IT lead checks what people searched the catalog for and didn't find. Managers at four hotels looked for a key card printer. By Monday it's a catalog item with its own form and approval.
What your employees can do
See what they can ask for
Each person's catalog is personalized to their role, team and location, so a hotel manager, a developer and a new accountant each see the items that apply to them, and nothing else.
Know what they'll get
Every item explains what's included, who needs to approve it and what to expect, from IT's own policy pages. People make the right request the first time.
Skip the requests they don't need
When something is already included or just needs a setup step, the item says so and links the guide. People sort it out on their own and move on.
Set up a new starter in one go
Managers fill in one form for a new hire. The role fills in the standard kit and access, and each piece reaches the team that handles it, in the right order.
Follow every request to done
Employees see each request's approvals, owner and progress in the portal. When IT needs something, the question reaches them by email, Slack or Microsoft Teams, and their answer lands on the request.
What your IT team gets
Requests arrive already approved and with the fields your team asked for: the role, the hotel, the start date, the asset tag. Hardware, accounts and software each get their own queue in a single inbox, and automations send each part of a bundle to the right queue. Techs claim work, pass it on with internal notes, and talk to the requester on the channel they use. Analytics show which items are requested most, where approvals sit longest and what people looked for that isn't in the catalog yet.
What changes when requests run this way
The first request is the right request. Each item has its own form and explains what's included, so your team stops bouncing requests back for missing details.
Approvals happen before work starts, not after. Manager and system owner sign-off is part of the request, in order, and on record.
New starters have what they need on day one. One form covers the laptop, accounts and access, and the manager can see every piece arrive.
The status question disappears. Every request shows its owner and the steps still to go, so nobody has to ask IT for an update.
Your catalog grows from real demand. Searches that found nothing tell you which item to add next.
People and AI, working the requests together
An assistant sits in the portal and in chat. It answers questions about what an item includes from your approved policy pages, with the source, and helps people find the right item. It can open a request on someone's behalf only if you allow that, and every action is logged. Approvals and the work itself remain in human hands.
How to build your IT self-service portal
- List what people ask IT for. Start with your most common requests: apps, access, hardware, new starters, leavers.
- Build a form for each. Ask only for what the team needs, and add the approvals each item requires.
- Link your policies. Connect the equipment and access policies you keep in SharePoint, Confluence or Google Drive, so every item explains itself.
- Bring in your people. Enable single sign-on, then pull roles, teams and locations from your identity provider, so each catalog and form fills itself in.
- Set up the queues. Route each item to the right team, and use automations to split bundles like new starter setup.
- Open it to one location. Launch with one office or site, see what people look for, and add items before you widen it.
Fits the systems you run today
Single sign-on and user sync through your identity provider, SharePoint, Confluence, Google Drive and OneDrive for your policies, Microsoft Teams, Slack and email for questions on requests, and Airtable, Monday or ClickUp if IT tracks equipment there. For anything else, use webhooks or the API.
Related
- AI agent for IT support for answers and requests in Slack, Teams and email
- IT help desk portal for getting help when something stops working
- Employee help desk software for one front door to IT, HR and facilities
- Forms and request intake on MatrixFlows
- Rolling out a self-service portal for employees
- Employee enablement and support
| IT self-service portal on MatrixFlows | The usual way to ask IT for things | |
|---|---|---|
| Finding what to ask for | A catalog personalized to each person's role and location | A page of links to forms, or an email to IT |
| Knowing what you'll get | Each item explains what's included and who approves it | Ask IT and wait for a reply |
| The form | Its own fields per item, prefilled from the person's role | One generic form for everything |
| Approvals | Built into the request, in order, on record | Forwarded emails and "did your manager OK this?" |
| New starters | One form for laptop, accounts and access, split to the right teams | Several requests and a checklist someone keeps by hand |
| Questions from IT | Reach the requester in Teams, Slack or email and land on the request | Phone calls and lost threads |
| Status | Owner, approvals and progress visible to the requester | Chasing IT for updates |
IT requests sit inside your employee operations on MatrixFlows, next to HR and facilities, and the same platform handles customer and partner service too.