---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# License key discovery and access control tables

# License key discovery and access control tables {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Reference information for the tables, fields, access control, and scheduled job used by license key discovery in Agent Client Collector for Visibility Content.

## Tables {#license-key-discovery-reference__license-key-discovery-reference-tables}

License key discovery uses the following tables.{#license-key-discovery-reference__license-key-discovery-reference-para-1}
{#license-key-discovery-reference__license-key-discovery-tables-overview__entry__3}

| Table | Label | Purpose |
|-|-|-|
| sn_acc_vis_content_license_registry_config | License Registry Configuration | Admin-managed list of registry paths and value names to collect from managed endpoints. |
| sn_acc_vis_content_license_keys | License Keys | Stores the license key values collected from endpoint devices. |
[Table 1. License key discovery tables]

{#license-key-discovery-reference__license-key-discovery-tables-overview}

## License Keys table fields {#license-key-discovery-reference__license-key-discovery-reference-fields}

The License Keys \[sn_acc_vis_content_license_keys\] table stores the following fields for each discovered key.{#license-key-discovery-reference__license-key-discovery-reference-para-2}
{#license-key-discovery-reference__license-key-discovery-keys-fields__entry__2}

| Field | Description |
|-|-|
| Configuration Item | Device the key was collected from. Table: cmdb_ci_computer. |
| Product | SAM product associated with this key. Table: samp_sw_product. |
| User | This field is automatically set to the user assigned to the CI. Table: sys_user. |
| License Key Config | Configuration rule that discovered this key. Table: sn_acc_vis_content_license_registry_config. |
| Resolved Registry Path | Exact registry path the key was read from on the endpoint. |
| License Key | Discovered key value. |
| Last Scanned | Date the key was last detected by the agent. |
| Absent | Selected when the key is no longer found on the device. Records are never deleted, they are marked Absent instead. |
[Table 2. License Keys form]

{#license-key-discovery-reference__license-key-discovery-keys-fields}

## License Registry Configuration form fields {#license-key-discovery-reference__license-key-discovery-reference-registry-config}

The following table describes the fields in the License Registry Configuration \[sn_acc_vis_content_license_registry_config\] table.{#license-key-discovery-reference__license-key-discovery-reference-para-5}
{#license-key-discovery-reference__license-key-discovery-registry-config-fields__entry__2}

| Field | Description |
|-|-|
| Product | SAM product this license key belongs to. Links to the SAM Professional product catalog. |
| Registry Path | Windows registry path where the key is stored. For example, HKLM\\SOFTWARE\\Microsoft\\Office\\16.0\\Registration. |
| Registry Value Name | Specific registry value to read. For example, DigitalProductId. |
| Name | This field is automatically set to a combination of the Product and Registry Value Name values. |
| Description | Notes about this configuration record. |
| Active | Indicator of whether this record is included in future collections. Clearing this check box removes the record from future collections. |
[Table 3. License Registry Configuration form]

{#license-key-discovery-reference__license-key-discovery-registry-config-fields}  
Note:  
The combination of Product, Registry Path, and Registry Value Name must be unique across all configuration records.

## Access control {#license-key-discovery-reference__license-key-discovery-reference-access}

The following table shows which roles can access each license key discovery table.{#license-key-discovery-reference__license-key-discovery-reference-para-3}
{#license-key-discovery-reference__license-key-discovery-access-table__entry__3}

| Role | License Registry Configuration table | License Keys table |
|-|-|-|
| ACC application admin (agent_client_collector_admin) | Read, write, create | Read only |
| Discovery admin (discovery_admin) | Read, write, create | Read only |
| SAM admin (sam_admin) | Read only | Read only |
| All other roles | No access | No access |
[Table 4. License key discovery role access]

{#license-key-discovery-reference__license-key-discovery-access-table}

## Scheduled job {#license-key-discovery-reference__license-key-discovery-reference-job}

The following scheduled job supports license key discovery.{#license-key-discovery-reference__license-key-discovery-reference-para-4}
{#license-key-discovery-reference__license-key-discovery-job-table__entry__3}

| Job | Schedule | Condition |
|-|-|-|
| Refresh License Key Config File | Daily at 8:30 a.m. UTC | Runs only when the sn_acc_vis_content.enable_license_key_discovery property is set to <kbd class="ph userinput">true</kbd> and the SAM Professional plugin (com.snc.samp) is activated. |
[Table 5. License key discovery scheduled job]

{#license-key-discovery-reference__license-key-discovery-job-table}