> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/user-guide/detail-view/visitors.md).

# Visitors

The Visitors document a list of users who viewed the record.

The content display is similar to the [Visitor](/widgets/section-widgets/regulation/audit-trail.md#visitor) widget. You can use the Visitor widget to insert the visitor information in the section view.

The page captures who and when the page is visited.

### Search visitors

You can search signers by typing a keyword into the search bar in the **visitor list view**, and then clicking **Search**. The search results can always be cleared by clicking the **Clear** button.

### Filter visitors

With the **Filter** function, you can limit the number of visitors displayed. You can do that by clicking **All visitors** and then selecting a filter from the dropdown. Here are a list of filters:

* **All visitors**. Filter to display all visitors.
* **My visitors**. Filter to display the visitors created by you.


---

# 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.labii.com/user-guide/detail-view/visitors.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.