Request lifecycle
How a request is created, triaged, worked, and closed. Covers the seven states, custom fields, watchers, links, attachments, and the audit history.
- Where
- Admin → Settings → Request types · Agent workspace → Queue
- Permission
- EDIT_REQUESTS · MANAGE_REQUEST_TYPES · MANAGE_FORMS
- Updated
- October 2026
Overview
A request moves through seven states: New, Triaged, In progress, Waiting on requester, Waiting on approval, Resolved, and Closed.
The moves allowed between states are fixed. Most working states can go straight to Resolved or Closed.
A Resolved or Closed request can be reopened to In progress. Waiting on approval is entered and left only through the approval workflow.
Every status change records who made it, when, and the old and new state. It shows on the request timeline and in the audit log.
Public comments are visible to the requester. Internal notes are for agents only, and requesters cannot post them.
Attachments follow the permissions of the request they belong to.
Link requests as relates to, blocks, blocked by, or duplicate of.
To merge two requests, open one and choose Actions → Merge request. The merge adds a merged-into link, and the merged request's requester sees where it went.
When the two requests have different requesters, the merged request's comments arrive as internal notes. Neither requester sees the other's conversation.
Step by step
- 01
Start from a template pack
Template packs create a team with ready-made request types, intake forms, SLA targets, a few automation rules and draft knowledge base articles. Open them from
Setup → Templates, orTemplateson the Request types page.- Packs: IT, HR, Finance, Facilities, Legal, Operations, Security
- Clear any request type you do not want before applying
- Anything that already exists, matched by name or slug, is left alone and reported
- Applying a pack again creates only what is missing
- Purchase, access, hardware, software and leave types require approval
- Knowledge base articles are created as drafts to finish and publish
- Admin → Setup → Resume setup → Templates
- Pick packs → review → Apply
- 02
Define a request type
A request type sets which team owns a kind of request and what form people fill in. Create one under
Admin → Settings → Request types.- Enter a name and choose the team that owns the type
- Choose whether it requires approval, optionally with an ordered approval chain
- Save, then open
Edit form schemato add custom fields and mark which are required - Field kinds: text, long text, select, multi-select, checkbox, date, and file
Edit form schemaneeds theManage formspermission- A new type starts with one required
Detailsfield - Duplicate a type from its row menu to copy its settings and form; the copy starts inactive
- Admin → Settings → Request types → New request type
- Enter a name → choose the owning team → set approval
- Save → Edit form schema → add fields
- 03
Set up intake
Decide where requests of this type come in: the employee portal or the REST API.
- Portal: add the type to the employee portal
- API: accept requests of the type through the REST API
- API callers can set the type's field values when they create a request
- 04
Triage from the queue
Work incoming requests from
Agent workspace → Queue. Find them with filters or search, then act on one request or many at once.- Filter by team, status, priority, type, tag, assignee, approval, or service level agreement (SLA) risk
- Search by title, number, or requester name
- Select requests to change their status, assignee, team, or tags in bulk
- Export the filtered queue to CSV
- Open a request to reply, add internal notes, or change its priority, team, or assignee
- Escalations run automatically from SLA policy rules
- 05
Keep a request confidential
Limit who can open a request. The request type's
Confidentialitysetting decides what the portal offers.- Settings:
Never(the default for a new type),Requester chooses, orAlways confidential - Who can open it: the team it is routed to, the requester, the assignee, watchers, approvers, and people or teams added to it
- Moving the request to another team moves that access
- On the request, open
Details → Confidentialto see who can open it and why - Add or remove a person or a team there, or use
Make confidentialandRemove confidentiality - Requests of an
Always confidentialtype stay confidential
- Settings:
- 06
Resolve and close
Move the request to
Resolvedwhen the work is done. The requester sees the resolution.- Close it from the request's status control
- Or let the requester confirm the resolution from the portal
- Or use an automation that sets the status to
Closed - If work resumes, reopen a
ResolvedorClosedrequest toIn progress
Good to know
- Managers and admins can force-resolve a request. This denies any pending approvals and records an internal audit note.
- Comments support @mentions. Mentioned people get a notification and an email.
- Mentioning someone in a public reply also adds them as a watcher.
- On internal notes and confidential requests, only people who can already see the request are notified.