> 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/samita-wholesale-b2b/setting/recent-activity-log.md).
# Recent Activity log
See a running history of new customers, order approvals, and orders created across your store.
The Recent Activity log gives you a timeline of what's been happening in your store — new wholesale sign-ups, customer approvals, and orders — in one place.
## What shows up here
* **Registration form activity** — new customers, customer updates, and approvals or rejections.
* **Order activity** — new orders and new draft orders created through the app.
## Finding the log
{% stepper %}
{% step %}
### Open Recent Activity
From the **Dashboard**, click **History** next to the **Recent activity** panel.
{% endstep %}
{% step %}
### Filter by date
Use the date range picker at the top of the page to narrow the timeframe.
{% endstep %}
{% step %}
### Open the related record
Click any activity to jump straight to the customer or order it relates to.
{% endstep %}
{% endstepper %}
> ### **Need support?**
>
> If you do encounter any difficulty while proceeding these steps, don’t show any hesitation to contact us promptly via the email address [support@samita.io](https://help.samita.io/support@samita.io)
---
# 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://docs.samita.io/samita-wholesale-b2b/setting/recent-activity-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.
