> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/documentation/protect/protect-features/guardware-protect-monitor.md).
# GuardWare PROTECT Monitor
The GuardWare PROTECT Monitor, visible in your system tray, serves as the client-side endpoint interface that allows you to monitor and manage the PROTECT agent on the endpoint.
It gives you a real-time view of:
* Your Azure login details (Azure User Principal Name (usually your email address), Tenant ID, and Subscription ID associated with the tenant)
* The PROTECT Agent version installed on the device
* Which Security Group you are in
* Which PROTECT features are available and unavailable to you
* Core components and databases of GuardWare PROTECT
* Enabling and exporting logs for troubleshooting
You can also enable or disable PROTECT for an endpoint from the PROTECT Monitor. This turns off all PROTECT protection on that device. However, you need the password set by your administrator to disable PROTECT.
## Refresh Icon
Use the **Refresh Icon** if icon overlays are missing in protected files or do not update after updating file protection settings.
For example, if you install new applications, such as AutoCAD or Microsoft Word, on a device with PROTECT installed, protected files associated with those applications may not show icon overlays right away. In that case, you can use **Refresh Icon** to update the icons.
## Login/Logout Button
The Login/Logout button allows you to manually authenticate with Azure if required. You can use it if your session has expired or Azure details have changed.
## Users
The **Users** page shows the Security Groups and PROTECT user policies applied to users. It also shows which PROTECT actions you are permitted to perform.
### Security Groups
This section shows which Security Groups your user account belongs to. A **Security Group** is a set of users within your organisation who have specific access permissions. Once a file is protected, Security Groups determine who can access the file. Only members of the authorised Security Groups can open or modify the file; others are restricted, ensuring it remains secure and accessible only to authorised users.
### Applied Policies
This section lists the PROTECT user policies currently applied to the user. These policies determine which PROTECT actions you can perform, such as adding, changing, removing, or sharing protection.
A green check mark indicates that the action is permitted. A red X indicates that the action is not permitted. Some policies also specify whether you can process multiple files at once or whether you must provide a reason for the action.
## Database
The **Database** page shows the PROTECT configuration data currently available on your device. This includes reports, applications, websites, classifications, Explorer menu settings, key servers, user policy settings, and other PROTECT settings.
Each item displays:
* Its current version number
* The date and time it was last updated
* Its update status
A green check mark indicates that the item is up to date.
Click **Refetch All** to update all database items. The **Uploads Pending** indicator shows how many updates are waiting to be uploaded. This value increases temporarily when logs or reports are being sent to the backend.
## Components
This **Components** page displays the status of the core components of GuardWare PROTECT. If any of the listed components are not running or are stopped, click **Restart**.
You can also enable or disable PROTECT for an endpoint from the Components page. Disabling PROTECT turns off all PROTECT protection on that device. To disable PROTECT, enter the password configured by your administrator.
**GWPROTECTCLIENT**
GWPROTECTCLIENT handles communication with the GuardWare PROTECT server and fetches and enforces server-side settings and user policies.
If the GWPROTECTCLIENT service is not running, the client may not reflect the latest server settings.
**FE2POLICY**
FE2POLICY manages file encryption and decryption decisions. It determines which applications are allowed to encrypt or decrypt files by listening to and processing driver-level calls and events. Based on these events, FE2POLICY evaluates policies and decides whether the requested operation should be permitted.
If the FE2POLICY service is not running, encryption requests are not processed, decryption requests fail, and protected files cannot be accessed as expected.
**GWDIRECTORYMONITOR**
GWDIRECTORYMONITOR is responsible for folder-based encryption. It continuously monitors configured directories and detects file activity within protected folders, and ensures encryption policies are consistently applied at the folder level.
In addition, GWDIRECTORYMONITOR launches required user-facing components, such as GWPROTECTDESKTOP.
If the GWDIRECTORYMONITOR service is not running, folder-based encryption and related user interactions do not function correctly.
**GWPROTECTDESKTOP**
GWPROTECTDESKTOP handles file decryption by providing the required decryption keys to authorised processes. It also handles secure sharing features, such as sharing protected files as ZIP, MIP, or secure HTML, adding expiry dates, and restricting further circulation.
If the GWPROTECTDESKTOP service is not running, file decryption and sharing features do not function properly.
## Logs
The **Logs** page lets you enable diagnostic logging and export log files for troubleshooting.
#### Enable Logs
Turn on **Enable Logs** to record diagnostic information. Because logging may affect system performance, you can select an **Auto-disable after** period to turn it off automatically.
#### Export Logs
Select **Export** to copy PROTECT logs to your clipboard. You can use it when Support requests logs, or you need to share diagnostic information.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.guardware.com/documentation/protect/protect-features/guardware-protect-monitor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
