Skip to main content

​
What This Does

Helix can recommend actions from the LoopIQ assistant, such as creating remediation work from release blockers or refreshing release evidence. When an action may create or update LoopIQ records, Helix asks for approval before it runs. The approval step lets you review the exact tool, payload, reason, and audit context before anything changes.

​
Where Approvals Appear

Helix action approvals can appear in:
  • the right-side Helix assistant in the LoopIQ web app
  • the LoopIQ Helix mobile app
  • release certification conversations where Helix recommends remediation work
  • MCP-powered workflows that need human confirmation

​
Before You Begin

Make sure:
  • you are in the correct organization, tenant, team, release, and certification context
  • your role can approve the requested action
  • the proposed payload references the records you expect
  • you understand whether the action is read-only or will create or update records

​
Review an Approval Request

When Helix needs approval, it displays an approval card with the proposed action. Review:
  • the tool name
  • the reason Helix wants to run it
  • the approval ID
  • the request, trace, workflow, and idempotency details
  • the preview payload
  • the records that may be created or updated
If the payload references the wrong release, team, provider finding, or parent record, reject the action and ask Helix to regenerate the plan with the correct context.

​
Approve and Run an Action

  1. Review the action card.
  2. Confirm the payload is correct.
  3. Select Approve and run.
  4. Wait for Helix to execute the approved action.
  5. Review the result message and audit trail.
  6. Open the created or updated records from the links Helix provides.
After approval, Helix sends the approved payload back to the server. The server executes the approved action directly instead of asking the model to recreate the payload.

​
Reject an Action

Select Reject if the action is not safe, not useful, or not grounded in the right records. Rejecting an action means no LoopIQ records are created or updated for that approval request.

​
Create Remediation Work Packages

For release blockers, Helix can create a remediation work package. This creates one parent remediation story and child tasks linked to that story. Use this when you want Helix to convert grounded release findings into trackable delivery work. The remediation package should include:
  • a clear parent story title
  • release, certification, team, and tenant context
  • the provider findings or controls that caused the blocker
  • child tasks with titles, owners if known, priorities, and rationale
  • evidence or finding references when available
Because the package is created in one approved transaction, Helix can capture the real parent story ID and attach child tasks to the correct parent.

​
Understand the Audit Trail

After an approved action runs, Helix should show what happened. Look for:
  • approval ID
  • tool name
  • execution status
  • created parent story ID
  • created child task IDs
  • idempotency key
  • request and trace identifiers
  • any structured errors
Use the audit trail to confirm that the records shown by Helix match what was created in LoopIQ.

​
Best Practices

  • Approve only actions that reference the expected release, certification, team, and provider findings.
  • Prefer remediation work packages for multi-task remediation plans instead of asking Helix to create unrelated standalone tasks.
  • Reject actions that invent backlog items or do not cite the records they are based on.
  • Ask Helix to explain which records it read before approving any write action.
  • Re-run or refresh the evidence graph before creating remediation work if the certification data looks stale.

​
Troubleshooting

​
The Approval Card Does Not Appear

The action may be read-only, your role may not require approval, or Helix may not have enough grounded context to propose a safe write action.

​
The Action Stays Pending

Check whether the request is waiting for an approver, the token expired, or the MCP service returned a structured error.

​
Records Were Not Created

Open the audit trail and check for rejected approval, missing permissions, wrong tenant context, duplicate idempotency key, or a tool error.

​
The Remediation Plan Has the Wrong Scope

Reject the action. Ask Helix to use the current release certification and list the evidence records, provider blockers, failed controls, and evidence gaps it read before proposing the next action.