Change approval in a builder chat

A builder Mind does not run the changes it proposes on its own: each proposed change arrives in the chat as an approval card and waits for your decision. This page covers the card, the decision and the states that follow. For the builder kinds, their acceptance modes and settings, see Warehouse Builder and Lake Builder.

Read the approval card

• The heading names the layer and the severity: Warehouse change needs your approval, Destructive warehouse change needs your approval, Lake change needs your approval, or Destructive lake change needs your approval.
• A count chip counts the group of actions waiting together, for example 2 of 3 actions.
• Each row lists one held action, with a status chip that starts at Awaiting approval, and the object the action would touch.
• The card carries the acceptance mode in force: Manual, Auto-accept, Unrestricted, or Auto-accept · destructive when auto-accept applies to a destructive change.
• The buttons are Approve, Reject and View details.
• An action the platform refuses rather than holds is marked Refused or Blocked on its card; it is not waiting for you.
• A step that is already running has its own stop controls on its card; see Stop and abort runs in chat.

Decide on the change

1. Select View details to read what would run before you decide.
2. Select Approve to let the changes run, or Reject to stop them.
3. If you reject, write a reason in the field Why? (optional; the model reads this), then select Confirm reject. Select Cancel to keep the card waiting.

• The reason is optional and holds up to 2000 characters.
• Your decision covers the whole group: approving runs every waiting action in it, and rejecting leaves every one of them unexecuted.
• Approving runs the change as you, and the tool view records the decision under an Approval panel: the decision, the mode, the tool class, the requested and decided times, and your reason. The tool view itself is described in Warehouse tool cards in chat.
• The buttons stay disabled while a decision is being applied, after the card is decided, and while the Mind is still streaming an answer.

What View details shows

• The drawer is titled Destructive change details or Proposed change details, and it counts the actions it holds, for example 3 proposed action(s).
• Each action appears with its arguments, and the SQL behind the change sits in its own block, for example Context SQL, with a Copy SQL action.
• Each row names its exact target, a table, data source, folder, secret, column, workflow or run, with its id where the name alone is not enough.
• On a phone the drawer opens as a bottom sheet.

Who can decide

• For a destructive change, Approve needs Add/Modify Warehouse Objects, or Add/Modify Lake Objects for a Lake Builder. Without it the button stays disabled and the card explains: "Approving a destructive change requires the Warehouse modify permission", or for a lake change "Approving a destructive lake change requires the Lake modify permission". On a phone the sentence shows as plain text because tooltips are not available.
• While the Mind is still generating a response, a decision is refused with "A response is still being generated for this conversation. Stop it before deciding." A second decision while one is being applied is refused with "A decision is already being applied to this conversation."
• A change cannot be approved while you view DataMind OS as another user: the platform refuses with "Changes cannot be approved from an impersonated session." Exit the view, then decide.
• When a builder runs from a scheduled task, the task's Acceptance setting decides what waits instead of a chat mode.
• Permissions are granted on roles; see Who can do what with Minds.

After a rejection

• The call's card carries the Rejected badge and reads "Nothing was executed for this call."
• The line under the heading names the decision-maker: Rejected by you, Rejected by another admin, or Rejected by an admin, followed by the written reason where one was given.
• A rejected change cannot be approved afterwards. The reason you wrote is read by the Mind, so it can propose a different change next time.

Connector work in a Lake chat

• A Lake Builder can hand custom connector work to a connector Mind. Its card shows a state badge: Working, Waiting for you, Finished, Failed or Stopped.
• Waiting for you means the connector Mind needs something from you before it continues.
• When the work finishes, its card opens the connector's data source in Lake.

Questions, answered

Why is Approve greyed out?

Two reasons. For a destructive change it needs Add/Modify Warehouse Objects, or Add/Modify Lake Objects for a Lake Builder; without it the card explains what it needs. Otherwise the card is locked because a decision is being applied, the card has already been decided, or the Mind is still streaming its answer.

What does "2 of 3 actions" mean on the card?

It counts the group: the card shows two of the three actions waiting in it, and one decision covers them all. Select View details to read every action.

Where can I read the SQL behind a proposed change?

Open View details. Each action lists its arguments, and the SQL behind the change sits in its own block, for example Context SQL, with Copy SQL next to it. This is also where you check the exact target before approving.

Why does the whole card say Destructive when only one action drops something?

The card takes the strictest class among its actions. One destructive action makes the whole card destructive, and the rows use the warning tone as well.

Does approving run the changes straight away?

Yes. Approving lets the group run: the change runs as you, and its row then reports the outcome, Done or Failed. The decision itself is recorded in the tool view.

Can I take back a rejection?

No. A rejected change stays unexecuted and cannot be approved afterwards. The reason you wrote is read by the Mind, so it can propose a different change next time.

The rejected card says "another admin". Who decided?

The line names the decision-maker: you when it was your decision, another admin when someone else decided, or an admin when the decision-maker cannot be resolved.

Can I approve a change while I view DataMind OS as another user?

No. The platform refuses with "Changes cannot be approved from an impersonated session." Exit the view, then decide on the card.

What does the mode label on the card mean?

It names the acceptance mode in force for the change: Manual, Auto-accept or Unrestricted, with Auto-accept · destructive when auto-accept applies to a destructive change. The modes themselves are described in Warehouse Builder and Lake Builder.