> 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/lock-all-modifications-on-or-before.md).

# Lock All Modifications on or Before

**YouTube:** [How to Lock All Modifications On or Before a Defined Date?](https://youtu.be/4tNLuGvJ-MY)

## How to Lock All Modifications On or Before a Defined Date?

In this tutorial, we will learn how to use a **global option in Logic ERP** that restricts all types of modifications or deletions to documents created before a specific date. This feature is especially useful for ensuring data integrity after closing monthly or yearly accounts.

***

### Configure Global Setting

* Open **Logic Admin**.
* Navigate to **Global Settings**&#x20;
* Under the **Other Settings** Click to **User Rights Settings**.
* Scroll to the bottom and locate the option labeled as:

> **“Lock all modifications on or before”**.

* Enter the **cut-off date** (e.g., 31-March-2025).
  * All entries created **on or before this date** will be locked.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FnBOYMlFgHttfoDMkzjoj%2FGlobal%20Admin%20dated.png?alt=media&amp;token=9058d6b2-cfc5-494e-acdb-21fe4789689d" alt=""><figcaption></figcaption></figure>

* Save the settings and **restart the software** for the changes to apply.

***

### Implement in Sale Bill

* Open the **Sale Bill** window.
* Select a bill created **before the defined lock date**.
* Try modifying the quantity and save the changes.
  * The software will immediately restrict the action and display an error message.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FRWJHrJTPobcInF8Z5DYc%2FPrompt.png?alt=media&amp;token=1731795d-75ff-4c90-abe2-e7c7527fb70f" alt=""><figcaption></figcaption></figure>

* Similarly, if you try to **delete the bill**, the software will block it.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FYW1LHWBjYd3BmG3ELqme%2FDelete%20Prompt.png?alt=media&amp;token=9042a6be-06f3-45cc-887f-6f0616599bb8" alt=""><figcaption></figcaption></figure>

***

### Verify in Other Documents

* Open another document, such as a **Sale Challan**.
* Select an existing challan created before the locked date.
* Attempt to modify or update the details.
  * Once again, the software will prevent the action and display a restriction message.

***

### Example Scenario

| Document Type | Created On | Action Tried    | System Response      |
| ------------- | ---------- | --------------- | -------------------- |
| Sale Bill     | 15-Mar-25  | Change quantity | ❌ Restricted (Error) |
| Sale Bill     | 20-Apr-25  | Change quantity | ✅ Allowed            |
| Sale Challan  | 28-Feb-25  | Delete entry    | ❌ Restricted (Error) |

***

### Key Benefits

* Ensures **data integrity** by preventing accidental or unauthorized edits.
* Helps in maintaining **finalized accounts** after audit/closing.
* Provides better **control over historical records**.


---

# 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/lock-all-modifications-on-or-before.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.
