Self-service portal & requester
End users and requesters use the Self-Service Portal at /portal on the same host as your Tenant Plane (e.g. https://<tenant-slug>.<your-domain>/portal). This is not the Control Plane — it is customer ITSM self-service on the TP.
1. Before you start
- Open your Tenant Plane URL (from your welcome email or admin).
- Sign in (email/password, SSO, or your org’s method).
- Your role must include portal access. The requester role is scoped to ITSM read/write and lands on
/portalin the default navigation layout.
Roles (summary):
| Role | Portal | Extra shortcuts |
|---|---|---|
| Requester | Full portal (catalog, my requests, knowledge) | No Report an incident or ITSM Dashboard buttons in the portal header |
| Fulfiller (and operator / admin) | Same portal plus links to Incidents and ITSM Dashboard | Can optionally “Also create an incident” when submitting a request |
2. Step-by-step: browse the service catalog
- Go to
/portal. - Open the Service Catalog tab (default).
- You see catalog items created in ITSM (
/api/itsm/catalog). If the list is empty, admins have not published items yet — you can still submit a generic request (next section). - Click a catalog item to open the request form pre-filled with the item name, or use Submit a request (no item).
3. Step-by-step: submit a service request
- Click Submit a request (header) or select a catalog item.
- Fill in:
- Title (required)
- Additional details (optional)
- Your email or ID (identifies you on the request)
- Requesters do not see “Also create an incident (for urgent issues)” — only fulfiller+ roles see that checkbox. If you need an incident and you are a requester, use your org’s process (e.g. service desk phone, or ask an admin to grant fulfiller / use Incidents if you are promoted).
- Click Submit. The UI calls
POST /api/itsm/requests. - On success, open My Requests to track status.
If the catalog item has a linked ITSM approval workflow, the platform may start a workflow instance automatically (see ITSM approval vs automation workflows).
4. Step-by-step: my requests
- Open the My Requests tab.
- The portal loads
GET /api/itsm/requests(with your tenant context). - Review status and any linked incident if your flow created one (fulfiller path).
5. Step-by-step: knowledge base (KEDB)
- Open the Knowledge Base tab.
- Enter a search query and search. The portal calls
POST /api/itsm/kedb/search. - Open articles from the results to self-solve before filing a request.
6. What requesters cannot do from the portal (by default UI)
- Open Incidents or ITSM full dashboard from the portal header shortcuts (those buttons are fulfiller+ only).
- Tick “Also create an incident” on the request modal (same gating).
- Change management (raise/approve changes) is not exposed as a dedicated button on
/portal— operators use ITSM modules (/itsm) for changes.
7. For administrators
- Publish catalog items in ITSM; they appear automatically on
/portalfor the same tenant. - Assign requester to employees who only need catalog + requests + knowledge; fulfiller to service desk staff.
- Configure SSO group → role mapping so IdP groups land in the right role (see Users, roles & access).
See also
- Users, roles & access — Roles, invite, SSO
- Workflows: ITSM vs automation — Catalog
workflow_definition_idand fulfillment - ITSM module — Full ITSM surface (changes, problems, catalog admin)
- Authentication & user management — Login and password reset