> 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/change-log-viewer.md). # Change Log Viewer **Available on:** Desktop · Web · Phone Navigate to **User Access** and click on "Change Log Viewer". **Change Log Viewer** shows the changes recorded by the screens that keep a change log — who made each one, when, from which computer, and each value before and after. It only shows changes; it never alters anything. A user who is not an administrator needs rights to this menu in **User Access**. ## What is recorded So far the payroll and attendance screens record their changes: * **Shift roster:** Setup Week-off Patterns, Setup Payroll Shifts, Setup Shift Rotations, each employee's lines in Allocate Roster, every roster generation (from Allocate Roster or Generate Roster), each switch back to branch holidays, and the days changed in Roster Calendar (old and new value per day). * **Organisation:** Setup Designations, Setup Org Units, and each employee's placement in Assign Employees to Org. * **Attendance app setup:** Setup Attendance App Branches and their sites, Setup Attendance App Users, Setup Attendance Approval Rules, and every action in Attendance App HR Review. * **The attendance app itself** (shown with the screen *Attendance App*): employees' requests and cancellations, approvals and rejections, punch reviews, and automatic absent marks. Saving a record without changing anything adds no entry. A change is saved only together with its log entry: if the entry cannot be written, the change is not saved either. ## See the changes ### **Step 1: Choose the range** * The list starts empty, with **From** set to 7 days ago and **To** to today. * Change **From** and **To**, or pick one kind of change under **Document** — **(ALL)** first, then the kinds already in the log, such as *Roster Day Change* or *Employee Org Placement*. Then press **Refresh**. Nothing is read until you press it. ### **Step 2: Read a change** * The changes appear newest first, each with: * **Date / Time**, **User**, **Module**, **Screen** and **Document**, * **Action** — NEW, MODIFY, DELETE, GENERATE, SWITCH-BACK, DAY-CHANGE, APPROVE, REJECT or CANCEL, * the **Record** and **Employee** concerned, a **Summary**, and how many **Fields** changed, * **Workstation** — on the desktop the computer and its Windows user, on the web the web login — and **Mode**, WIN for the desktop or WEB for the web. Changes made on the web also show the network address of the user's computer (**Client IP**). * Click a change: **Fields changed** lists each field with its old and new value. The list shows at most the newest 5,000 changes; narrow the dates or the document to see older ones. > **Example —** An employee's week-offs changed unexpectedly. HR opens **Change Log Viewer**, sets **From** to the start of the month, picks **Roster Day Change** under **Document**, and presses **Refresh**. The entry for that employee — summary *1 day(s) changed, 14/11/2026* — shows who made it, when and from which computer; **Fields changed** shows *14/11/2026 Sat* going from *WEEK-OFF* to *DAY SHIFT (BY HAND)*. ## Messages you may see | Message | Why | What to do | | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | | Enter valid From and To dates | A date is missing or not a date | Correct it | | To cannot be before From | Dates reversed | Correct the dates | | Showing the newest 5000 changes only. Narrow the dates or the document type to see older ones. | More than 5,000 changes in the range | Narrow the range | | The change log could not be written: … | On any screen that records changes: the entry could not be saved, so the change was not saved either | Try again; if it repeats, ask your Logic ERP support team | ## On the web The same screen is on the web. On a phone or a narrow tablet the list of changes and the list of fields sit one above the other; on a wider screen, side by side. --- # 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/change-log-viewer.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.