✓Approvals
A catalog request or a normal change stays unworked until the named person or approver group accepts it. The decision is written on the ticket timeline.
EU, US and India data residency · a DPA you can sign
Trust Center →ITSM
Approvals, changes, and problems. The rest is planned.
FlowTux still starts from the queue and the automatic fix. The classic process around that queue is now part of the product where it is listed as available, and only planned where it is listed as coming next. Nothing here has a ship date.
Available now
✓Change calendar
Each change has a risk, a planned window, an implementation note, and a backout note. Standard changes can go straight onto the calendar. Normal and emergency changes wait for approval.
✓Approver group
The group is a team you already have. Any member of that team can approve. FlowTux does not schedule CAB meetings or keep meeting minutes.
✓Problem records
A confirmed group of repeat incidents can be opened as one problem. The workaround is what agents see on those incidents until the cause is gone.
Coming next
- →Resolution SLA, with the clock paused while you wait on the requester, and business hours so nights do not burn the target
- →Major-incident flag and a stakeholder update cadence
- →Workload board for open tickets and SLA risk per person
- →Release windows that group scheduled changes
- →Joiner, mover, and leaver journeys beyond the onboarding checklist
- →Ticket-to-asset links and inventory reported by the device agent
Planned. No date.
Response-time SLAs, the service catalog, onboarding checklists, and the asset register are already in the product. They are not the fuller versions on the planned list: there is no resolution target yet, the catalog does not run a multi-step fulfillment, and asset discovery records hosts that answer a ping.