# Curbing Distractions

We360.ai's domain blocking feature allows administrators to actively prevent access to distracting or policy-violating websites at the endpoint level — enforced by the desktop agent itself.

{% hint style="warning" %}
Domain blocking requires the We360.ai desktop agent to be running. It does not function as a network-level firewall and applies only on machines where the agent is installed.
{% endhint %}

## Setup Steps

{% stepper %}
{% step %}

#### Access URL Blocking

Go to **Settings → Compliance & Security → URL Blocking**. This panel allows you to create a blacklist of domains.
{% endstep %}

{% step %}

#### Add Domains to Block

Enter the domain(s) you want to restrict (e.g., `facebook.com`, `youtube.com`, `reddit.com`). Subdomains are automatically included. You can add as many as needed.
{% endstep %}

{% step %}

#### Assign to Teams (Optional)

By default, blocking rules apply organization-wide. You can scope them to specific teams — for example, blocking social media only for the support or engineering teams, while allowing it for marketing.
{% endstep %}
{% endstepper %}

<details>

<summary>What happens when a blocked domain is accessed?</summary>

When an employee attempts to navigate to a blocked domain, the agent intercepts the request at the browser level and the page fails to load. The access attempt is also logged in the **Alerts** dashboard, with a timestamp and employee name.

</details>


---

# 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.we360.ai/how-to-and-best-practices/optimizing-productivity-and-focus/curbing-distractions.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.