> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/others/user-rights-settings/do-not-allow-modification-of-approved-documents.md).

# Do not allow modification of Approved Documents

**YouTube:** [How to Prevent Modification of Approved Documents?](https://www.youtube.com/watch?v=2uo_I68wp8g)

## How to Prevent Modification of Approved Documents?

In this tutorial, we’ll walk you through how to **restrict the modification of approved documents** in **Logic ERP**, ensuring data integrity and controlled access.

***

### **Enable Restriction on Approved Document Modification**

* Open **Logic Admin** and navigate to **Global Settings**.
* Go to **Other** section and click to "User Rights Settings"&#x20;
* Locate and enable the option labeled: **“Do Not Allow Modification of Approved Documents”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F4lZchx4IfpgEEquRq8V2%2FDo%20not%20allow%20modification%20of%20Approved%20Documents.png?alt=media&amp;token=41e5938e-4fcb-4523-aaa2-82662ac73d2f" alt=""><figcaption><p>Let's keep this feature enable to observe its impact in billing</p></figcaption></figure>

* Save the settings.
* Restart the software for the changes to take effect.

***

### **Approve a Document**

* Navigate to Logic Icon/ Common Programs and then click to **"My Messages"**.
* Locate a pending entry and **right-click** on it.
* Choose the **Approve** option to finalize the entry.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fmc80m9B3yRobR9qqZxrN%2FApproval.png?alt=media&amp;token=87e899e4-9bb8-46fc-a973-e65f828392e5" alt=""><figcaption><p>Use the Illustration Above to Approve the Entry</p></figcaption></figure>

> Once approved, the entry becomes **non-editable**.

***

### **Attempt to Modify an Approved Entry**

* Go to the **Bank Payment Entry** window.
* Select a document that was **previously approved**.
* Try to **change the amount** or any other field.
* Click **Save**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FLtSNwvDE6pFSqlh9CpS0%2FDisallow.png?alt=media&amp;token=85d9e3fc-9e9e-4649-b4e5-ce2c54e98d77" alt=""><figcaption><p>System Restriction: Approved Voucher Is Locked for Editing</p></figcaption></figure>

> The system will display an error message:
>
> *“This entry has already been approved and cannot be modified.”*

***

### **Conclusion**

Enabling this feature in Logic ERP helps enforce strict control over financial and operational records by **locking approved documents**, preventing unauthorized or accidental changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/others/user-rights-settings/do-not-allow-modification-of-approved-documents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
