> 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-document-configuration-modification-for-supervisor.md).

# Do not Allow Document Configuration Modification for Supervisor

**YouTube:** [How to Globally Restrict Supervisors from Modifying Document Configurations?](https://www.youtube.com/watch?v=xZTmSDj8qoo)

## How to Globally Restrict Supervisors from Modifying Document Configurations?

In this tutorial, we’ll demonstrate how to **restrict supervisors from modifying document configurations** in Logic ERP.

***

### **Enable the Restriction Setting**

* Open **Logic Admin** and go to **Global Settings**.
* Go to **Other** section and click to "User Rights Settings"&#x20;
* Locate and enable the option labeled as: **“Do not allow document configuration modification for supervisor”**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FIMGsaiwPCHnAZuPRxXj8%2FAdmin%20-%20Do%20not%20Allow%20Report%20Configuration%20Modification%20for%20Supervisor%20new.png?alt=media&amp;token=da3f6c0a-1c23-41f5-a92c-fe8541fb579d" alt=""><figcaption><p>Let's proceed with this option turned on to understand its practical implications in billing.</p></figcaption></figure>

* Save the settings.
* Restart the software to apply the changes.
* Use a **supervisor user account** to log in to Logic ERP.

> **Note:** To login through supervisor user press **Shift+F3**.

***

### **Attempt Configuration Modification**

* Go to any **Voucher Configuration** window.
* Try making a change in the configuration.
* Click **Save**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FYARzY0jGO6XOz8iD8fWt%2FPrompt%20for%20not%20allowed.png?alt=media&amp;token=fa875812-247b-41f4-88b8-c98048ffe464" alt=""><figcaption><p>As you can see in the image above, the software has prompted 'Modification Not Allowed'.</p></figcaption></figure>

> **Expected Result:** The software blocks the action and displays an **error message**:\
> **“Modification rights are not available.”**

* The configuration options will remain **disabled** for the supervisor in **all document configuration screens**.

***

### **Conclusion**

This feature ensures that **supervisors cannot modify document configurations**, preserving control and consistency across all branches and users, as enforced by admin settings.


---

# 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-document-configuration-modification-for-supervisor.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.
