> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/library-packs/security-and-compliance/workflow-chrome-update-compliance/usage-guide-chrome-update-compliance.md).

# Usage guide: Chrome update compliance

### Overview <a href="#overview" id="overview"></a>

Maintaining updated web browsers is vital for security and efficiency, but managing updates can be difficult. Employees might neglect updates, leading to outdated Chrome versions on enterprise devices, posing security risks and limiting productivity. “Workflow: Chrome update compliance” pack helps to keep Chrome updated. It checks if the running Chrome version matches the latest one and prompts a restart if not. After two prompts, if not updated, it automatically restarts Chrome.

Ensure your library pack is properly configured by following the steps highlighted in its configuration guide:

[Configuration guide: Chrome update compliance](/platform/library-packs/security-and-compliance/workflow-chrome-update-compliance/configuration-guide-chrome-update-compliance.md)

### Workflow Structure <a href="#workflow-structure" id="workflow-structure"></a>

This workflow is designed to operate automatically via an schedule trigger. This section describes the key steps in this workflow:

* The workflow starts by checking whether the Chrome browser requires a restart due to an pending update. If no update is pending and a restart isn’t necessary, the workflow ends processing.

<figure><img src="/files/gg46TKY3rcaFo4GQdYDh" alt="" width="563"><figcaption></figcaption></figure>

If a restart is needed then the campaign is triggered to inform the user about the need of restarting the browser.

<figure><img src="/files/t3NOWgjN5chV5j80zDh7" alt="" width="525"><figcaption></figcaption></figure>

* In case the user consents, the remote actions restarts the browser and workflow terminates, recording that the necessary action has been taken.
* If the user declines the Chrome browser restart, the workflow makes another attempt after a delay. In this scenario, if a restart is still required and the user once again refuses to restart the Chrome browser, a forced restart is implemented after a delay.

<figure><img src="/files/WvnQLcIKZtWBKGks0Cab" alt="" width="563"><figcaption></figcaption></figure>

RELATED TOPICS

* [Manage Workflows](https://docs.nexthink.com/platform/user-guide/workflows/managing-workflows)
* [Manage Remote Actions](https://docs.nexthink.com/platform/user-guide/remote-actions/getting-started-with-remote-actions)
* [Manage Campaigns](https://docs.nexthink.com/platform/user-guide/campaigns/managing-campaigns)


---

# 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:

```
GET https://docs.nexthink.com/platform/library-packs/security-and-compliance/workflow-chrome-update-compliance/usage-guide-chrome-update-compliance.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.