Documentation
  1. WORKFLOWS STUDIO
  2. Reports

Admin Action

An Admin Action is a record of a manual change an admin makes to an in-flight request from Reports — for example, correcting a form response on a request that's already running. It appears as an entry in the request's Progress Path so there's a clear audit trail of who changed what.

📘

Not a builder node

Unlike the workflow nodes you place on the canvas, Admin Action is not something you add when building a workflow. It's generated automatically when an admin uses Take Action on a request in Reports. You'll only ever see it in the Progress Path of a request, never in the builder.

How it's created

There is nothing to configure in the workflow builder. An Admin Action is generated at runtime when an admin uses Take Action:

  1. In Reports, open an in-progress request.
  2. Click the edit (pencil) icon on the request/task — its tooltip reads Take Action while the request is running (and View Form once it's complete). A Take action option is also available in the Progress Path timeline's action menu, alongside Nudge.
  3. Edit the form response and submit. The platform records that edit as an Admin Action entry.

Crucially, the original submission is not overwritten — the Admin Action is added as a separate entry, so the Progress Path shows both the employee's original response and the administrative correction. This keeps the history complete and auditable.

The only thing you configure: the permission

Admin Action itself isn't set up anywhere — but the ability to perform one is controlled by a permission. Grant it under Workflows → Settings → Permissions → Users → "Take actions via reports" (takeActionReport). Without it, an agent can't take action on a request, so no Admin Action entries are created.

Viewing Admin Actions in the Progress Path

  1. Go to Reports and open the request.
  2. Open its Progress Path.
  3. Turn on the Show Admin/Agent actions filter (the filter list also includes Hide Skipped nodes, Show failed nodes, and Show Blocked/stalled nodes).
  4. The entry appears inline as a Form Actions card showing Updated by <admin name> and the date the change was made.
📒

Good to know

  • Admin Actions require the Take actions via reports permission (RBAC); users without it only see View Form, not Take Action.
  • Because each Admin Action is a distinct timeline entry, you can always trace which value came from the original submission and which was an admin correction.
  • This is closely related to Retrigger & recovery — both are admin interventions performed on a request from Reports rather than configured in the workflow.