> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/legal-evidence/verifying-digitally-signed-documents/activity-log.md).

# Activity Log

An activity log in emSigner refers to a record of actions and events related to user activities within the emSigner system. It provides a detailed account of who did what and when, which is crucial for tracking user interactions, maintaining security, and ensuring compliance.

The Activity log can be accessed by following the below steps.

**Step 1:** Login to emSigner account. Click on ‘Settings’ tab to open the Admin Settings and navigate to Activity Log

<figure><img src="/files/GUESigDFDyHTVsflFrWk" alt=""><figcaption><p>Activity Log under Admin Settings</p></figcaption></figure>

**Step 2:** The activity or audit log will show the details of all the activities that were performed. The table will capture the details like the Date & Time of the activity, Username, What action was performed, the Description of the action, Operating System & Browser and the IP Address.

<figure><img src="/files/7f80QwpCTXzuZkDwBD1R" alt=""><figcaption><p>Activity/Audit Log</p></figcaption></figure>


---

# 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://support.emsigner.com/legal-evidence/verifying-digitally-signed-documents/activity-log.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.