When the builder wants to add, edit or delete records, or change who can see a table, it asks first. How to read the card, approve or reject, and what the messages mean.
Your records are real customer data: bookings, leads, payments. So when you ask the builder in the chat to change records themselves, for example "mark the three trial members as paid" or "delete the test leads", it does not do it on its own. It shows a card and waits for you. The same goes for changing who may see a table. Nothing changes until you approve, and a restorable version is saved first.
Screen recording: A data change waiting for approval in the Studio chat.
1. Ask in the chat: Write what should change in the records, in plain words. The builder prepares the change.
2. Read the card: A card titled Review changes (or Confirm database change for one change) shows the kind of change (Create, Update or Delete), how many records and a short summary.
3. Open the details: What will change? opens a table with Field, Before and After for each record. Check names and numbers.
4. Approve or reject: Press Approve change, or Reject to cancel. With several changes, Approve all approves them together.
Every table has rules for who may view, add, edit and delete records. When a change touches these rules, a separate card titled Access change shows Now and After approval for each action. The roles are Everyone, including visitors who are not signed in, Signed-in users, Owner, Admins and No one. An access change is never approved by Approve all; it has its own Approve access change button.
Read the red line: If you see After approval, this data is also available without signing in., the table becomes public. Fine for a class schedule, never for patients, payments or private notes.
You see | What it means
Changes apply only after approval. A restorable version is saved first. | Nothing happened yet. If you approve and regret it, restore the version. See Saved versions.
Change rejected. No records were changed. | You pressed Reject. All is as before.
Updated records: 3 | Done. The card keeps an Execution receipt with the number of records.
Database change was not completed. No success was recorded. | The change did not go through. Nothing was recorded as done; ask again in the chat.
2 changes completed. Stopped because the next change could not be confirmed. Review its status before continuing. | Part of an Approve all went through. Check the rest one by one before you approve again.
The access change was not applied. Access is unchanged. | The access rules stayed as they were.
Q: Why does the builder ask me? I asked for it.
A: Because records cannot be rebuilt from the code. The card lets you see exactly which rows change before they do.
Q: Does a normal build ask too?
A: No. Changing screens and code does not need this card; only changes to the records and to access rules do.
Q: Can I undo after approving?
A: Yes. A version is saved before the change; restore it from Versions.
Q: Where do I edit one record by hand?
A: In the database of the app. See The database.
Related: The database: tables and records, Saved versions and restore, App users, login and security, The chat: Build, Action and Talk