> 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-version-release-notes/october-2026/user-access/user-access-reports/report-configuration-modification-log.md). # Report Configuration Modification Log Logic ERP has introduced a new **Report Configuration Modification Log**. It shows who changed which setting of a report configuration, the **old** and **new** value, and the date and time of the change. It also records when a report configuration is **created**, **copied**, **renamed**, **deleted** or **imported**. *** ### **Step 1: Open the Report** * Navigate to **User Access** and select **User Access Reports**. * Open the **Report Configuration Modification Log**. *** ### **Step 2: What is recorded** * **Setting changes:** for reports that use the newer settings screen (the settings grid), when a report configuration is saved, each setting that was changed is recorded with its old and new value, as shown on the settings screen. Saving a configuration without changing anything adds no entry. * **New configurations:** for the same reports, saving a new configuration is recorded. * **Copy, Delete, Rename and Import:** these are recorded for every report when they are done from the **Copy** button on the report screen (the **Copy**, **Delete**, **Rename** and **Import** tabs). * For an import, each configuration brought in from the file is recorded. A configuration that already exists and is skipped, because **Overwrite Existing Configurations** was not ticked, is not recorded. * Every entry records the user, the date and time, the computer it was made from, and the branch the user was logged in to. *** ### **Step 3: Choose what to see** * Select the date range. * Pick a user in **User Selection** to see only that user's changes. * Type in any of these boxes to narrow the list: **Report Name**, **Configuration Name**, **Setting Name**, **Workstation Name** and **Workstation User Name**. Each box accepts several names separated by commas, and finds any of them. * **Report Name** finds the report by its name on the menu or by the title of its settings screen. * When **Setting Name** is filled in, only setting changes are listed. New, copied, renamed, deleted and imported configurations do not appear, because they change no individual setting. *** ### **Step 4: Report configuration options** * **Show** - limit the report to one kind of change: **All**, **Settings Changed**, **New Configuration**, **Copied Configuration**, **Deleted Configuration**, **Renamed Configuration** or **Imported Configuration**. * **Match Names By** - how the name boxes are matched: **Any Part of Name**, **Start of Name** or **Whole Name**. A new configuration starts with **Any Part of Name**. * **Include New, Copied and Deleted Configurations** - when off, the report lists only the individual settings that were changed, so renamed and imported configurations are hidden too, whatever **Show** is set to. A new configuration starts with this option on. * **Show Branch** - adds the **BRANCH NAME** column: the branch the user was logged in to when the change was made. * **Show Workstation** (under **Support Options**) - adds the **WORKSTATION** column: the computer, and its Windows user, the change was made from. * **Show Technical Values** (under **Support Options**) is meant for your Logic ERP support team. *** ### **Step 5: Read the report** * The report shows **SNO.**, **DATE**, **TIME**, **USER NAME**, **MENU TITLE**, **REPORT**, **CONFIGURATION**, **ACTION**, **SETTING**, **SETTING GROUP**, **OLD VALUE** and **NEW VALUE**. * **MENU TITLE** is the report's name as it appears on the menu. **CONFIGURATION** is the name of the configuration. * **ACTION** says what happened: **Setting Changed**, **New Configuration Created**, **Copied From** (with the name of the configuration it was copied from), **Renamed From** (with the old name), **Configuration Deleted** or **Configuration Imported**. * For a setting change there is one line for each changed setting, with its **SETTING GROUP**, **OLD VALUE** and **NEW VALUE**. The lines of one save are kept together. * The changes are listed oldest first. > **Example -** A store's daily Sale Register report suddenly looks different. The manager opens the **Report Configuration Modification Log** for the last week and types *Sale Register* in **Report Name**. The report shows that Ravi saved the configuration *DAILY* on 28/09/2026 at 04:35 PM. The **ACTION** is **Setting Changed**, and one line names the setting that was changed, with its value before the change in **OLD VALUE** and after it in **NEW VALUE**. --- # 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-version-release-notes/october-2026/user-access/user-access-reports/report-configuration-modification-log.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.