Model Builder approvals, messages and report visibility

While a Model Builder session runs, everything that needs a person waits in the Needs you part of its session card, and the two chats around the build exchange messages by strict rules. This page covers answering its questions, deciding its held changes, queuing messages during a round, and who can read what the model's Model AI wrote. The session itself is followed on Model Builder sessions; the cards it shows are read on Model Builder cards.

What waits in Needs you

• The section sits first on the session card, with a badge counting everything that waits: the questions relayed to you plus the decisions still open. When nothing waits, the section folds down to Recently decided, a list of the latest decisions with the decision, the name and the time.
• Each row says what it is and where it came from: a Question or an Approval, from the Model AI or from the Model Builder.
• Where the Model AI offered choices, a question shows them as option chips, and a Blocking chip when it holds the build.

Answer a question the build relays

1. Read the question. Where the Model AI offered choices, they show as chips.
2. Choose a chip, or write your own answer in the field, which suggests Or write your own answer. An answer can hold up to 2000 characters; Enter sends it and Shift+Enter starts a new line.
3. Choose Send answer. It stays disabled while your answer is on its way, and while the field is empty.

• If the server refuses the answer, the reason shows under the field, so nothing is lost quietly. When a personal-data check only warns about your answer, you can send it on with Send anyway. An answer the stricter check blocks is not sent.
• Once an answer is accepted, the row reads answered by name, and a notice reads Answer recorded.
• A question that only writers can answer says: "Someone who can write in this chat answers this question."

Decide a change the build holds

• A held change appears as a row with the tool's label, its title and its lines. When you may decide it, the row offers Approve and Reject; a rejection takes an optional note, up to 500 characters, with the placeholder "Why? (optional; the AI reads this)", and asks you to confirm with Confirm reject.
• After a decision, the row reads Approved or Rejected with the time, and the latest decisions appear under Recently decided.
• If the decision belongs to someone else, the row reads Waiting for name to decide. and the change waits for the person who started the build.
• Where a held item lives in the model's Model AI chat, the row points there instead: A change waits for approval in the Model AI chat, or The Model AI asks a question in its own chat, with Open Model AI chat. A question offers Answer in Model AI chat.
• The change itself is applied, or dropped, in the model's Model AI chat.

Messages while a round runs

• The build's rounds run in the model's Model AI chat; that chat is described on Model AI. Its message box stays open while a round runs, and a message you send waits instead of being refused: the hint reads Your message is delivered right after the Model Builder's round, and the message shows as Queued · delivered after the round with Remove.
• One message waits at a time. A new message of yours replaces your earlier queued one; if someone else queued first, your send is refused with "name already queued a message for after the Model Builder's round. Wait for the round to end, then send."
• Remove belongs to the person who queued the message; anyone else is refused with "Only name can remove the message they queued." When nothing waits, the refusal reads "No message is queued for this model's AI chat."
• Others see that a message is waiting, and who queued it; the text is shown to the person who wrote it.
• A queued message is delivered as you sent it, right after the round and before the build's next round. It waits through Stop and the session's deadline. If your access to that chat changed by the time it is delivered, it is dropped, the reason shows, and the text comes back to your message box.
• Attachments cannot be queued: "Attachments cannot be queued while the Model Builder works. Send the text now and the image after its round, or wait for the round to end."
• While you view the platform as another user, queuing is refused: "Messages cannot be queued for after the Model Builder's round while you are impersonating another user."

Writing to the build itself

• The build's own conversation takes no messages from people. Sending or editing there is refused with: "The Model Builder works on its own and takes no messages here. Follow it and answer its questions on its card in the Warehouse Builder chat."
• A message that started a round cannot be retried or continued: "This message started a Model Builder round, so it cannot be retried or continued. The Model Builder reports an unfinished round by itself; start it again from the Warehouse Builder chat if needed."
• Other agents cannot feed it either: "The Model Builder takes no messages from other agents; it reports here by itself. Its session card has Stop for anyone who can write in this chat, and Continue and Start again for the person who started it." See Model Builder.
• While you view the platform as another user, you can read a session but not act on it: "Model Builder actions are not available while you are impersonating another user." See Impersonate a user.

What crosses between the chats

