# Manager tools

Company managers have access to extra data on top of the regular document view, designed to help track who has read each document and to audit compliance with company publications.

> Manager tools are available to users in **group level 150 or lower** (administrators and managers). Pilots and other regular members do not see them.

### Download registry

For each document, managers can see the full download history of the current version, including:

* User name and group
* Download date
* IP information when available

Re-downloads by the same user are not duplicated — the registry reflects unique readers per version, which is the figure that matters for compliance.

![](https://tawk.link/61f94bae9bd1f31184da67e3/kb/attachments/TitB2ImhZs.png)

### Pending users

Together with the download list, the view page shows a **Pending users** list — authorized users who have not yet downloaded the current version. The list is built from the document's authorized user groups minus the users that already downloaded, excluding inactive and deleted accounts.

This is the easiest way to chase the few crew members that still need to read a critical publication.

### Version reset

Publishing a new version clears the download registry and the comments for that document. From that moment, the **Pending users** list shows every authorized user again and the cycle restarts.

This guarantees that "downloaded" always refers to the current publication, never to an older one.

### Cross-company visibility

Because manager tools are tied to the company scope, managers see download data only for documents owned by their own company. There is no cross-company visibility, even for users that belong to multiple companies.


---

# Agent Instructions: 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:

```
GET https://docs.flylogs.com/fcom/documents/manager-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.