---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Browser extension permissions

# DEX browser extension permissions and data collection {#ariaid-title1}

Release version: Australia  
Updated August 25, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The DEX browser extension requests specific browser permissions to measure the performance, availability, and usage of monitored web applications. Each permission is limited to the
minimum access required for that measurement purpose.

## How web application usage data is collected {#dex-browser-extension-permissions__section_collecting-web-app-data}

Application usage data is collected differently depending on whether the application is installed on the endpoint or accessed through a browser:

* Installed application usage data is collected by the Agent Client Collector (ACC) installed on the endpoint.
* Web application usage data is collected by the DEX browser extension for Google Chrome and Microsoft Edge. The extension reports the collected data through the same channel used by ACC: data is routed from the browser extension to ACC, and then sent to the ServiceNow shared services and on to your instance.

{#dex-browser-extension-permissions__ul_app-data-collection-methods}

To collect this data, the browser extension requests the browser permissions described in the following table. Each permission is limited to the minimum access required to measure page performance and availability for
monitored applications. The extension does not read page content, form data, cookies, or credentials.

## Permissions requested by the browser extension {#dex-browser-extension-permissions__section_permissions-requested}

{#dex-browser-extension-permissions__table_browser-extension-permissions__entry__2}

| Permission | Purpose |
|-|-|
| Storage | Temporarily saves collected performance metrics, such as page load times and session data, on the local device between collection intervals, before the data is sent to your instance. |
| Active Tab | Identifies the currently active tab so the extension can determine which tab to collect and update data for while a user is viewing it. |
| Tabs | Detects when a monitored application's tab is opened, kept open, or closed, to determine what session and usage data to record. This permission applies only to tabs recognized as monitored applications. |
| Alarms | Triggers metric collection and reporting on a recurring schedule instead of continuously, to minimize the impact on browser performance. |
| Web Request | Observes network requests made by monitored applications, specifically counting successful and failed requests, to calculate an application availability score. |
| Declarative Net Request | Adjusts the Origin and Content-Type request headers on requests sent to the extension's own reporting service, so that they meet the security requirements of that service. |
| Declarative Net Request with Host Access | Works with the Declarative Net Request permission, but restricts the header adjustment to a single, specific destination. This ensures the adjustment can't affect requests to any other site. |
| Host Permission (access to site URLs) | Reads the URL of open browser tabs, so the extension can determine when a monitored application was opened and how long it remained open. This is the basis for the usage and performance metrics shown in your instance. |
[Table 1. Browser permissions and their purpose]

{#dex-browser-extension-permissions__table_browser-extension-permissions}

## Scope of data collected {#dex-browser-extension-permissions__section_scope-of-data-collected}

* The extension extracts only standard browser performance timing data, such as page load, network, and response timings. It does not access page content, form inputs, cookies, or credentials.
* The Web Request and Declarative Net Request permissions are used narrowly: to count request successes and failures, and to adjust two specific headers on calls to the extension's own reporting service. They aren't used to read or modify the content of requests or responses to any other site.
* The Host Permission and Tabs permissions require broad tab and URL visibility because the extension can't determine in advance which sites are your monitored applications. That determination happens at runtime, and only recognized monitored applications have their data recorded.
* Collected metrics are limited to performance and availability statistics, such as load times, session duration, and request success or failure counts, tied to monitored application URLs. The extension reports metrics only to your own instance.
{#dex-browser-extension-permissions__ul_scope-notes}
**Related concepts**   

* [DEX Architecture](https://servicenow-prod.fluidtopics.net/W~_XWZu9hWRobshdEW~VDg "Digital End-User Experience (DEX) architecture describes the cloud-native services, endpoint agents, and data flows that connect end-user devices to your ServiceNow instance.")  
**Related tasks**   

* [Enable DEX browser extension](https://servicenow-prod.fluidtopics.net/gInyzpRs4jIn~~IxAoU_ew "Activate the DEX Chrome or Edge Extension on your system to collect different operational or performance-based metrics for the web applications.")  
**Related reference**   

* [Installed with DEX](https://servicenow-prod.fluidtopics.net/glC1xESxsZ4hagcNeeR2ig "Several types of components are installed with activation of the DEX application [sn_dex] plugin, including user roles and tables.")