---
title: Installed with DEX
description: Several types of components are installed with activation of the DEX application \[sn\_dex\] plugin, including user roles and tables.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/digital-end-user-experience-dex/components-installed-with-dex.html
release: australia
product: Digital End-User Experience \(DEX\)
classification: digital-end-user-experience-dex
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 1
keywords: [dex components, dex roles, dex administrator role, dex engineer role, dex user role, dex service desk agent, dex application table, metric rules table, alert metadata table, alert impacted users table, alert locations table, action app config table, ci device configuration table]
breadcrumb: [DEX Application and Device Health reference, Reference, Digital End-User Experience, IT Service Management]
---
# Installed with DEX
Several types of components are installed with activation of the DEX application \[sn\_dex\] plugin, including user roles and tables.
## Roles installed
|
Role title \[name\]
|
Description
|
Contains roles
|
|---|
|
DEX administrator \[sn\_dex.admin\]
|
Responsible for managing user access to DEX, managing the applications that are being monitored, and handling onboarding/offboarding-related tasks. They also troubleshoot any issues that arise within the application.
|
- agent\_client\_collector\_admin
- report\_admin
- sn\_dex.user
- sn\_dex.engineer
- sn\_cmdb\_editor
|
|
DEX engineer \[sn\_dex.engineer\]
|
Responsible for accessing and executing the remedial actions.
|
sn\_dex.user
|
|
DEX user \[sn\_dex.user\]
|
Responsible for accessing and using the features provided by DEX.
|
- agent\_client\_collector\_user
- cmdb\_read
- dependency\_views
- mbplus\_reader
- sam\_user
- sn\_cmdb\_editor
- sn\_incident\_read
- sn\_sow.sow\_home
- sn\_sow.sow\_list
- sn\_sow.sow\_user
|
|
DEX Service Desk agent\[sn\_dex.service\_desk\_user\]
|
Responsible for L1 or L2 support representatives accessing DEX from the incident platform to explore and investigate the details of the devices linked to the incident.
|
Not applicable
|
## Tables installed
|
Table
|
Description
|
|---|
|
DEX Application\[dex\_application\]
|
Parent table that stores a list of all the applications configured for monitoring on the **Administration** > **Applications** page. The table extends the parent table sn\_acc\_vis\_content\_application in the Agent Client Collector for Visibility Content scoped app.
|
|
Metric Rules\[dex\_metric\_rules\]
|
Table that stores all the DEX metric rules.
|
|
Alert Metadata\[dex\_alert\_metadata\]
|
Table that stores data about incoming events from the metric rules.
|
|
Alert Impacted Users\[dex\_alert\_impacted\_users\]
|
Table that stores data about users or devices, which are impacted for a given metric rule.
|
|
Alert Locations\[dex\_alert\_location\]
|
Table that stores data about locations, which are impacted for a given metric rule.
|
|
Action App Config\[dex\_action\_app\_config\]
|
Table that stores applications, which support the clear app cache action.
|
|
CI Device Configuration\[dex\_ci\_device\_config\]
|
Table that stores the device configuration data including the logged-in user information.For information on the related policies and check definitions, see [DEX Content Playbook reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/digital-end-user-experience-dex/dex-content-playbook-reference.md).
|
**Parent Topic:**[DEX Application and Device Health reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/digital-end-user-experience-dex/dex-console-reference.md)