> 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/prompt-reason-in-case-of-item-account-master-modification-or-deletion.md).

# Prompt Reason in case of Item/Account Master Modification or Deletion

**YouTube:** [How to Enable Reason Prompt on Item/ Account Master Modification or Deletion?](https://www.youtube.com/watch?v=6ihjr4gxbnA)

## How to Enable Reason Prompt on Item/ Account Master Modification or Deletion?

In this tutorial, we'll demonstrate how to enable a feature in **Logic ERP** that prompts users to **provide a reason whenever an item or account master is modified or deleted**. This ensures accountability and traceability in master data changes.

***

### **Enable the Prompt for Reason**

* Open **Logic Admin** and navigate to **Global Settings**.
* Go to **Other** section and click to "User Rights Settings" 
* Locate and enable the option lableled as: **“Prompt Reason in Case of Item/Account Master Modification or Deletion”.**

<figure><img src="/files/uNSvHMxu9jK29ETiF5DB" 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.

***

### Demonstrating the Feature in Action

* **Item Master Modification**
  * Open the **Item Setup** window.
  * Select any existing item.
  * Modify a field—for example, update the **GST tax percentage**.
  * As soon as the change is made, the system will **prompt the user to enter a reason** before saving.

<figure><img src="/files/sXH5Xc1nVnRaTnsbs4Nl" alt=""><figcaption></figcaption></figure>

* **Account Master Modification**
  * Open the **Account Master** (e.g., Supplier Ledger).
  * Add or modify information—for example, **enter a mobile number**.
  * When the user tries to save, a **prompt appears asking for the reason**.
  * Once the reason is provided, the change will be saved successfully.

<figure><img src="/files/hk20rNaBSeGLncatmC2C" alt=""><figcaption></figcaption></figure>

***

### **Conclusion**

This feature helps maintain a detailed audit trail for sensitive master data changes by **capturing the reason behind each modification or deletion**, thereby improving **transparency and control** within 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/others/user-rights-settings/prompt-reason-in-case-of-item-account-master-modification-or-deletion.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.