> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/manage-task/view-and-track-changes-in-bulk-edit.md).
# View & Track Changes in Bulk Edit
Monitor modifications made to your products in bulk.
### **Where to Find the Change Log**
1\. Open the app **Dashboard**, you can see all the tasks you created in te task list.
2\. Click on a task to open it and view task detail
3\. View the product change section to see how the products were edited
**What’s Inside the Change Log?**
✔ **Date & Time** – When changes were made.\
✔ **Action Type** – (E.g., “Price Updated,” “Title Updated”).\
✔ **Before & After Values** – See exactly what was modified.
If you do encounter any difficulty while proceeding these steps, don’t show any hesitation to contact us promptly via the email address .
---
# 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://docs.samita.io/bulk-price-editor-sami/manage-task/view-and-track-changes-in-bulk-edit.md?ask=&goal=
```
`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.