Create and improve your business system with approval checkpoints before certain changes.
Build makes changes and asks for approval before certain actions. It has the same building capabilities as Auto mode, with more opportunities to review what Zite is about to do.
Select the current mode below the chat box, then choose Build. Zite remembers your Auto or Build choice for that workspace in this browser.
Choose Build from the mode menu.
In the chat box, Shift + Tab cycles through Auto, Build, Plan, and Chat.
2
Describe the change
Name the page or process, the outcome you want, and what should stay unchanged. For example:
On the Jobs page, add a filter using the existing Priority field. Keep its current options, all job records, and the other filters unchanged.
3
Review approval requests
Before accepting a proposal, check the target app or table, affected data, and what the action will do. If it doesn’t match your request, skip or decline it and explain what to change.Build asks before deleting a database table or field, or changing a field’s type. It also pauses for actions such as connecting an account or confirming a new app.
4
Test the result
Read Zite’s summary and try the changed task. In this example, check each priority filter and confirm that your existing jobs still appear.If something is wrong, describe what you did, what happened, and what you expected.
App changes and data changes are separate. You can restore an earlier app version through version history, but that doesn’t undo changes to your tables or records.
