> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/website-visited.md).

# Website visited

## Visited website trigger

Trigger **Visited website** enables management of access to websites and monitoring of user activity in web browsers. This management is supported by advanced artificial intelligence **BTC Web Classification**, using machine learning and deep learning technologies for precise site classification.

## Trigger configuration

{% stepper %}
{% step %}

### Website masks

* **Website mask:**
  * Defines sites to be monitored.
  * Works analogously to path masks, e.g.:
    * `www.test.pl`
    * `www.test/test*.com`.
* **Excluded website mask:**
  * Specifies exceptions that will not be monitored.

<div align="left"><figure><img src="/files/0aa23b3efea5d4a1161faee6d163e6f9e846a066" alt="" width="95"><figcaption></figcaption></figure></div>

[How to add/edit a mask?](/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/file-operations/masks.md)
{% endstep %}

{% step %}

### Process masks

* **Process mask:**
  * Restricts monitoring to specific web browsers.
  * Example: `chrome.exe`, `firefox.exe`.
  * Optionally monitor all, i.e. `*` and exclude selected ones.
* **Excluded process mask:**
  * Allows excluding selected browser processes from monitoring.

<div align="left"><figure><img src="/files/eb9aa89f15d18d6be31c9f182c31f604e6f5fb7f" alt="" width="96"><figcaption></figcaption></figure></div>

[How to add/edit a mask?](/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/file-operations/masks.md)
{% endstep %}

{% step %}

### Website categories

* **Website categories:**
  * A multi-select list containing various types of websites (e.g., “Games”, “Finance & Banking”, “Social Media”).
  * If no category is selected, the policy operates regardless of category.
* **Excluded website categories:**
  * Allows specifying categories to be excluded from monitoring.
* **Three-position switch:**
  * Facilitates choosing between the “include” and “exclude” options.
  * **Left (exclude):** The switch changes color to black.
  * **Right (include):** The switch changes color to green.

<div align="left"><figure><img src="/files/1fd491fa35b5140156f064f2206e4615084a0ae0" alt="" width="94"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

### List of supported site categories

Example categories available in the system:

* Finance, Banking & Insurance
* Games
* Gambling
* Career, Education & Religion
* Computers, Software & Electronics
* Culinary & Restaurants
* People & Social Media
* Malware
* Media, News & Weather
* Automotive & Transportation
* Dangerous site structure
* Unrecognized language
* Real Estate, Home & Garden
* Politics, Law & Government Institutions
* Pornography
* Industry, Business & Services
* Entertainment
* Sports
* Login page
* Art & Culture

The full list of categories contains dozens of entries, allowing precise policy tailoring.

## Example of use

**Objective:** Restrict access to gossip sites for the sales department during working hours.

* **Configuration:**
  * Select the “Entertainment” category and set the switch to **include** (green).
  * Set the process mask to the browsers used in the company, e.g. `chrome.exe`.
  * Define actions in the next step — block.

**Effect:**

* Sales department users will not have access to gossip sites.
* Every attempt to access such a site will be recorded in the system logs.

## Summary

Trigger **Visited website** allows effective management of access to websites, supporting security and productivity policies in the organization. With advanced configuration features such as masks, categories and intelligent site classification, the tool provides precise control over user activity in browsers.


---

# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/website-visited.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.
