> 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/setups/setup-items/setup-items-multiple-pack-sizes/configuration-multiple-packs-sizes/configuration-options-1/do-not-allow-item-modification.md).
# Do Not Allow Item Modification
**YouTube:** [How To Restrict Item Modification Through Item Configuration in Logic ERP Software?](https://www.youtube.com/watch?v=kaJ-ppSW3BU)
## How To Restrict Item Modification Through Item Configuration?
In this tutorial, we will guide you through an essential feature of Logic ERP: **Restricting item modification** to enhance security, data integrity, and compliance.
### **Accessing the Configuration**
* Navigate to the Setups/Setup Items and then click on "Setup Items Multiple Packs/Sizes".
* Click on the Configuration.
* Locate the option "Do Not Allow Item Modification" under the Configuration option - 1.
Click on the option to enable it as instructed.
### **Implementing the Restriction**
* Attempt to modify a previously created item.
* The software will immediately generate an alert stating that **modification rights are not available.**
As you can see, the software has prompted the message: "Modification rights not available."
### **Conclusion**
By enabling this restriction, you can ensure that item modifications are controlled, reducing errors and unauthorized changes. This contributes to a **more secure, efficient, and compliant** business environment within Logic ERP.
---
# 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/setups/setup-items/setup-items-multiple-pack-sizes/configuration-multiple-packs-sizes/configuration-options-1/do-not-allow-item-modification.md?ask=&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.
