> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/posts/view-log.md).

# View log

With the view log, you can easily see who has viewed and read posts and comments. It helps you stay informed about reach and ensures important updates aren’t missed. 

{% hint style="info" %}
**Note:** If a post or comment has attached files, the view log only shows who viewed the post or comment - not whether they opened the attached files. To see who has viewed a specific file, go to the [file’s view and download log](/using-hippoly/files-and-folders/view-and-download-log.md).
{% endhint %}

To open the view log for a post or comment follow these steps

{% stepper %}
{% step %}
Go to your post or comment and click the `Menu-icon` at the top right corner. 
{% endstep %}

{% step %}
Select the `Seen by` menu option.

<figure><img src="https://2368761383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5A8sAk8EwFvZz8ID3yYR%2Fuploads%2FBLCT7Jsg5OOKb7jkxGMz%2Fposts-menu.png?alt=media&amp;token=f21356af-4eaf-4095-b53b-dfc4ddee1dd7" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
A dialog will appear showing all users who have viewed the post or comment.
{% endstep %}
{% endstepper %}


---

# 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://help.hippoly.com/using-hippoly/posts/view-log.md?ask=<question>&goal=<user_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.