> For the complete documentation index, see [llms.txt](https://enterprise.hideez.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enterprise.hideez.com/hideez-enterprise-server/audit/workstation-sessions.md).

# Workstation Sessions

To view Workstations Sessions, go to the appropriate “**Audit - Sessions**” section. 

![](/files/T5zsLn8udUMpM3i2uie5)

A session is the period of time between unlocking the computer and the event leading to its locking.

Log table fields:

* Start Time - the point in time when the session was started
* End Time - the point in time when the session was completed
* Duration - session duration
* Unlocked By - how the session was started - with a dongle or without Hideez
* Computer - computer name
* User Session - the name of the user account on the computer
* Device SN - the serial number of the device if the session was started using the Hideez Key
* Employee, Company, Department - employee information (employee name, company, department)
* Account Name - the name of the account used
* Account Type - account type (personal or shared)


---

# 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://enterprise.hideez.com/hideez-enterprise-server/audit/workstation-sessions.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.