> For the complete documentation index, see [llms.txt](https://help.partek.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.partek.illumina.com/partek-flow/user-manual/settings/access/access-control-log.md).

# Access Control Log

*Access control log* is administrative tool giving an overview of Partek Flow users' access privileges. The tool focuses on activities related to [*User management*](/partek-flow/user-manual/settings/access/user-management.md#user-management-page) and *Group management*. To invoke it, first log in as a user with administrative privileges and then go to **Settings** > *Access management* > **Access control log**. Example report is given in Figure 1.

<figure><img src="/files/mWoLuaODhDEksgRa5qYq" alt=""><figcaption><p>Figure 1. Example output of Access control log</p></figcaption></figure>

The first column (*Time*) contains the timestamp of the activity. Column *Changer* shows you the display name of the Partek Flow user who changed the access along with their permanent numeric identifier (parenthesized). The current display name of the changed user, as well as the matching numeric ID, can be seen in the *Object* column. Finally, the change made to the object, followed by the project (the number in the parenthesis is the change counter), role or privilege is listed in the *Change* column. Text boxes on top of each column are search tools, while the arrows icon enables to sort the column ascending or descending.

### Additional Assistance <a href="#accesscontrollog-additionalassistance" id="accesscontrollog-additionalassistance"></a>

If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.


---

# 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.partek.illumina.com/partek-flow/user-manual/settings/access/access-control-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.