> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/library-packs/l1-support/workflow-browser-behavior-awareness.md).

# Workflow: Browser behavior awareness

A Nexthink automation pack that detects recent browser updates and delivers just-in-time guidance on Local Network Access prompts, reducing IT tickets, improving user confidence, and strengthening security outcomes.

## Problem <a href="#problem" id="problem"></a>

Recent browser updates have introduced a new type of permission prompt (e.g., "Local network access required") that confuses users. Users often create unnecessary IT tickets for guidance, which slows down response times.

## Solution <a href="#solution" id="solution"></a>

This content pack helps IT teams reduce browser-related support demand by proactively guiding employees through new browser security prompts introduced by recent updates. It uses Nexthink Workflows to detect devices that have recently updated their browser and automatically triggers a short educational campaign at the right time - when users are most likely to encounter unfamiliar prompts.

The campaign focuses specifically on the Local Network Access prompt, explaining in plain language what it means and how to respond safely (allow only for trusted business sites; block if unsure). A dedicated dashboard provides visibility into browser version distribution and recent update activity, and tracks campaign delivery and user responses to measure adoption and effectiveness.

### Benefits and outcome <a href="#expected-value" id="expected-value"></a>

By implementing the **Browser behavior awareness** library pack, you:

* Reduce IT tickets through proactive guidance
* Improve update adoption with timely education
* Strengthen security with safer user decisions
* Reduce risk from untrusted access approvals
* Ensure consistent security messaging
* Gain visibility into browser updates and versions
* Measure impact with campaign engagement
* Scale easily with automated Workflows

### Getting started with "Browser behavior awareness" <a href="#getting-started-with-license-reclamation" id="getting-started-with-license-reclamation"></a>

Configure and start using your pack by following these links:

* [Usage guide: Browser behavior awareness](/library-packs/l1-support/workflow-browser-behavior-awareness/usage-guide-browser-behavior-awareness.md) for standard users.
* [Configuration guide: Browser behavior awareness](/library-packs/l1-support/workflow-browser-behavior-awareness/configuration-guide-browser-behavior-awareness.md) only accessible to users with an [administrator](/user-guide/administration/account-management/roles.md#roles-administration) role.


---

# 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.nexthink.com/library-packs/l1-support/workflow-browser-behavior-awareness.md?ask=<question>&goal=<user_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.