how-tos · section
Sign in
Approvals.
Changes BE AI proposes, and approving, rejecting or retrying them.
Approve or reject a proposal
BE AI files the exact command. A named person approves. The audit trail keeps both.
Retry a proposal that failed
Retry is on a row that never ran. The first press asks you to confirm. The second press runs it again.
Show only failed proposals
The status menu keeps failed, or executed, and hides the rest. Nothing runs.
Group the approval queue
Group by machine, tag, company, status, or the action. The rows do not change, and nothing runs.
Group proposals by a site
Group by tag lists a machine under every group it belongs to. The rows are the same, and nothing runs.
Group proposals by the action
Action type puts every run_shell under one heading. The rows stay, and nothing runs.
Collapse or expand the approval queue
Collapse all hides the rows and leaves the heading. Expand all opens them. Nothing is approved.
Reject every waiting proposal
On Proposals, reject all clears every proposal still waiting on that machine. The first press only asks you to confirm.
Read approvals beside the machine
Inbox opens the waiting proposals for the machine you have open. Approve still runs the command.
Show only waiting approvals
The menu on the approvals rail hides cards that already ran or failed. Nothing is approved.
Save a proposal as a script
A run_shell proposal becomes a library entry, so the next person does not retype the command.