> ## Documentation Index > Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt > Use this file to discover all available pages before exploring further. # Approving changes > Approve or reject the configuration changes the admin assistant proposes — in the panel, on the Approvals page, or previewed in the matching editor. Every change the [admin assistant](https://docs.insight.nobly.dk/ai-administration/admin-assistant.md) proposes waits for your decision, unless it may [apply without asking](https://docs.insight.nobly.dk/ai-administration/admin-assistant.md#choose-your-own-auto-apply). Changes proposed from an AI assistant over [AI assistant access](https://docs.insight.nobly.dk/mcp/introduction.md#changing-configuration) wait in the same place. ## Prerequisites * Your user group holds **Use AI Admin Assistant**. * The assistant is available: AI features are available in your environment, the assistant is [switched on](https://docs.insight.nobly.dk/ai-administration/admin-assistant.md#switch-the-assistant-on), and the AI service can be reached. * You hold the permission the change's admin page requires. It is checked again when you approve. ## Who decides A change waits for the person who asked for it, and only that person can approve or reject it. The Approvals page lists only your own changes; the assistant never routes a change to a colleague for a second opinion. A change belongs to you, not to the conversation it was proposed in. Deleting a conversation, or a conversation passing the chat history period, leaves its changes on the Approvals page. A change that is over — applied, rejected, cancelled, expired or interrupted — is removed from the page once it is older than the chat history period; the configuration audit log keeps the record of what was applied. ## Cards A proposed change appears as a card in the assistant panel: * **The heading** names the operation and the item it touches, in the product's own words. The assistant's summary sits underneath; when the two disagree, trust the heading. * **Field**, **Before** and **After** show what changes. Values too large for the table are in **Show details**, where **Fields** and **JSON / code** show the whole change. * For a workflow, a script or a template, the details include a diff against the saved version — or, while you have the item open in its editor, against the editor's content including unsaved edits. Decide with **Approve** or **Reject**. Rejecting asks for no reason and applies nothing. ### Several changes at once When one answer proposes several changes, they arrive as one card: **Change 1 of 3**, with **Previous change** and **Next change** to browse them. **Apply all** approves them in the order they were proposed, and stops at the first one that is refused: what applied stays applied, and the rest keep waiting. A change that builds on another in the same batch shows **Waiting on the change above.** until that one is applied. If you reject the one it builds on, it can never apply and is marked **Cancelled**, and so is every change waiting on it in turn. In a batch from an outside assistant, each waiting change waits on the one above it, whether or not the two are related. Approve such a batch from the top, or with **Apply all**; rejecting one of its changes cancels the waiting changes below it. ## Preview in the editor A change to a workflow, a script, a Caseflow template or a form template can be tried out in its editor before you approve it. **1. Open the editor** Select **Open in designer** (workflows) or **Open in editor** (scripts and templates) on the card. Keep the assistant panel open. **2. Preview** Select **Preview in editor**. The proposal appears in the editor as unsaved edits — on the workflow canvas, in the script, or in the template. Nothing is saved. **3. Decide** **Approve** saves the proposal. **Reject** puts the editor back as it was. If you change the editor after the preview, approving saves the proposal as it was and drops your later edits; the card warns you first. The preview keeps the version of the item the proposal was prepared on. If you save it from the editor instead of approving it, and someone saved the item after the proposal was prepared, the editor refuses the save as out of date, as it would any save made on an older version. ## The Approvals page **Settings → AI Admin Assistant → Approvals** lists the changes you have been asked to decide: one row per assistant answer or per request from an outside assistant, newest first. | Column | What it shows | | - | - | | **Change** | What the batch changes | | **Source** | **Chat** for the assistant panel, **MCP** for an outside assistant | | **Status** | The status of its changes, or **Mixed** | | **Created** | When it was proposed | | **Progress** | How far it has got, such as **2 of 4 applied** | Open a row to see the same card as in the panel, and decide it there or with **Approve** and **Reject** on the row (**Approve all** and **Reject all**, with the number of changes, when the row holds several waiting changes). To decide several batches at once, select them and use **Approve selected** or **Reject selected**. Deciding from a row or a selection first lists every change it decides, with their number, and asks you to confirm. A change proposed into a batch after that list was shown is not decided with it; it keeps waiting, and the row says so. **Status** filters the list, **Refresh the list** reads it again, and **Load more** shows older batches. **Open in conversation** takes you to the answer that proposed a batch. **View in approvals** on a card in the panel goes the other way. When the assistant is not available — AI features switched off, the assistant switched off for the environment, or the AI service unreachable — the page says why, and your changes can be neither listed nor decided until it is available again. They keep waiting meanwhile. Changes that nobody decides expire after 7 days. ## Statuses | Status | Meaning | | - | - | | **Pending** | Waiting for a decision. | | **Applied** | The change was made. | | **Rejected** | Rejected, so the change was not made. | | **Cancelled** | A change it waits on was rejected, was cancelled or failed while applying, or the outside assistant's request it belonged to was refused, so it can never be applied. | | **Expired** | Nobody decided within 7 days. | | **Interrupted** | Applying the change failed partway or was cut off, so whether it applied is unknown. Check the configuration; the change is not applied again. | ## What approval checks again Approving applies the change exactly as it was shown, after checking again that you may make it and that nobody has changed the item since it was proposed. If either check fails, nothing is written and the card says why. Ask the assistant to prepare the change again on the current configuration. If writing the change fails partway, the card says so and the change is marked **Interrupted**: whether it applied is unknown, so check the configuration. It is not applied again, and every change waiting on it is cancelled. **Apply all** stops there; the changes after it keep waiting unless they wait on it. An approval cut off before it finished, for example by a restart, also stays **Interrupted**, and the changes waiting on it are cancelled within a day. An interrupted change is removed from the page with the changes that are over. ## Where to read next > **[Introduction to Caseflow](https://docs.insight.nobly.dk/caseflow/introduction.md)** > > Understand how Caseflow works in Nobly Insight — the object-data layer for case and process-driven business data. > **[Admin assistant](https://docs.insight.nobly.dk/ai-administration/admin-assistant.md)** > > Switch the assistant on, set what it may do, and choose your own auto-apply. > **[AI assistant access](https://docs.insight.nobly.dk/mcp/introduction.md)** > > Approve changes from an AI assistant such as Claude in its own dialog or on the Approvals page. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.