Approving Qubit's actions
Qubit asks for your approval before it does anything that changes data; this page explains the approval card, standing approvals and where other approvals are decided.
Written By Chris Scaminaci
Last updated About 1 hour ago
Qubit reads freely and asks before it changes anything. When it wants to run a tool that changes data, the answer stops and shows an Approval needed card, and you decide. Every signed-in person decides the approvals in their own conversations.
Before you start: Sign in with your QuantumOps account. A chat without an account identity cannot approve actions; its card says Sign in with your QuantumOps account to approve actions. Start a new thread to continue without it. Which tools ask for approval is set by your administrators in Tool Governance.
Why Qubit asks
Looking something up, searching documentation or drawing a chart does not change anything, so Qubit does it without asking. A tool that changes something, such as creating a draft QBR report or making a change in another system through an MCP source, asks first. This is the default, and your administrators can change it for each tool in Tool Governance:
- A tool can be allowed, so it runs without asking.
- A tool can be set to ask, so you see the card.
- A tool can be denied. A denied tool never runs and cannot be approved from the chat, and a standing approval never overrides a deny rule.
- By default, a tool that is marked as destructive asks on every call, and no standing approval covers it.
Decide an approval
- Read the Approval needed card. It names the tool (Qubit wants to run …), may give a reason, and shows the arguments, which are exactly what will run.
- Choose a button:
- Approve runs the tool once.
- Deny runs nothing. Qubit is told it was denied and carries on without it.
- For this conversation approves the tool and does not ask again for it in this conversation.
- Always allow approves the tool and does not ask you again for it in any conversation, until you revoke it.
- Read what happens next. The card shows approved or denied, and Qubit continues the answer with the result.
For this conversation and Always allow appear when the tool can be covered by a standing approval. A tool marked as destructive offers only Approve and Deny, and so does a card that is shown again when you reopen a conversation.
If Qubit asked for the same tool more than once in one answer, For this conversation and Always allow also approve the other waiting cards for that tool, so one click settles them all.
If something interrupts the decision, the card says why, for example Stopped before the decision was recorded., and you can decide again.
While a decision is waiting
A conversation that is waiting for your decision is paused. The message box shows Waiting for your decision… and the notice Approve or deny the pending action to continue this thread. You can close the chat and come back; the card is still there. If Qubit asked for several actions at once, the answer continues when every one has been decided. To leave the question unanswered, select New conversation.
Standing approvals
A standing approval is what For this conversation and Always allow create. The tool then runs without asking until you take the approval back.
- Select Standing approvals, the shield button next to the model list.
- Read the list. Each row names the tool, says how far it reaches (always, this conversation or one conversation) and when it began.
- Select Revoke on a row to take it back. The tool asks again from your next message.
- Select Done.
An empty list says None yet. Every gated tool asks each time. The browser extension shows the same list. Administrators can see and revoke everyone's standing approvals in the Tool Governance card on the StackJack Integration page; see Review and revoke standing approvals.
Where other approvals are decided
Related pages
- Chat with Qubit: the chat itself.
- Tool Governance: how administrators decide which tools ask.
- Approvals tab: approvals that are not part of a chat.
- Approvals and files in Slack and Teams: approvals on a Slack or Teams card.
- Connecting external AI clients over MCP: the clients whose write requests wait for an Administrator.
- Chat tab: approvals in the browser extension.
Was this helpful?
Still need help? Ask the team