> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/docs/docs-consultation.md). # How do I track document views? ### Viewing tracking The Docs app lets you track who viewed a document and how many times. #### Available information * **View counter** : total number of views per document * **Reader list** : which collaborators viewed the document * **View date** : when each collaborator opened the document #### Access view statistics From a document’s details, a section displays the view information. ### Document sharing A document can be shared in several ways: * **Post on the news feed** (News): create a post linked to the document with a description * **Copy link** : get an internal link to the document (requires Steeple authentication) ### Access and security Documents require authentication on mobile and desktop devices. On TV screens, documents are accessible without individual sign-in, which may represent a security consideration in public spaces. ### What the assistant can do The assistant cannot display view statistics. It can explain how to access view tracking in the Docs app. --- # 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://help.steeple.com/en/docs/docs-consultation.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.