• Work moves between your chat with the Warehouse Builder and the model's Model AI chat as briefs and reports. Two kinds of text never cross.
• SQL stays out: a line that reads as SQL is left out, marked "(left out: it reads as SQL, and SQL never crosses to the Model AI)".
• Your own words stay out: a line that repeats a long run of your words from a private chat is left out, marked "(left out: it repeats the user's own words from a private chat)".
• Text is also screened for personal data before it crosses; replacements read "[personal data]".

Who can read the Model AI's words

• Text that comes from the model's Model AI chat is gated per model: only people who can use that model's Model AI can read it. Everyone else sees stubs.
• The report stub reads The Model AI filed its report, with the note "Only people who can use this model's Model AI can read the report." and a Load the report button that re-reads the window.
• The Model AI's own questions and change requests are stubbed the same way: a stubbed question reads "A question from the Model AI (only people who can use this model's Model AI can read it)".
• The check fails closed: when the platform cannot confirm that you can use the model's Model AI, you see the stub.
• Everything the build itself wrote stays readable: its questions to you, the shared-table questions, its decisions and names, the status, the rounds, the timings and the chart names. The names behind the Model AI's decisions are hidden too.
• The final report card in the chat carries no Model AI text; it is written to be read by everyone. The words live on the session card, behind the same check.

Who can act

• You read a session with the same access that lets you view its chat.
• Taking part needs write access in the chat: answering a relayed question, deciding a held change, stopping the build. Answering needs an open session and a question that waits; deciding, Continue with 2 more rounds and Start again belong to the person who started the build.
• The Model AI's words need that model's Model AI access (see above).
• The build adds no permission names of its own: it works with the chat and DataPrism permissions you already hold. For the full picture, see Who can do what in DataPrism and Model Builder.

What the build may change without asking

• On its own, the build changes only the objects of its own design: the tables the design created or changed. Anything older comes to you first, as a shared-table question on the session card. See Full-history backfill and the performance ladder and Design a model with the Warehouse Builder.
• The rule fails closed: a table the platform cannot confirm as the design's own is treated as older and asked about first. At most five such questions wait at once.
• A change outside the design is not attempted; it comes back to you, through a question or a new design card.

Questions, answered

What happens after I send an answer?

It goes to the build. The row then reads answered by name, and a notice reads Answer recorded. While it sends, Send answer is disabled; if the server refuses the answer, the reason shows under the field, so you can correct it and send again.

Why does a row offer "Answer in Model AI chat"?

That item belongs to the model's Model AI chat rather than the session card. The row points there instead of deciding on the card: Answer in Model AI chat for a question, Open Model AI chat for a change that waits there.

Why can't I write a message in the Model Builder's conversation?

It takes no messages from people: "The Model Builder works on its own and takes no messages here. Follow it and answer its questions on its card in the Warehouse Builder chat." Follow the rounds there, and answer, stop or continue the build from its session card.

Why can't I retry or edit a message that started a round?

That message is the round's trigger, so it is locked: "This message started a Model Builder round, so it cannot be retried or continued. The Model Builder reports an unfinished round by itself; start it again from the Warehouse Builder chat if needed."

What happens if two people queue a message for the same round?

One message waits at a time. The first queued message keeps the slot, and the second person is refused with "name already queued a message for after the Model Builder's round. Wait for the round to end, then send." Your own new message replaces your own queued one.

Can I remove a message that someone else queued?

No. Remove belongs to the person who queued the message; anyone else is refused with "Only name can remove the message they queued." The text of a waiting message is shown to its author; others see the slot and the name.

What happens to a queued message if the session stops?

It waits. A queued message survives Stop and the session's deadline and is delivered after the round, as you sent it. If your access to the chat changed by then, it is dropped, the reason shows, and the text returns to your message box.

Can I attach a file while a round is running?

No. Attachments cannot be queued: "Attachments cannot be queued while the Model Builder works. Send the text now and the image after its round, or wait for the round to end."

Why did my answer come back as "already answered"?

The question was settled before your answer landed. The refusals read "This question was already answered by name.", "Another answer was saved at the same moment. Send yours again." when two answers cross, or "This Model Builder session has already ended." when the session closed first.

Which permissions do I need to take part in a build?

A session is read with the same access that lets you view its chat. Answering, deciding and stopping need write access in the chat; deciding and the extra rounds belong to the person who started the build; the Model AI's words need that model's Model AI access. The build introduces no permission names of its own.