Approvals

Inspect a proposed AI action before it changes team data.
4 min read · Reviewed

Stay in control when Bidlo AI proposes an action that can change team data. An approval request gives you a final decision point for a protected action; it doesn't replace a careful prompt or a check of the result.

Prepare a change you can review

Give Bidlo AI a narrow, inspectable request before it starts working.

  1. Open Home or an existing conversation in Chats.
  2. Name the page, record, or collection the change should affect.
  3. Use @ or Add Context when the target already exists in Bidlo.
  4. State the exact fields, values, and record set that may change.
  5. Add a boundary such as “do not change any other records.”

For example, “Set Status to Review on the three mentioned projects; do not change dates, assignees, or any other projects” is safer to review than “clean up these projects.”

Review an approval request

When Bidlo requires approval, the request appears in the conversation where the action was proposed. Review the request before choosing its allow or decline option.

  1. Confirm the action matches your request, such as creating, updating, or deleting data.
  2. Confirm the target is the intended page, collection, record, or external destination.
  3. Confirm the scope includes only the expected records and fields.
  4. Confirm the new values are complete and correctly formatted.
  5. Consider the consequence, including whether the action changes access, removes data, affects many records, or sends information outside Bidlo.
  6. Continue only when every part matches your intent. Otherwise, decline the action and send a narrower or corrected request.

After you continue, keep the chat open until Bidlo reports whether the action completed or failed.

Understand approval and the thinking trace

While Bidlo AI works, you can use Show thinking to inspect the visible work trace. Depending on the request, this can include steps such as Check capabilities, Search notes, or Query mentioned document.

The thinking trace explains what the assistant tried to do. It is not the same as an approval request, and a capability check is not evidence that you approved a change.

Not every request produces an approval step. A request may return an answer, complete an allowed action, or explain that the requested action isn't available. If you no longer want the current run to continue, select Stop.

Verify the saved result

Approval confirms the proposed action, not the accuracy of the final data. Check the destination separately after the run finishes.

  1. Open the affected page, record, or collection from the sidebar or search.
  2. Confirm that the intended records contain the expected values.
  3. Check that unrelated fields and records did not change.
  4. Open Activity when it is available and you need to review the record's recent history.
  5. Return to the chat with any correction, naming the exact value that needs to change.

For a bulk change, spot-check representative records and compare the total number of affected records with the scope you approved.

If the request is too broad

Decline the proposed action and rewrite the request with a smaller boundary. Useful corrections include:

  • “Show me the proposed values first; don't save anything yet.”
  • “Apply this only to the two records I mentioned.”
  • “Update Status only. Leave every other field unchanged.”
  • “Create a draft, but don't publish or send it.”
  • “Explain what you cannot verify before asking me to approve a change.”

If the assistant says an action is unavailable, don't treat the message as a pending approval. Choose a supported action or complete the change directly in the relevant Bidlo page.

FAQs

Does mentioning a page authorize Bidlo AI to change it?

No. A mention provides context. The available action still depends on your access, and protected changes may require a separate approval.

What should I check before approving a change?

Confirm the exact action, target, scope, and consequence. Take extra care with deletions, bulk updates, permission changes, and external sends.