> 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/import-export/general/do-not-allow-modification-in-imported-documents.md).

# Do not allow Modification in Imported Documents

**YouTube:** [How to Restrict Modification of Imported Documents?](https://www.youtube.com/watch?v=x57XVRc-PEE)

## How to Restrict Modification of Imported Documents?

In this tutorial, we’ll explore a feature in **Logic ERP** that ensures **data integrity** by preventing users from editing **stock transfer documents** that have been imported from other branches.

***

### **Enable Restriction Setting**

To activate this restriction:

* Open **Logic Admin**.
* Navigate to **Global Settings**.
* Under **"Import/Export"**, go to **"General Settings"**.
* Locate and enable the option labeled as:

  > **“Do not allow Modification in Imported Documents”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FsgQq7HgQiT6M2gKYOy0h%2FGlobal%20Admin.png?alt=media&amp;token=558f667f-0209-49bd-ae20-38a475ebd1e6" alt=""><figcaption></figcaption></figure>

* **Save** the settings and **restart** the software for changes to take effect.

***

### **Import a Stock Transfer Document**

* Open the **Import Stock Transfer – Virtual Branches** utility.
* Import a stock transfer document from another branch into the current branch.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FYAvaPPyqqkoVI8SBi2qp%2FSTI.png?alt=media&amp;token=03f76c7c-1647-4428-9a2a-5176bd794890" alt=""><figcaption></figcaption></figure>

***

### **Attempt to Modify the Imported Document**

* Open the **Stock Transfer** window.
* Click on **Modify** and select the recently imported document.
* Attempt to:
  * Change the **quantity**
  * Modify **item details**
  * Edit any field in the voucher

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FBsdgfsAm83mokRdf7U53%2FError%20Prompt.png?alt=media&amp;token=a986a718-5944-4541-9b69-86b16e2ff226" alt=""><figcaption></figcaption></figure>

**Result**:\
Upon saving, the software will display an **error message**, preventing any modifications. This confirms that the restriction is working as intended.

***

### **Conclusion**

This feature is essential for organizations working across **multiple branches**. It helps:

* **Maintain consistency** in records
* **Prevent accidental or unauthorized changes**
* Ensure **accountability** for inter-branch stock movements

Enabling this setting provides greater control and trust over **imported transaction data** in the system.


---

# 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/import-export/general/do-not-allow-modification-in-imported-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.
