> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parable.work/llms.txt
> Use this file to discover all available pages before exploring further.

# ServiceNow

> ServiceNow is an enterprise IT service management (ITSM) and business workflow platform. It provides a unified system of record for IT services, operations, HR, security, and more. Data is accessed primarily through the Table API, a REST interface that provides access to every table in the platform using offset-based pagination and incremental sync via sys_updated_on timestamps.

ServiceNow is an enterprise IT service management (ITSM) and business workflow platform. It provides a unified system of record for IT services, operations, HR, security, and more. Data is accessed primarily through the Table API, a REST interface that provides access to every table in the platform using offset-based pagination and incremental sync via sys\_updated\_on timestamps.

<Tabs>
  <Tab title="Overview">
    ### OAuth 2.0 Client Credentials

    Connect Parable to ServiceNow via **OAuth 2.0 client credentials** against the Table API. Parable syncs people, ITSM work items, catalog request rows, and audit history.

    ### Basic Authentication (Username/Password)

    ## ServiceNow — Basic Auth

    Connect Parable to ServiceNow with HTTP Basic authentication (integration username and password) against the Table API.

    Prefer OAuth 2.0 client credentials for production. Basic auth is useful for personal developer instances (PDI) and early validation.

    ## Data streams

    This Provider Plugin defines 15 data streams.

    | Stream              | Description                                                                                                                                                                                                                                 | Sync        |
    | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
    | `sys_user`          | Extracts all user records from ServiceNow sys\_user table, including name, email, roles, department, manager, active status, and system metadata.                                                                                           | incremental |
    | `sys_user_group`    | Extracts all user group records from ServiceNow sys\_user\_group table, including group name, description, manager, parent group, and type.                                                                                                 | incremental |
    | `sys_user_grmember` | Extracts user-to-group membership records from ServiceNow sys\_user\_grmember table, linking users to their groups.                                                                                                                         | incremental |
    | `cmn_department`    | Extracts department records from ServiceNow cmn\_department table, including department name, head, parent department, and company.                                                                                                         | incremental |
    | `cmn_location`      | Extracts location records from ServiceNow cmn\_location table, including name, address, city, state, country, and coordinates.                                                                                                              | incremental |
    | `core_company`      | Extracts company records from ServiceNow core\_company table, including company name, contact info, and parent company.                                                                                                                     | incremental |
    | `incident`          | Extracts incident records from ServiceNow. Incidents represent reported issues or service disruptions that need resolution. Core ITSM table.                                                                                                | incremental |
    | `incident_task`     | Extracts incident tasks from ServiceNow. Incident tasks are work items created to track and resolve an incident.                                                                                                                            | incremental |
    | `problem`           | Extracts problem records from ServiceNow. Problems represent the root cause of one or more incidents and are used in problem management processes.                                                                                          | incremental |
    | `change_request`    | Extracts change request records from ServiceNow. Change requests track planned changes to IT infrastructure and services through a formal change management process.                                                                        | incremental |
    | `sc_request`        | Extracts service catalog requests (sc\_request table) from ServiceNow. These represent user-initiated requests for services, hardware, software, or other catalog items.                                                                    | incremental |
    | `sc_req_item`       | Extracts requested items (catalog items ordered through the service catalog) from ServiceNow. Each record represents a single line item within a service catalog request, tracking fulfillment status, assigned groups, and approval state. | incremental |
    | `sc_task`           | Extracts catalog tasks from ServiceNow. Catalog tasks are work items created to fulfill requested items from the service catalog, representing individual steps in the fulfillment process.                                                 | incremental |
    | `sys_audit`         | Extracts audit log records from the sys\_audit table. Each record captures a single field-level change on an audited record, providing a detailed who-changed-what-when trail across the platform.                                          | incremental |
    | `sys_audit_delete`  | Extracts deleted record audit entries from ServiceNow. Tracks records that have been deleted from audited tables, enabling detection of deletions for incremental sync.                                                                     | incremental |
  </Tab>

  <Tab title="Setup Guide">
    ### OAuth 2.0 Client Credentials

    #### What You'll Need

    | Credential        | What it is                                                                 |
    | ----------------- | -------------------------------------------------------------------------- |
    | **Instance**      | ServiceNow instance id (subdomain in `https://{instance}.service-now.com`) |
    | **Client ID**     | OAuth application Client ID                                                |
    | **Client Secret** | OAuth application Client Secret                                            |

    Optional fallback: a dedicated integration username and password for basic auth.

    * Admin access to create an OAuth API endpoint / application and assign roles
    * A service account (or OAuth Application User) with read access to the tables Parable syncs
    * For `sys_audit` / `sys_audit_delete`: table ACLs beyond `snc_read_only` (custom role with read on those tables)

    #### Step 1: Create an OAuth application

    1. In ServiceNow, open **System OAuth** → **Application Registry**
    2. Create a new **OAuth API endpoint for external clients**
    3. Note the **Client ID** and **Client Secret**
    4. Confirm the token endpoint is `https://{instance}.service-now.com/oauth_token.do`
    5. Bind an **OAuth Application User** (Tokyo+). Client-credentials grants need a user context; without it, token exchange may succeed while Table API calls return 401/403.

    #### Step 2: Assign integration roles

    1. Open the OAuth Application User (or a dedicated integration user)
    2. Grant read access for:

    | Table                                             | Purpose                                   |
    | ------------------------------------------------- | ----------------------------------------- |
    | `sys_user`, `sys_user_group`, `sys_user_grmember` | People and groups                         |
    | `cmn_department`, `cmn_location`, `core_company`  | Org reference data                        |
    | `incident`, `problem`, `change_request`           | ITSM work                                 |
    | `sc_request`, `sc_req_item`, `sc_task`            | Catalog requests                          |
    | `sys_audit`, `sys_audit_delete`                   | Field-level history (requires custom ACL) |

    #### Step 3: Connect in Parable

    1. Add the ServiceNow Provider
    2. Enter **Instance**, **Client ID**, and **Client Secret**
    3. Validate credentials (Parable exchanges a client-credentials token and probes `sys_user`)

    ### Basic Authentication (Username/Password)

    | Field    | Description                                       |
    | -------- | ------------------------------------------------- |
    | Instance | Subdomain in `https://{instance}.service-now.com` |
    | Username | Dedicated integration user                        |
    | Password | Password for that user                            |

    1. Create a dedicated integration user in ServiceNow (**User Administration → Users**).

    2. Grant read ACLs on the tables Parable syncs (users/groups/org, ITSM, catalog, and optionally audit tables).

    3. Confirm Table API access:

       ```bash theme={null}
       curl -u "$SN_USER:$SN_PASSWORD" \
         "https://{instance}.service-now.com/api/now/table/sys_user?sysparm_limit=1&sysparm_display_value=false"
       ```

    4. In Parable, add ServiceNow, choose **Basic Auth**, enter instance + username + password, and validate.

    Wake hibernating developer instances in a browser before validation (they can return HTML with HTTP 200).
  </Tab>

  <Tab title="Permissions">
    <AccordionGroup>
      <Accordion id="provider-permission-tap-servicenow-change-request-281d392fdfbb" title="Change Request" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `change_request`

        Change Request covers change request records from ServiceNow. Change requests track planned changes to IT infrastructure and services through a formal change management process.

        * **Enables:** follow service work from the reported record through its returned assignee, status, priority, and timestamps during triage or fulfillment.
        * **Scope:** Extracts change request records from ServiceNow. Change requests track planned changes to IT infrastructure and services through a formal change management process; the connector reads `/api/now/table/change_request` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-change-request-active-566d259e5477" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.active`

            Active records whether the change request is active. It is needed to distinguish Change Request rows by the exact ServiceNow-returned active value.

            * **Enables:** select Change Request rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-activity-due-f7fb3af2e155" title="Activity Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.activity_due`

            Activity Due records date/time the next activity is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `activity_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-additional-assignee-li-a64eef708f79" title="Additional Assignee List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.additional_assignee_list`

            Additional Assignee List records comma-separated list of `sys_ids` of additional assignees. It is needed to refer to the same additional assignee list across records without relying on display text.

            * **Enables:** match `additional_assignee_list` to additional assignee list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-approval-be2aea5989fd" title="Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.approval`

            Approval records overall approval status of the change request. Instance-customizable choice; known defaults include: not yet requested, requested, approved, rejected, cancelled. It is needed to distinguish Change Request rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-approval-history-0e305d48b79e" title="Approval History" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.approval_history`

            Approval History records journal field capturing approval history. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `approval_history` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-approval-set-bf6a1d760e21" title="Approval Set" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.approval_set`

            Approval Set records date/time when the approval was set. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `approval_set`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-assigned-to-5fc479f4f66c" title="Assigned To" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.assigned_to`

            Assigned To records `Sys_id` of the individual assigned to implement the change. It is needed to refer to the same assigned to across records without relying on display text.

            * **Enables:** match `assigned_to` to assigned to references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-assignment-group-4c1669d3af4b" title="Assignment Group" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.assignment_group`

            Assignment Group records `Sys_id` of the group assigned to implement the change. It is needed to refer to the same assignment group across records without relying on display text.

            * **Enables:** match `assignment_group` to assignment group references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-backout-plan-3b50d3feb2ec" title="Backout Plan" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.backout_plan`

            Backout Plan records plan for reverting the change if implementation fails. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `backout_plan` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-business-service-8e56faa70bf5" title="Business Service" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.business_service`

            Business Service records `Sys_id` of the business service affected by the change. It is needed to refer to the same business service across records without relying on display text.

            * **Enables:** match `business_service` to business service references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-cab-date-13bb7bb9862b" title="Cab Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.cab_date`

            Cab Date records date/time of the CAB meeting for this change. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `cab_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-cab-delegate-1ddf3e0b66c6" title="Cab Delegate" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.cab_delegate`

            Cab Delegate records `Sys_id` of the CAB delegate for this change. It is needed to refer to the same cab delegate across records without relying on display text.

            * **Enables:** match `cab_delegate` to cab delegate references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-cab-recommendation-5ea50b2a6e5d" title="Cab Recommendation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.cab_recommendation`

            Cab Recommendation records recommendation from the Change Advisory Board. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `cab_recommendation` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-cab-required-1da75f81472b" title="Cab Required" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.cab_required`

            Cab Required records whether Change Advisory Board review is required. It is needed to distinguish Change Request rows by the exact ServiceNow-returned cab required value.

            * **Enables:** select Change Request rows where `cab_required` is true or false when comparing the condition described by Cab Required.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-category-44b9701b37c0" title="Category" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.category`

            Category records category of the change, e.g. Hardware, Software, Network. It is needed to distinguish Change Request rows by the exact ServiceNow-returned category value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `category` label when comparing category.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-change-plan-32b84170670d" title="Change Plan" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.change_plan`

            Change Plan records detailed plan for implementing the change. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `change_plan` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-chg-model-ad8de731a3d8" title="Chg Model" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.chg_model`

            Chg Model records `Sys_id` of the change model used. It is needed to refer to the same chg model across records without relying on display text.

            * **Enables:** match `chg_model` to chg model references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-close-code-4a0f4eb38199" title="Close Code" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.close_code`

            Close Code records code indicating how the change was closed. Instance-customizable choice; known defaults include: successful, `successful_with_issues`, unsuccessful, cancelled. It is needed to distinguish Change Request rows by the exact ServiceNow-returned close code value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `close_code` label when comparing close code.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-close-notes-1510bb540f40" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.close_notes`

            Close Notes records notes entered when closing the change request. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-closed-at-432422a891fb" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.closed_at`

            Closed At records date/time when the change request was closed. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-closed-by-a528e86183b5" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.closed_by`

            Closed By records `Sys_id` of the user who closed the change request. It is needed to refer to the same closed by across records without relying on display text.

            * **Enables:** match `closed_by` to closed by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-cmdb-ci-74c9517bd582" title="Cmdb Ci" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.cmdb_ci`

            Cmdb Ci records `Sys_id` of the configuration item (CI) affected by the change. It is needed to refer to the same cmdb ci across records without relying on display text.

            * **Enables:** match `cmdb_ci` to cmdb ci references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-comments-58badfd35109" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.comments`

            Comments records customer-visible comments (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-comments-and-work-note-0b457f0b645e" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-company-1f19d6af2bcc" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.company`

            Company records `Sys_id` of the company associated with the change request. It is needed to refer to the same company across records without relying on display text.

            * **Enables:** match `company` to company references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-conflict-last-run-c2fe27f58b59" title="Conflict Last Run" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.conflict_last_run`

            Conflict Last Run records date/time of the last conflict detection run. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `conflict_last_run`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-conflict-status-23a28f6b78d9" title="Conflict Status" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.conflict_status`

            Conflict Status records status of conflict detection for this change. Instance-customizable choice; known defaults include: `not_run`, conflict, `no_conflict`. It is needed to distinguish Change Request rows by the exact ServiceNow-returned conflict status value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `conflict_status` label when comparing conflict status.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-contact-type-a79289e0dc24" title="Contact Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.contact_type`

            Contact Type records how the change request was initiated, e.g. phone, email, self-service. It is needed to distinguish Change Request rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-correlation-display-290c9a94c065" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.correlation_display`

            Correlation Display records display value for the correlation identifier. It is needed to refer to the same correlation display across records without relying on display text.

            * **Enables:** match `correlation_display` to correlation display references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-correlation-id-60d06fd845d4" title="Correlation ID" icon="link" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.correlation_id`

            Correlation ID records correlation identifier for linking to external systems. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-department-45305754913a" title="Department" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.department`

            Department records `Sys_id` of the department associated with the change request. It is needed to refer to the same department across records without relying on display text.

            * **Enables:** match `department` to department references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-description-c1345c091ba2" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.description`

            Description records detailed description of the change. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is description text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-due-date-823a13845d8d" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.due_date`

            Due Date records due date for the change request. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-end-date-4eb0f0afd8e6" title="End Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.end_date`

            End Date records planned end date/time of the change implementation. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `end_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-escalation-25de148f5085" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.escalation`

            Escalation records escalation level of the change request. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Change Request rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-expected-start-82ecc5be86e0" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.expected_start`

            Expected Start records expected start date/time for the change. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-follow-up-b948cbeff7d5" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.follow_up`

            Follow Up records follow-up date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-impact-10e4d3b8eb24" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.impact`

            Impact records impact level of the change on the organization. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Change Request rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-implementation-plan-278ea21b926d" title="Implementation Plan" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.implementation_plan`

            Implementation Plan records step-by-step implementation plan for the change. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `implementation_plan` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-justification-15afd88ed9c1" title="Justification" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.justification`

            Justification records business justification for the change. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `justification` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-knowledge-b5867e2e7046" title="Knowledge" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.knowledge`

            Knowledge records whether a knowledge article has been flagged for creation. It is needed to distinguish Change Request rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Change Request rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-location-f04e72af94b3" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.location`

            Location records `Sys_id` of the location associated with the change request. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Change Request row.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-made-sla-5075ceb1c15e" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.made_sla`

            Made Sla records whether the change request met its SLA. It is needed to distinguish Change Request rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Change Request rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-number-ed7789af7714" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.number`

            Number records human-readable change request number, e.g. CHG0001234. It is needed to refer to the same change request across records without relying on display text.

            * **Enables:** match `number` to change request references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-number-of-affected-cis-cd801cf8fcb4" title="Number Of Affected Cis" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.number_of_affected_cis`

            Number Of Affected Cis records number of configuration items affected by this change. It is needed to measure the ServiceNow-reported number of configuration items affected by this change at one Change Request record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of configuration items affected by this change in `number_of_affected_cis` at one Change Request record per row.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is a ServiceNow-reported count at one Change Request record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-on-hold-15c16920811e" title="On Hold" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.on_hold`

            On Hold records whether the change request is currently on hold. It is needed to distinguish Change Request rows by the exact ServiceNow-returned on hold value.

            * **Enables:** select Change Request rows where `on_hold` is true or false when comparing the condition described by On Hold.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-on-hold-reason-7d5744d82f4a" title="On Hold Reason" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.on_hold_reason`

            On Hold Reason records reason the change request is on hold. It is needed to distinguish Change Request rows by the exact ServiceNow-returned on hold reason value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `on_hold_reason` label when comparing on hold reason.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-on-hold-task-aa38bba61b67" title="On Hold Task" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.on_hold_task`

            On Hold Task records `Sys_id` of the task causing the hold. It is needed to refer to the same on hold task across records without relying on display text.

            * **Enables:** match `on_hold_task` to on hold task references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-opened-at-ee2d0011d648" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.opened_at`

            Opened At records date/time when the change request was opened, in yyyy-MM-dd HH:mm:ss format. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-opened-by-bb3061fc3c71" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.opened_by`

            Opened By records `Sys_id` of the user who opened the change request. It is needed to refer to the same opened by across records without relying on display text.

            * **Enables:** match `opened_by` to opened by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-order-168dddd7f964" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.order`

            Order records order value for sorting. It is needed to place this Change Request row in the order explicitly reported by ServiceNow.

            * **Enables:** order Change Request rows by the explicit `order` sequence value returned for each Change Request record.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-outside-maintenance-sc-f94f095cb293" title="Outside Maintenance Schedule" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.outside_maintenance_schedule`

            Outside Maintenance Schedule records whether the change is scheduled outside the normal maintenance window. It is needed to distinguish Change Request rows by the exact ServiceNow-returned outside maintenance schedule value.

            * **Enables:** select Change Request rows where `outside_maintenance_schedule` is true or false when comparing the condition described by Outside Maintenance Schedule.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-parent-c09b7efcb0f8" title="Parent" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.parent`

            Parent records `Sys_id` of the parent record. It is needed to refer to the same parent across records without relying on display text.

            * **Enables:** match `parent` to parent references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-phase-a40190cf89e6" title="Phase" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.phase`

            Phase records current phase of the change. Instance-customizable choice; known defaults include: requested, plan, build, test, implement, review, closed. It is needed to distinguish Change Request rows by the exact ServiceNow-returned phase value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `phase` label when comparing phase.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-phase-state-023397e76407" title="Phase State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.phase_state`

            Phase State records state within the current phase. Instance-customizable choice; known defaults include: open, pending, `work_in_progress`, complete, skipped. It is needed to distinguish Change Request rows by the exact ServiceNow-returned phase state value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `phase_state` label when comparing phase state.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-priority-a5a7b78ce2f5" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.priority`

            Priority records priority level of the change request. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Change Request rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-production-system-a481a7503f18" title="Production System" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.production_system`

            Production System records whether the change affects a production system. It is needed to distinguish Change Request rows by the exact ServiceNow-returned production system value.

            * **Enables:** select Change Request rows where `production_system` is true or false when comparing the condition described by Production System.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-reason-99286227dad3" title="Reason" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.reason`

            Reason records reason or justification for the change. It is needed to distinguish Change Request rows by the exact ServiceNow-returned reason value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `reason` label when comparing reason.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-reassignment-count-b7380377bf95" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.reassignment_count`

            Reassignment Count records number of times the change request has been reassigned. It is needed to measure the ServiceNow-reported number of times the change request has been reassigned at one Change Request record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the change request has been reassigned in `reassignment_count` at one Change Request record per row.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is a ServiceNow-reported count at one Change Request record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-requested-by-90e415463bdb" title="Requested By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.requested_by`

            Requested By records `Sys_id` of the user who requested the change. It is needed to refer to the same requested by across records without relying on display text.

            * **Enables:** match `requested_by` to requested by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-requested-by-date-2dbf80ba3878" title="Requested By Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.requested_by_date`

            Requested By Date records date by which the requester needs the change completed. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `requested_by_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-review-comments-7114cfff45ae" title="Review Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.review_comments`

            Review Comments records comments from the post-implementation review. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `review_comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-review-date-633c6d9ee338" title="Review Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.review_date`

            Review Date records date/time for post-implementation review. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `review_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-review-status-9e9932e13cb2" title="Review Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.review_status`

            Review Status records status of the post-implementation review. It is needed to distinguish Change Request rows by the exact ServiceNow-returned review status value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `review_status` label when comparing review status.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-risk-a04120f6cf97" title="Risk" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.risk`

            Risk records risk level associated with the change. Instance-customizable choice; known defaults include: 1, 2, 3, 4. It is needed to distinguish Change Request rows by the exact ServiceNow-returned risk value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `risk` label when comparing risk.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-risk-impact-analysis-4b5bc66e84d5" title="Risk Impact Analysis" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.risk_impact_analysis`

            Risk Impact Analysis records analysis of the risk and impact of the change. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `risk_impact_analysis` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-route-reason-194e7c8799d1" title="Route Reason" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.route_reason`

            Route Reason records reason for routing the change to a particular group. It is needed to distinguish Change Request rows by the exact ServiceNow-returned route reason value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `route_reason` label when comparing route reason.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-scope-0f1abfe507a6" title="Scope" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.scope`

            Scope records scope of the change. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Change Request rows by the exact ServiceNow-returned scope value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `scope` label when comparing scope.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-service-offering-cf2ae3b043f2" title="Service Offering" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.service_offering`

            Service Offering records `Sys_id` of the service offering affected. It is needed to refer to the same service offering across records without relying on display text.

            * **Enables:** match `service_offering` to service offering references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-short-description-82dcac521b34" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.short_description`

            Short Description records brief summary of the change. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is description text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sla-due-bfd15d1d3519" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sla_due`

            Sla Due records date/time the SLA is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-start-date-062661e01910" title="Start Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.start_date`

            Start Date records planned start date/time of the change implementation. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `start_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-state-22f4c4f4a8e6" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.state`

            State records current state of the change request in its lifecycle. Instance-customizable choice; known defaults include: -5, -4, -3, -2, -1, 0, 1, 2, 3, 4. It is needed to distinguish Change Request rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-std-change-producer-ve-4207d6c005da" title="Std Change Producer Version" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.std_change_producer_version`

            Std Change Producer Version records `Sys_id` of the standard change producer version, if this is a standard change. It is needed to refer to the same std change producer version across records without relying on display text.

            * **Enables:** match `std_change_producer_version` to std change producer version references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-subcategory-fd6ab17664e9" title="Subcategory" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.subcategory`

            Subcategory records subcategory providing further classification of the change. It is needed to distinguish Change Request rows by the exact ServiceNow-returned subcategory value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `subcategory` label when comparing subcategory.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-class-name-aa258f470569" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_class_name`

            Sys Class Name records table class name, typically '`change_request`'. It is needed to distinguish Change Request rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-created-by-d7efe90c7d7d" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Change Request row to the returned person, account, or organization reference.

            * **Enables:** attribute the Change Request row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-created-on-4a5dec97a788" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_created_on`

            Sys Created On records date/time the record was created in yyyy-MM-dd HH:mm:ss format. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-domain-a78f105ba44f" title="Sys Domain" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_domain`

            Sys Domain records domain of the record for domain-separated instances. It is needed to compare the returned sys domain for individual Change Request rows and select rows with a specific `sys_domain` value.

            * **Enables:** trace the sys domain relationship returned in `sys_domain` from the Change Request row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-domain-path-8493e66dd221" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_domain_path`

            Sys Domain Path records domain path for the record. It is needed to compare the returned sys domain path for individual Change Request rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Change Request row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-id-f3e53c3fbc66" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_id`

            Sys ID records unique 32-character system identifier (GUID) for the change request record. It is needed to distinguish repeated deliveries of the same Change Request row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Change Request and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-mod-count-3c258b14fe18" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Change Request record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Change Request record per row.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is a ServiceNow-reported count at one Change Request record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-tags-dc6055c93fda" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Change Request rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-updated-by-6c374c034877" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Change Request row to the returned person, account, or organization reference.

            * **Enables:** attribute the Change Request row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-sys-updated-on-fd328c127879" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.sys_updated_on`

            Sys Updated On records date/time the record was last updated in yyyy-MM-dd HH:mm:ss format. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-test-plan-6672efa7869a" title="Test Plan" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.test_plan`

            Test Plan records plan for testing the change after implementation. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `test_plan` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is descriptive text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-type-5c9e328db420" title="Type" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.type`

            Type records type of change request. Instance-customizable choice; known defaults include: normal, standard, emergency. It is needed to distinguish Change Request rows by the exact ServiceNow-returned type value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `type` label when comparing type.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-unauthorized-898e50a74f78" title="Unauthorized" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.unauthorized`

            Unauthorized records whether the change is flagged as unauthorized. It is needed to distinguish Change Request rows by the exact ServiceNow-returned unauthorized value.

            * **Enables:** select Change Request rows where `unauthorized` is true or false when comparing the condition described by Unauthorized.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-upon-approval-9d57215cb783" title="Upon Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.upon_approval`

            Upon Approval records action to take when the change is approved. Instance-customizable choice; known defaults include: proceed, `do_nothing`. It is needed to distinguish Change Request rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-upon-reject-310290be6846" title="Upon Reject" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.upon_reject`

            Upon Reject records action to take when the change is rejected. Instance-customizable choice; known defaults include: cancel, `do_nothing`. It is needed to distinguish Change Request rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-urgency-19dded3b7f7b" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.urgency`

            Urgency records urgency level of the change request. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Change Request rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Change Request rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-user-input-64ca4a2a35be" title="User Input" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.user_input`

            User Input records user input captured during record creation. It is needed to attribute this Change Request row to the returned person, account, or organization reference.

            * **Enables:** attribute the Change Request row to the returned person or account and match the exact `user_input` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-watch-list-e39a8aa71260" title="Watch List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.watch_list`

            Watch List records comma-separated list of `sys_ids` of users watching this change. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `watch_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is a list of ServiceNow user identifiers at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-work-end-afe7252493c8" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.work_end`

            Work End records actual end date/time when work on the change completed. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-work-notes-1282fe89e66d" title="Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.work_notes`

            Work Notes records work notes (journal field, typically write-only via API). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-work-notes-list-35da494f283f" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.work_notes_list`

            Work Notes List records comma-separated list of `sys_ids` of users in the work notes list. It is needed to refer to the same work notes list across records without relying on display text.

            * **Enables:** match `work_notes_list` to work notes list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is comment or journal text at one Change Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-change-request-work-start-906caa2a3b01" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `change_request.work_start`

            Work Start records actual start date/time when work on the change began. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Change Request records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Change Request object returned for Change Request; it is interpreted at one Change Request record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-cmn-department-9c1f66b45cd0" title="Departments" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `cmn_department`

        Departments covers department records from ServiceNow `cmn_department` table, including department name, head, parent department, and company.

        * **Enables:** connect each returned department to its head, parent department, and company.
        * **Scope:** Extracts department records from ServiceNow `cmn_department` table, including department name, head, parent department, and company; the connector reads `/api/now/table/cmn_department` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-cmn-department-business-unit-a1926af9a2ec" title="Business Unit" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.business_unit`

            Business Unit records reference to the business unit record (`sys_id` of `business_unit`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `business_unit` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-company-dbf1648d6e1a" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.company`

            Company records reference to the company record (`sys_id` of `core_company`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `company` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-cost-center-222be8a6fd1f" title="Cost Center" icon="money-check-dollar" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.cost_center`

            Cost Center records reference to the cost center record (`sys_id` of `cmn_cost_center`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `cost_center` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-dept-head-bf703df6b9db" title="Dept Head" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.dept_head`

            Dept Head records reference to the department head user record (`sys_id` of `sys_user`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `dept_head` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-description-c670f57f6085" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.description`

            Description records detailed description of the department. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is description text at one Cmn Department record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-head-count-9648a6a1f183" title="Head Count" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.head_count`

            Head Count records number of members in the department. Returned as a string from the API. It is needed to measure the ServiceNow-reported number of members in the department. Returned as a string from the API at one Cmn Department record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of members in the department. Returned as a string from the API in `head_count` at one Cmn Department record per row.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is a ServiceNow-reported count at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-id-5c3c5412c40f" title="ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.id`

            ID records department ID, a user-defined identifier for the department. It is needed to refer to the same cmn department across records without relying on display text.

            * **Enables:** match `id` to cmn department references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-name-10c4e81129f0" title="Name" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.name`

            Name records display name of the department. It is needed to compare the returned name for individual Departments rows and select rows with a specific `name` value.

            * **Enables:** locate Departments rows whose returned name exactly matches `name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-parent-e370cf4c4855" title="Parent" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.parent`

            Parent records reference to the parent department record (`sys_id` of `cmn_department`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `parent` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-primary-contact-573a43ce8064" title="Primary Contact" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.primary_contact`

            Primary Contact records reference to the primary contact user record (`sys_id` of `sys_user`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `primary_contact` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-class-name-4cb7063c577b" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_class_name`

            Sys Class Name records the table class name for the record, typically '`cmn_department`'. It is needed to distinguish Departments rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Departments rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-created-by-ceef10b087b8" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_created_by`

            Sys Created By records username of the user who created the department record. It is needed to attribute this Departments row to the returned person, account, or organization reference.

            * **Enables:** attribute the Departments row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-created-on-e02f69a38038" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_created_on`

            Sys Created On records timestamp when the department record was created, in format YYYY-MM-DD HH:mm:ss. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Departments records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-domain-89958b18b26e" title="Sys Domain" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_domain`

            Sys Domain records domain identifier for domain-separated instances (`sys_id` of `sys_user_group` or global). It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-domain-path-442fd53e5df8" title="Sys Domain Path" icon="link" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_domain_path`

            Sys Domain Path records domain path for domain-separated instances, represented as a slash-delimited path. It is needed to compare the exact sys domain path configuration returned for this Cmn Department record.

            * **Enables:** compare the exact `sys_domain_path` configuration returned for each Cmn Department record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-id-c31640669aca" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_id`

            Sys ID records unique 32-character system identifier (GUID) for the department record. It is needed to distinguish repeated deliveries of the same Departments row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Departments and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-mod-count-165d79797d37" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Cmn Department record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Cmn Department record per row.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is a ServiceNow-reported count at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-policy-f83aac3248fc" title="Sys Policy" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_policy`

            Sys Policy records read/write policy applied to the record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `sys_policy` access value with the resource, account, or membership represented by the same Departments row.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-scope-7bd94fd5f1bc" title="Sys Scope" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_scope`

            Sys Scope records application scope of the record (`sys_id` of `sys_scope`). It is needed to refer to the same sys scope across records without relying on display text.

            * **Enables:** match `sys_scope` to sys scope references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is an identifier, not a measured quantity; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-tags-4c024eee5b45" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_tags`

            Sys Tags records tags associated with the department record. It is needed to distinguish Departments rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Departments rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-update-name-f886257f29e2" title="Sys Update Name" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_update_name`

            Sys Update Name records update name used for tracking record changes in update sets. It is needed to compare the returned sys update name for individual Departments rows and select rows with a specific `sys_update_name` value.

            * **Enables:** locate Departments rows whose returned sys update name exactly matches `sys_update_name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-updated-by-3df26fc24c7b" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_updated_by`

            Sys Updated By records username of the user who last updated the department record. It is needed to attribute this Departments row to the returned person, account, or organization reference.

            * **Enables:** attribute the Departments row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-department-sys-updated-on-983b965eb461" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_department.sys_updated_on`

            Sys Updated On records timestamp when the department record was last updated, in format YYYY-MM-DD HH:mm:ss. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Departments records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Cmn Department object returned for Departments; it is interpreted at one Cmn Department record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-cmn-location-01f93420f701" title="Locations" icon="map-location-dot" iconType="sharp-duotone-solid">
        Developer identifier: `cmn_location`

        Locations covers location records from ServiceNow `cmn_location` table, including name, address, city, state, country, and coordinates.

        * **Enables:** compare the configured ServiceNow location records and their parent or contact references without treating addresses or coordinates as proof of residency.
        * **Scope:** Extracts location records from ServiceNow `cmn_location` table, including name, address, city, state, country, and coordinates; the connector reads `/api/now/table/cmn_location` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-cmn-location-city-daea4468fd3b" title="City" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.city`

            City records city where the location resides. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `city` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-cmn-location-source-e2d72d0fe52b" title="Cmn Location Source" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.cmn_location_source`

            Cmn Location Source records source from which the location record was created or imported. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `cmn_location_source` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-cmn-location-type-a8b66e0af4a8" title="Cmn Location Type" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.cmn_location_type`

            Cmn Location Type records location type classification reference. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `cmn_location_type` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-company-43993c8db280" title="Company" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.company`

            Company records reference to the associated company record (`sys_id`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `company` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-contact-ca3dbf942303" title="Contact" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.contact`

            Contact records reference to the contact user record (`sys_id`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `contact` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-coordinates-retrieved-on-49cec58facd8" title="Coordinates Retrieved On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.coordinates_retrieved_on`

            Coordinates Retrieved On records timestamp when the geographic coordinates were last retrieved. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Locations records by `coordinates_retrieved_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; its unit or granularity is provider-reported geographic coordinates; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-country-a23e775a4b70" title="Country" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.country`

            Country records country of the location. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `country` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-duplicate-01619c4339e2" title="Duplicate" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.duplicate`

            Duplicate indicates whether this location is a duplicate. It is needed to distinguish Locations rows by the exact ServiceNow-returned duplicate value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `duplicate` label when comparing duplicate.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-fax-phone-1d3ea4e05bc9" title="Fax Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.fax_phone`

            Fax Phone records fax phone number for the location. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `fax_phone` to the same Cmn Location record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-full-name-5a4a1d735238" title="Full Name" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.full_name`

            Full Name records full hierarchical name of the location including parent locations. It is needed to compare the returned full name for individual Locations rows and select rows with a specific `full_name` value.

            * **Enables:** locate Locations rows whose returned full name exactly matches `full_name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-latitude-2708e689807a" title="Latitude" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.latitude`

            Latitude records latitude coordinate of the location. It is needed to preserve the ServiceNow-reported geographic coordinate context for the same record.

            * **Enables:** compare the ServiceNow-reported geographic coordinate context in `latitude` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; its unit or granularity is provider-reported geographic coordinates; the value is geographic coordinate context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-life-cycle-stage-1d65e75b0df1" title="Life Cycle Stage" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.life_cycle_stage`

            Life Cycle Stage records life cycle stage of the location. It is needed to distinguish Locations rows by the exact ServiceNow-returned life cycle stage value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `life_cycle_stage` label when comparing life cycle stage.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-life-cycle-stage-status-a89076e6cac5" title="Life Cycle Stage Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.life_cycle_stage_status`

            Life Cycle Stage Status records status within the current life cycle stage. It is needed to distinguish Locations rows by the exact ServiceNow-returned life cycle stage status value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `life_cycle_stage_status` label when comparing life cycle stage status.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-longitude-ece45f829940" title="Longitude" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.longitude`

            Longitude records longitude coordinate of the location. It is needed to preserve the ServiceNow-reported geographic coordinate context for the same record.

            * **Enables:** compare the ServiceNow-reported geographic coordinate context in `longitude` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; its unit or granularity is provider-reported geographic coordinates; the value is geographic coordinate context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-managed-by-group-559bef054321" title="Managed By Group" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.managed_by_group`

            Managed By Group records reference to the group that manages this location (`sys_id`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `managed_by_group` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-name-4af33990f145" title="Name" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.name`

            Name records name of the location. It is needed to compare the returned name for individual Locations rows and select rows with a specific `name` value.

            * **Enables:** locate Locations rows whose returned name exactly matches `name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-parent-0d73923927b5" title="Parent" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.parent`

            Parent records reference to the parent location record (`sys_id`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `parent` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-phone-0856a6627912" title="Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.phone`

            Phone records phone number for the location. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `phone` to the same Cmn Location record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-phone-territory-4c37f65a0d05" title="Phone Territory" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.phone_territory`

            Phone Territory records phone territory associated with the location phone number. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `phone_territory` to the same Cmn Location record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-state-2bef8200373b" title="State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.state`

            State records state or province of the location. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `state` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-stock-room-af3730187121" title="Stock Room" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.stock_room`

            Stock Room indicates whether the location is a stock room (boolean stored as string). It is needed to distinguish Locations rows by the exact ServiceNow-returned stock room value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `stock_room` label when comparing stock room.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-street-322a14032b96" title="Street" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.street`

            Street records street address of the location. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `street` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-class-name-7f05837f7c5a" title="Sys Class Name" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_class_name`

            Sys Class Name records the table class name for the record (e.g., `cmn_location`). It is needed to distinguish Locations rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-created-by-f717b3616d22" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Locations row to the returned person, account, or organization reference.

            * **Enables:** attribute the Locations row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-created-on-a202476364af" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_created_on`

            Sys Created On records timestamp when the location record was created in ServiceNow. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Locations records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-domain-ccde9d96289d" title="Sys Domain" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_domain`

            Sys Domain records domain to which this record belongs (`sys_id`), used in domain-separated instances. It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-domain-path-4580eaac881e" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_domain_path`

            Sys Domain Path records domain path for the record in domain-separated instances. It is needed to compare the returned sys domain path for individual Locations rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Cmn Location row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-id-002283cc0012" title="Sys ID" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_id`

            Sys ID records unique system identifier for the location record. It is needed to distinguish repeated deliveries of the same Locations row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Locations and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-mod-count-9f4d36f8cb71" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Cmn Location record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Cmn Location record per row.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is a ServiceNow-reported count at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-tags-68c5d47e8b5d" title="Sys Tags" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_tags`

            Sys Tags records tags associated with the location record. It is needed to distinguish Locations rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-updated-by-78e29bcf9c56" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Locations row to the returned person, account, or organization reference.

            * **Enables:** attribute the Locations row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-sys-updated-on-a4e814f34404" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.sys_updated_on`

            Sys Updated On records timestamp when the location record was last updated in ServiceNow. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Locations records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-time-zone-d0fdcb4ee3d3" title="Time Zone" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.time_zone`

            Time Zone records time zone of the location (e.g., US/Eastern, Europe/London). It is needed to preserve the ServiceNow-reported timezone or locale setting for the same record.

            * **Enables:** compare the ServiceNow-reported timezone or locale setting in `time_zone` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the schema uses the `Temporal.TimeZone` scalar; the value is timezone or locale setting; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-type-a5777d94881a" title="Type" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.type`

            Type records type classification of the location. It is needed to distinguish Locations rows by the exact ServiceNow-returned type value.

            * **Enables:** separate Locations rows by the exact ServiceNow-returned `type` label when comparing type.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-cmn-location-zip-b7cdba0d7061" title="Zip" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `cmn_location.zip`

            Zip records postal or ZIP code of the location. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `zip` for individual Locations rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Cmn Location object returned for Locations; it is interpreted at one Cmn Location record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-core-company-649212270573" title="Companies" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `core_company`

        Companies covers company records from ServiceNow `core_company` table, including company name, contact info, and parent company.

        * **Enables:** connect each returned company record to its parent company and returned contact references.
        * **Scope:** Extracts company records from ServiceNow `core_company` table, including company name, contact info, and parent company; the connector reads `/api/now/table/core_company` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-core-company-apple-icon-a2cd90561beb" title="Apple Icon" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.apple_icon`

            Apple Icon records apple touch icon for the company. It is needed to compare the returned apple icon for individual Companies rows and select rows with a specific `apple_icon` value.

            * **Enables:** trace the apple icon relationship returned in `apple_icon` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-banner-image-68b1a83d0be6" title="Banner Image" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.banner_image`

            Banner Image records banner image attachment `sys_id` for the company. It is needed to refer to the same banner image across records without relying on display text.

            * **Enables:** match `banner_image` to banner image references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-banner-image-light-29a270e99973" title="Banner Image Light" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.banner_image_light`

            Banner Image Light records light-themed banner image attachment `sys_id`. It is needed to refer to the same banner image light across records without relying on display text.

            * **Enables:** match `banner_image_light` to banner image light references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-banner-text-2b35b451b797" title="Banner Text" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.banner_text`

            Banner Text records text displayed on the company banner. It is needed to compare the returned banner text for individual Companies rows and select rows with a specific `banner_text` value.

            * **Enables:** trace the banner text relationship returned in `banner_text` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-city-357cff9884a8" title="City" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.city`

            City records city where the company is located. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `city` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-contact-1c1c7ebe1eb6" title="Contact" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.contact`

            Contact records reference (`sys_id`) to the primary contact user record. It is needed to refer to the same contact across records without relying on display text.

            * **Enables:** match `contact` to contact references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-country-349c5ed17d2c" title="Country" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.country`

            Country records country where the company is located. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `country` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-customer-8d0885074d44" title="Customer" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.customer`

            Customer indicates whether this company is a customer. It is needed to distinguish Companies rows by the exact ServiceNow-returned customer value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `customer` label when comparing customer.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-discount-a9f05b4b9a79" title="Discount" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.discount`

            Discount records discount percentage associated with the company. It is needed to compare the returned discount for individual Companies rows and select rows with a specific `discount` value.

            * **Enables:** trace the discount relationship returned in `discount` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; its unit or granularity is percent.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-email-address-3f2d40ff228f" title="Email Address" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.email_address`

            Email Address records primary email address for the company. It is needed to attribute this Companies row to the returned person, account, or organization reference.

            * **Enables:** attribute the Companies row to the returned person or account and match the exact `email_address` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-fax-phone-1614038bab1d" title="Fax Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.fax_phone`

            Fax Phone records fax phone number for the company. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `fax_phone` to the same Core Company record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-fiscal-year-4b26833cd73b" title="Fiscal Year" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.fiscal_year`

            Fiscal Year records fiscal year end month or date for the company. It is needed to compare the returned fiscal year for individual Companies rows and select rows with a specific `fiscal_year` value.

            * **Enables:** trace the fiscal year relationship returned in `fiscal_year` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-latitude-ec494339f59b" title="Latitude" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.latitude`

            Latitude records geographic latitude coordinate of the company location. It is needed to preserve the ServiceNow-reported geographic coordinate context for the same record.

            * **Enables:** compare the ServiceNow-reported geographic coordinate context in `latitude` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; its unit or granularity is provider-reported geographic coordinates; the value is geographic coordinate context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-longitude-8c43987a538d" title="Longitude" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.longitude`

            Longitude records geographic longitude coordinate of the company location. It is needed to preserve the ServiceNow-reported geographic coordinate context for the same record.

            * **Enables:** compare the ServiceNow-reported geographic coordinate context in `longitude` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; its unit or granularity is provider-reported geographic coordinates; the value is geographic coordinate context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-manufacturer-0aff2e111022" title="Manufacturer" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.manufacturer`

            Manufacturer indicates whether this company is a manufacturer. It is needed to distinguish Companies rows by the exact ServiceNow-returned manufacturer value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `manufacturer` label when comparing manufacturer.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-market-cap-540315765385" title="Market Cap" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.market_cap`

            Market Cap records market capitalization of the company. It is needed to compare the returned market cap for individual Companies rows and select rows with a specific `market_cap` value.

            * **Enables:** trace the market cap relationship returned in `market_cap` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-name-7e9b714d90b1" title="Name" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.name`

            Name records company name. It is needed to compare the returned name for individual Companies rows and select rows with a specific `name` value.

            * **Enables:** locate Companies rows whose returned name exactly matches `name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-notes-3804facbdb84" title="Notes" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.notes`

            Notes records free-text notes or description about the company. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `notes` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is comment or journal text at one Core Company record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-num-employees-e62128196056" title="Num Employees" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.num_employees`

            Num Employees records number of employees at the company. It is needed to measure the ServiceNow-reported number of employees at the company at one Core Company record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of employees at the company in `num_employees` at one Core Company record per row.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is a ServiceNow-reported count at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-parent-06ec459bf9d9" title="Parent" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.parent`

            Parent records reference (`sys_id`) to the parent company record. It is needed to refer to the same parent across records without relying on display text.

            * **Enables:** match `parent` to parent references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-phone-4867ef105ce5" title="Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.phone`

            Phone records primary phone number for the company. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `phone` to the same Core Company record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-primary-9216ba1594a2" title="Primary" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.primary`

            Primary indicates whether this is a primary company record. It is needed to distinguish Companies rows by the exact ServiceNow-returned primary value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `primary` label when comparing primary.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-profits-4a24e5a83abb" title="Profits" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.profits`

            Profits records profit amount for the company. It is needed to measure the exact commercial amount reported on this record.

            * **Enables:** measure and compare the reported `profits` amount for Companies records, using the record's currency code when one is returned.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the ServiceNow response determines the currency or pricing basis; do not infer one when it is absent.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-publicly-traded-f40b5236c493" title="Publicly Traded" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.publicly_traded`

            Publicly Traded records whether the company is publicly traded. It is needed to distinguish Companies rows by the exact ServiceNow-returned publicly traded value.

            * **Enables:** select Companies rows where `publicly_traded` is true or false when comparing the condition described by Publicly Traded.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-rank-tier-df349bbd4eff" title="Rank Tier" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.rank_tier`

            Rank Tier records rank or tier classification of the company. It is needed to compare the exact rank tier configuration returned for this Core Company record.

            * **Enables:** compare the exact `rank_tier` configuration returned for each Core Company record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-revenue-per-year-e9b9b4aa9f71" title="Revenue Per Year" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.revenue_per_year`

            Revenue Per Year records annual revenue of the company. It is needed to measure the exact commercial amount reported on this record.

            * **Enables:** measure and compare the reported `revenue_per_year` amount for Companies records, using the record's currency code when one is returned.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the ServiceNow response determines the currency or pricing basis; do not infer one when it is absent.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-state-0aa8ea3606d4" title="State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.state`

            State records state or province where the company is located. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `state` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-stock-symbol-1d133f6c1266" title="Stock Symbol" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.stock_symbol`

            Stock Symbol records stock ticker symbol for the company. It is needed to compare the returned stock symbol for individual Companies rows and select rows with a specific `stock_symbol` value.

            * **Enables:** trace the stock symbol relationship returned in `stock_symbol` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-street-5d702911e488" title="Street" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.street`

            Street records street address of the company. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `street` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-class-name-0c522b2e7ec7" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_class_name`

            Sys Class Name records the table class name for this record (e.g., `core_company`). It is needed to distinguish Companies rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-class-path-56d17bb720ea" title="Sys Class Path" icon="link" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_class_path`

            Sys Class Path records hierarchical class path for the record's table. It is needed to distinguish Companies rows by the exact ServiceNow-returned sys class path value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `sys_class_path` label when comparing sys class path.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-created-by-bbc3323395d7" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Companies row to the returned person, account, or organization reference.

            * **Enables:** attribute the Companies row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-created-on-c92d344ca4ef" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_created_on`

            Sys Created On records timestamp (UTC) when the record was created. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Companies records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-domain-9d4dbbeee604" title="Sys Domain" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_domain`

            Sys Domain records domain `sys_id` to which this record belongs (domain separation). It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-domain-path-0e79997775c3" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_domain_path`

            Sys Domain Path records domain path for domain-separated instances. It is needed to compare the returned sys domain path for individual Companies rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-id-fb7982dfb9d4" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_id`

            Sys ID records unique system identifier (GUID) for the company record. It is needed to distinguish repeated deliveries of the same Companies row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Companies and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-mod-count-14ee68121668" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Core Company record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Core Company record per row.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is a ServiceNow-reported count at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-tags-44bba5267e76" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_tags`

            Sys Tags records comma-separated tags associated with the record. It is needed to distinguish Companies rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-updated-by-8da776f9f492" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Companies row to the returned person, account, or organization reference.

            * **Enables:** attribute the Companies row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-sys-updated-on-2f13a0b124b6" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.sys_updated_on`

            Sys Updated On records timestamp (UTC) when the record was last updated. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Companies records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-theme-d3b37a8cdf66" title="Theme" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.theme`

            Theme records reference (`sys_id`) to the UI theme associated with the company. It is needed to refer to the same theme across records without relying on display text.

            * **Enables:** match `theme` to theme references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-vendor-a42dc62e1d8e" title="Vendor" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.vendor`

            Vendor indicates whether this company is a vendor. It is needed to distinguish Companies rows by the exact ServiceNow-returned vendor value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `vendor` label when comparing vendor.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-vendor-manager-8f5e686f67c3" title="Vendor Manager" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.vendor_manager`

            Vendor Manager records reference (`sys_id`) to the vendor manager user record. It is needed to refer to the same vendor manager across records without relying on display text.

            * **Enables:** match `vendor_manager` to vendor manager references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-vendor-type-7767a07cbbdd" title="Vendor Type" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.vendor_type`

            Vendor Type records type classification for vendor companies. It is needed to distinguish Companies rows by the exact ServiceNow-returned vendor type value.

            * **Enables:** separate Companies rows by the exact ServiceNow-returned `vendor_type` label when comparing vendor type.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-website-088bad547ba9" title="Website" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.website`

            Website records company website URL. It is needed to compare the returned website for individual Companies rows and select rows with a specific `website` value.

            * **Enables:** trace the website relationship returned in `website` from the Core Company row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the schema uses the `Network.Url` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-core-company-zip-ba9bc6f06212" title="Zip" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `core_company.zip`

            Zip records postal or ZIP code. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `zip` for individual Companies rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Core Company object returned for Companies; it is interpreted at one Core Company record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-incident-3cbf153bc2f0" title="Incident" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `incident`

        Incident covers incident records from ServiceNow. Incidents represent reported issues or service disruptions that need resolution. Core ITSM table.

        * **Enables:** follow service work from the reported record through its returned assignee, status, priority, and timestamps during triage or fulfillment.
        * **Scope:** Extracts incident records from ServiceNow. Incidents represent reported issues or service disruptions that need resolution. Core ITSM table; the connector reads `/api/now/table/incident` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-incident-active-d6ba5203ea55" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.active`

            Active records whether the incident is currently active (true) or inactive (false). It is needed to distinguish Incident rows by the exact ServiceNow-returned active value.

            * **Enables:** select Incident rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-additional-assignee-list-4ba9836c6db3" title="Additional Assignee List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.additional_assignee_list`

            Additional Assignee List records comma-separated list of additional assignee `sys_ids`. It is needed to refer to the same additional assignee list across records without relying on display text.

            * **Enables:** match `additional_assignee_list` to additional assignee list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-approval-7deda736e53c" title="Approval" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.approval`

            Approval records approval status of the incident. It is needed to distinguish Incident rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-assigned-to-67e751a3da9b" title="Assigned To" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.assigned_to`

            Assigned To records `Sys_id` of the individual assigned to resolve the incident (reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `assigned_to` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-assignment-group-04a4d74c62c9" title="Assignment Group" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.assignment_group`

            Assignment Group records `Sys_id` of the group assigned to resolve the incident (reference to `sys_user_group`). It is needed to refer to the same `sys_user_group` across records without relying on display text.

            * **Enables:** match `assignment_group` to `sys_user_group` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-business-duration-80d0d2635591" title="Business Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.business_duration`

            Business Duration records duration of the incident in business hours (ServiceNow duration format). It is needed to measure the exact duration reported for one Incident record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_duration` per Incident record in hours.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; its unit or granularity is hours.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-business-service-8c402dcb704e" title="Business Service" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.business_service`

            Business Service records `Sys_id` of the business service affected (reference to `cmdb_ci_service`). It is needed to refer to the same `cmdb_ci_service` across records without relying on display text.

            * **Enables:** match `business_service` to `cmdb_ci_service` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-calendar-duration-3f1d8d3afc48" title="Calendar Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.calendar_duration`

            Calendar Duration records duration of the incident in calendar time (ServiceNow duration format). It is needed to measure the exact duration reported for one Incident record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_duration` per Incident record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-caller-id-530e1654d581" title="Caller ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.caller_id`

            Caller ID records `Sys_id` of the user who reported the incident (reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `caller_id` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-category-d5f0ef8803f2" title="Category" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.category`

            Category records category classification of the incident (e.g., Inquiry, Software, Hardware, Network). It is needed to distinguish Incident rows by the exact ServiceNow-returned category value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `category` label when comparing category.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-caused-by-983aff0c4945" title="Caused By" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.caused_by`

            Caused By records `Sys_id` of the change request that caused this incident. It is needed to refer to the same caused by across records without relying on display text.

            * **Enables:** match `caused_by` to caused by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-child-incidents-e1cbbac4acb4" title="Child Incidents" icon="link" iconType="sharp-duotone-solid">
            Developer identifier: `incident.child_incidents`

            Child Incidents records number of child incidents linked to this incident. It is needed to measure the ServiceNow-reported number of child incidents linked to this incident at one Incident record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of child incidents linked to this incident in `child_incidents` at one Incident record per row.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is a ServiceNow-reported count at one Incident record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-close-code-1a5e5ead3391" title="Close Code" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.close_code`

            Close Code records resolution code selected when closing the incident. It is needed to distinguish Incident rows by the exact ServiceNow-returned close code value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `close_code` label when comparing close code.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-close-notes-006ea2244318" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident.close_notes`

            Close Notes records notes entered when closing the incident describing the resolution. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is comment or journal text at one Incident record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-closed-at-d4fbc27c7454" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.closed_at`

            Closed At records date/time the incident was closed. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-closed-by-dc3ab5bff7c2" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.closed_by`

            Closed By records `Sys_id` of the user who closed the incident (reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `closed_by` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-cmdb-ci-875f78fbf235" title="Cmdb Ci" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.cmdb_ci`

            Cmdb Ci records `Sys_id` of the configuration item affected by the incident (reference to `cmdb_ci`). It is needed to refer to the same `cmdb_ci` across records without relying on display text.

            * **Enables:** match `cmdb_ci` to `cmdb_ci` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-comments-1c74bcef77d4" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident.comments`

            Comments records customer-visible comments (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is comment or journal text at one Incident record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-comments-and-work-notes-5422c45ac5cc" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is comment or journal text at one Incident record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-company-1d481f33babc" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.company`

            Company records `Sys_id` of the company associated with the incident (reference to `core_company`). It is needed to refer to the same `core_company` across records without relying on display text.

            * **Enables:** match `company` to `core_company` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-contact-type-7a129017539a" title="Contact Type" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.contact_type`

            Contact Type records how the incident was reported (e.g., phone, email, self-service). Instance-customizable choice; known defaults include: phone, email, self-service, walk-in, `virtual_agent`, chat. It is needed to distinguish Incident rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-correlation-display-f2fdb8f70172" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.correlation_display`

            Correlation Display records display value for the correlation identifier. It is needed to refer to the same correlation display across records without relying on display text.

            * **Enables:** match `correlation_display` to correlation display references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-correlation-id-593c6677d812" title="Correlation ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.correlation_id`

            Correlation ID records correlation identifier used for event management integration. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-department-0068dfebdd33" title="Department" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.department`

            Department records `Sys_id` of the department associated with the incident (reference to `cmn_department`). It is needed to refer to the same `cmn_department` across records without relying on display text.

            * **Enables:** match `department` to `cmn_department` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-description-19bd06a6b1ff" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.description`

            Description records detailed description of the incident. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is description text at one Incident record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-due-date-de0814161528" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.due_date`

            Due Date records date/time by which the incident should be resolved. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-escalation-f1268f4daa4a" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.escalation`

            Escalation records escalation level of the incident. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Incident rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-expected-start-ddd2aba93995" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.expected_start`

            Expected Start records expected start date/time for work on the incident. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-follow-up-e57f6194e1bd" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.follow_up`

            Follow Up records date/time for follow-up on the incident. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-group-list-767bc68e12f4" title="Group List" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.group_list`

            Group List records comma-separated list of group `sys_ids` associated with the incident. It is needed to preserve the explicit ServiceNow group references attached to this row.

            * **Enables:** split the references in `group_list` and match each returned group identifier to the corresponding ServiceNow group record when available.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is a list of ServiceNow group identifiers at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-hold-reason-78ab6b377705" title="Hold Reason" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.hold_reason`

            Hold Reason records reason the incident is on hold, if applicable. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Incident rows by the exact ServiceNow-returned hold reason value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `hold_reason` label when comparing hold reason.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-impact-ba63c7690f1a" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.impact`

            Impact records impact level indicating the breadth of effect on the business. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Incident rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-incident-state-457fccb7b083" title="Incident State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.incident_state`

            Incident State records incident-specific state value, mirrors state for incident table. Instance-customizable choice; known defaults include: 1, 2, 3, 6, 7, 8. It is needed to distinguish Incident rows by the exact ServiceNow-returned incident state value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `incident_state` label when comparing incident state.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-knowledge-2be73897a50b" title="Knowledge" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.knowledge`

            Knowledge records whether a knowledge article was used or is associated with this incident. It is needed to distinguish Incident rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Incident rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-location-aedc44ac4c7b" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `incident.location`

            Location records `Sys_id` of the location associated with the incident (reference to `cmn_location`). It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Incident row.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-made-sla-c61b14d1cacb" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.made_sla`

            Made Sla records whether the incident met its SLA target. It is needed to distinguish Incident rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Incident rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-notify-fc61757e1e1b" title="Notify" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.notify`

            Notify records notification setting for the incident. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to compare the exact notify configuration returned for this Incident record.

            * **Enables:** compare the exact `notify` configuration returned for each Incident record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-number-ae073ffa52f6" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.number`

            Number records human-readable incident number, e.g. INC0001234. It is needed to refer to the same incident across records without relying on display text.

            * **Enables:** match `number` to incident references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-opened-at-ada16cec32e2" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.opened_at`

            Opened At records date/time the incident was opened, in ServiceNow format (yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-opened-by-954490562a2c" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.opened_by`

            Opened By records `Sys_id` of the user who opened the incident (reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `opened_by` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-order-6ec91548bcf6" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.order`

            Order records ordering value for the incident. It is needed to place this Incident row in the order explicitly reported by ServiceNow.

            * **Enables:** order Incident rows by the explicit `order` sequence value returned for each Incident record.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-origin-id-c4c2daad5dad" title="Origin ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.origin_id`

            Origin ID records `Sys_id` of the originating record if created from another record. It is needed to refer to the same origin across records without relying on display text.

            * **Enables:** match `origin_id` to origin references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-origin-table-58fac0c679e6" title="Origin Table" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `incident.origin_table`

            Origin Table records table name of the originating record. It is needed to compare the returned origin table for individual Incident rows and select rows with a specific `origin_table` value.

            * **Enables:** trace the origin table relationship returned in `origin_table` from the Incident row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-parent-incident-04c456cd33be" title="Parent Incident" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.parent_incident`

            Parent Incident records `Sys_id` of the parent incident if this is a child incident. It is needed to refer to the same parent incident across records without relying on display text.

            * **Enables:** match `parent_incident` to parent incident references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-priority-9c4be882cbd9" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.priority`

            Priority records calculated priority level derived from impact and urgency. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Incident rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-problem-id-b697c53fb757" title="Problem ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.problem_id`

            Problem ID records `Sys_id` of the associated problem record (reference to problem). It is needed to refer to the same `problem` across records without relying on display text.

            * **Enables:** match `problem_id` to `problem` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-reassignment-count-7140cb5ddba2" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.reassignment_count`

            Reassignment Count records number of times the incident has been reassigned. It is needed to measure the ServiceNow-reported number of times the incident has been reassigned at one Incident record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the incident has been reassigned in `reassignment_count` at one Incident record per row.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is a ServiceNow-reported count at one Incident record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-reopen-count-cbe924ca0d69" title="Reopen Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.reopen_count`

            Reopen Count records number of times the incident has been reopened. It is needed to measure the ServiceNow-reported number of times the incident has been reopened at one Incident record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the incident has been reopened in `reopen_count` at one Incident record per row.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is a ServiceNow-reported count at one Incident record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-resolved-at-6d90ba5785a9" title="Resolved At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.resolved_at`

            Resolved At records date/time the incident was resolved. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `resolved_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-resolved-by-5bab8413ea1a" title="Resolved By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.resolved_by`

            Resolved By records `Sys_id` of the user who resolved the incident (reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `resolved_by` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-rfc-fda7d7d5e148" title="Rfc" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.rfc`

            Rfc records `Sys_id` of the associated change request (reference to `change_request`). It is needed to refer to the same `change_request` across records without relying on display text.

            * **Enables:** match `rfc` to `change_request` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-route-reason-6e33b76b1f4e" title="Route Reason" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.route_reason`

            Route Reason records reason code for routing the incident. It is needed to distinguish Incident rows by the exact ServiceNow-returned route reason value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `route_reason` label when comparing route reason.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Generic.Int64` scalar; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-service-offering-ed3cc76fbbd9" title="Service Offering" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.service_offering`

            Service Offering records `Sys_id` of the service offering related to the incident. It is needed to refer to the same service offering across records without relying on display text.

            * **Enables:** match `service_offering` to service offering references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-severity-1e861c22e592" title="Severity" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.severity`

            Severity records severity level of the incident. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Incident rows by the exact ServiceNow-returned severity value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `severity` label when comparing severity.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-short-description-f99b4947b456" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.short_description`

            Short Description records brief summary of the incident. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is description text at one Incident record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sla-due-e4bda8c2e7a7" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sla_due`

            Sla Due records SLA due date/time for the incident. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-state-c233d218fe17" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.state`

            State records current state of the incident lifecycle. Instance-customizable choice; known defaults include: 1, 2, 3, 6, 7, 8. It is needed to distinguish Incident rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-subcategory-2cefef97f4f2" title="Subcategory" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.subcategory`

            Subcategory records subcategory classification providing further detail within the category. It is needed to distinguish Incident rows by the exact ServiceNow-returned subcategory value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `subcategory` label when comparing subcategory.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-class-name-a0a5d52c8111" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_class_name`

            Sys Class Name records table class name, typically 'incident'. It is needed to distinguish Incident rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-created-by-823d3d872593" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Incident row to the returned person, account, or organization reference.

            * **Enables:** attribute the Incident row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-created-on-e2a509dfd8a5" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_created_on`

            Sys Created On records date/time the record was created in ServiceNow. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-domain-d9371fe5a499" title="Sys Domain" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_domain`

            Sys Domain records `Sys_id` of the domain to which the record belongs (for domain-separated instances). It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-domain-path-3dcfe28b0a2c" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_domain_path`

            Sys Domain Path records domain path for the record. It is needed to compare the returned sys domain path for individual Incident rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Incident row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-id-8f4b269130f8" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_id`

            Sys ID records unique 32-character system identifier (GUID) for the incident record. It is needed to distinguish repeated deliveries of the same Incident row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Incident and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-mod-count-8684e4cbf1f3" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Incident record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Incident record per row.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is a ServiceNow-reported count at one Incident record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-tags-1cd245edc8a6" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Incident rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-updated-by-04633243d953" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Incident row to the returned person, account, or organization reference.

            * **Enables:** attribute the Incident row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-sys-updated-on-e81c7acd1186" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.sys_updated_on`

            Sys Updated On records date/time the record was last updated in ServiceNow. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-effective-number-e1af948d0ceb" title="Task Effective Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.task_effective_number`

            Task Effective Number records effective task number for the incident. It is needed to refer to the same task effective number across records without relying on display text.

            * **Enables:** match `task_effective_number` to task effective number references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-time-worked-fcfb0f503414" title="Time Worked" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident.time_worked`

            Time Worked records total time worked on the incident (ServiceNow duration format). It is needed to measure the exact duration reported for one Incident record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `time_worked` per Incident record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-universal-request-40d1cd1dc871" title="Universal Request" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident.universal_request`

            Universal Request records `Sys_id` of the associated universal request record. It is needed to refer to the same universal request across records without relying on display text.

            * **Enables:** match `universal_request` to universal request references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-upon-approval-495b1dd33286" title="Upon Approval" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.upon_approval`

            Upon Approval records action to take when the incident is approved. It is needed to distinguish Incident rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-upon-reject-072a676ac8c2" title="Upon Reject" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident.upon_reject`

            Upon Reject records action to take if the incident approval is rejected. It is needed to distinguish Incident rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-urgency-bacaa385d5c9" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.urgency`

            Urgency records urgency level indicating how quickly the incident needs resolution. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Incident rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Incident rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-watch-list-6e625aac4ba0" title="Watch List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident.watch_list`

            Watch List records comma-separated list of `sys_ids` of users watching the incident. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `watch_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is a list of ServiceNow user identifiers at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-work-end-7a24686339c1" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.work_end`

            Work End records actual end date/time when work was completed on the incident. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-work-notes-6fb891bb7d28" title="Work Notes" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident.work_notes`

            Work Notes records internal work notes (journal field, may return last entry or empty depending on configuration). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is comment or journal text at one Incident record per row; availability and any truncation follow the limitation stated in the field description.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-work-notes-list-d26c74714843" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident.work_notes_list`

            Work Notes List records comma-separated list of `sys_ids` of work note journal entries. It is needed to refer to the same work notes list across records without relying on display text.

            * **Enables:** match `work_notes_list` to work notes list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is comment or journal text at one Incident record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-work-start-f1708ad4189d" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident.work_start`

            Work Start records actual start date/time when work began on the incident. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident object returned for Incident; it is interpreted at one Incident record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-incident-task-05b2f71067f5" title="Incident Task" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `incident_task`

        Incident Task covers incident tasks from ServiceNow. Incident tasks are work items created to track and resolve an incident.

        * **Enables:** follow service work from the reported record through its returned assignee, status, priority, and timestamps during triage or fulfillment.
        * **Scope:** Extracts incident tasks from ServiceNow. Incident tasks are work items created to track and resolve an incident; the connector reads `/api/now/table/incident_task` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-incident-task-active-9f6fa855394d" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.active`

            Active records whether the incident task is currently active. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned active value.

            * **Enables:** select Incident Task rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-activity-due-2a7a6398fd73" title="Activity Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.activity_due`

            Activity Due records date/time when the next SLA activity is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `activity_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-additional-assignee-lis-bd8ccb3eaa0b" title="Additional Assignee List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.additional_assignee_list`

            Additional Assignee List records comma-separated list of additional assignee user `sys_ids`. It is needed to refer to the same additional assignee list across records without relying on display text.

            * **Enables:** match `additional_assignee_list` to additional assignee list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-approval-b5021f334a0b" title="Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.approval`

            Approval records approval status of the incident task. Instance-customizable choice; known defaults include: not requested, requested, approved, rejected, cancelled. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-approval-history-9958164a7434" title="Approval History" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.approval_history`

            Approval History records history of approval actions on this task. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned approval history value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `approval_history` label when comparing approval history.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-approval-set-be6daa4a00fc" title="Approval Set" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.approval_set`

            Approval Set records date/time when the approval status was last set. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `approval_set`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-assigned-to-817f8379f74f" title="Assigned To" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.assigned_to`

            Assigned To records reference (`sys_id`) to the user assigned to this task. It is needed to refer to the same assigned to across records without relying on display text.

            * **Enables:** match `assigned_to` to assigned to references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-assignment-group-9ac93f3d2f9c" title="Assignment Group" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.assignment_group`

            Assignment Group records reference (`sys_id`) to the group assigned to this task. It is needed to refer to the same assignment group across records without relying on display text.

            * **Enables:** match `assignment_group` to assignment group references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-business-duration-d75ff3bfb474" title="Business Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.business_duration`

            Business Duration records elapsed business time for the task (duration field). It is needed to measure the exact duration reported for one Incident Task record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_duration` per Incident Task record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-business-service-606648b2b9fb" title="Business Service" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.business_service`

            Business Service records reference (`sys_id`) to the business service related to this task. It is needed to refer to the same business service across records without relying on display text.

            * **Enables:** match `business_service` to business service references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-calendar-duration-a1de43d2cc9c" title="Calendar Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.calendar_duration`

            Calendar Duration records elapsed calendar time for the task (duration field). It is needed to measure the exact duration reported for one Incident Task record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_duration` per Incident Task record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-close-notes-15a1ce0b7027" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.close_notes`

            Close Notes records notes entered when the task was closed. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is comment or journal text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-closed-at-dafdf0a9b760" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.closed_at`

            Closed At records date/time when the task was closed (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-closed-by-a51b02864c5a" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.closed_by`

            Closed By records reference (`sys_id`) to the user who closed this task. It is needed to refer to the same closed by across records without relying on display text.

            * **Enables:** match `closed_by` to closed by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-cmdb-ci-60c50dddb8d3" title="Cmdb Ci" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.cmdb_ci`

            Cmdb Ci records reference (`sys_id`) to the configuration item related to this task. It is needed to refer to the same cmdb ci across records without relying on display text.

            * **Enables:** match `cmdb_ci` to cmdb ci references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-comments-54f1d955788b" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.comments`

            Comments records additional comments on the task (customer-visible journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is comment or journal text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-comments-and-work-notes-6ba0c634cbe5" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is comment or journal text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-company-e21c86dd46c2" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.company`

            Company records reference (`sys_id`) to the company associated with this task. It is needed to refer to the same company across records without relying on display text.

            * **Enables:** match `company` to company references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-contact-type-68ce9b2a8e3c" title="Contact Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.contact_type`

            Contact Type records how the task was initiated (e.g., phone, email, self-service). It is needed to distinguish Incident Task rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-correlation-display-17366482bc97" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.correlation_display`

            Correlation Display records display value for the correlation identifier. It is needed to refer to the same correlation display across records without relying on display text.

            * **Enables:** match `correlation_display` to correlation display references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-correlation-id-ca08bda74d30" title="Correlation ID" icon="link" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.correlation_id`

            Correlation ID records correlation identifier for linking related records across systems. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-description-d87507bc3633" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.description`

            Description records detailed description of the incident task. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is description text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-due-date-79bb7114e3bf" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.due_date`

            Due Date records due date for the incident task (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-escalation-ee11484eb674" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.escalation`

            Escalation records current escalation level of the task. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-expected-start-7d79d166b21f" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.expected_start`

            Expected Start records expected start date/time for the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-follow-up-fa93d1160d4c" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.follow_up`

            Follow Up records follow-up date/time for the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-group-list-113fb48281bc" title="Group List" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.group_list`

            Group List records comma-separated list of group `sys_ids` that have visibility. It is needed to preserve the explicit ServiceNow group references attached to this row.

            * **Enables:** split the references in `group_list` and match each returned group identifier to the corresponding ServiceNow group record when available.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is a list of ServiceNow group identifiers at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-impact-5b9f44c2282d" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.impact`

            Impact records impact level of the incident task. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-incident-8e6d2f87c850" title="Incident" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.incident`

            Incident records reference (`sys_id`) to the parent incident. It is needed to refer to the same incident across records without relying on display text.

            * **Enables:** match `incident` to incident references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-knowledge-6a05ff170835" title="Knowledge" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.knowledge`

            Knowledge records whether a knowledge article was used or flagged for creation. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Incident Task rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-location-fe4c1face41b" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.location`

            Location records reference (`sys_id`) to the location associated with this task. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Incident Task row.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-made-sla-19b14621bbc1" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.made_sla`

            Made Sla records whether the task met its SLA requirements. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Incident Task rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-number-07ab8f917edd" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.number`

            Number records display number for the incident task (e.g., TASK0001234). It is needed to refer to the same incident task across records without relying on display text.

            * **Enables:** match `number` to incident task references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-opened-at-d7e60166ede5" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.opened_at`

            Opened At records date/time when the task was opened (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-opened-by-048e1816ed65" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.opened_by`

            Opened By records reference (`sys_id`) to the user who opened this task. It is needed to refer to the same opened by across records without relying on display text.

            * **Enables:** match `opened_by` to opened by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-order-27e726f66a25" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.order`

            Order records execution order of the incident task. It is needed to place this Incident Task row in the order explicitly reported by ServiceNow.

            * **Enables:** order Incident Task rows by the explicit `order` sequence value returned for each Incident Task record.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-parent-871f8f907567" title="Parent" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.parent`

            Parent records reference (`sys_id`) to the parent task (often the parent incident). It is needed to refer to the same parent across records without relying on display text.

            * **Enables:** match `parent` to parent references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-priority-17273beba7f7" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.priority`

            Priority records priority level of the incident task. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-reassignment-count-50ed1dd2c66d" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.reassignment_count`

            Reassignment Count records number of times the task has been reassigned. It is needed to measure the ServiceNow-reported number of times the task has been reassigned at one Incident Task record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the task has been reassigned in `reassignment_count` at one Incident Task record per row.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is a ServiceNow-reported count at one Incident Task record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-route-reason-19c4a4e677bc" title="Route Reason" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.route_reason`

            Route Reason records reason code for the routing of the task. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned route reason value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `route_reason` label when comparing route reason.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the schema uses the `Generic.Int64` scalar; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-short-description-404f5f1adf9e" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.short_description`

            Short Description records brief description of the incident task. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is description text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sla-due-ddbfae9b1481" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sla_due`

            Sla Due records SLA due date/time for the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-state-a2087e783c39" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.state`

            State records current state of the incident task. Instance-customizable choice; known defaults include: -5, 1, 2, 3, 4, 7. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-class-name-cb2272b397b3" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_class_name`

            Sys Class Name records table class name for the record (e.g., `incident_task`). It is needed to distinguish Incident Task rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-created-by-cce2235acc2f" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Incident Task row to the returned person, account, or organization reference.

            * **Enables:** attribute the Incident Task row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-created-on-63fa0843c8a6" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_created_on`

            Sys Created On records date/time when the record was created (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-domain-ea89b14ce37e" title="Sys Domain" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_domain`

            Sys Domain records domain to which this record belongs (for domain-separated instances). It is needed to compare the returned sys domain for individual Incident Task rows and select rows with a specific `sys_domain` value.

            * **Enables:** trace the sys domain relationship returned in `sys_domain` from the Incident Task row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-domain-path-cbb3ea7112e2" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_domain_path`

            Sys Domain Path records domain path for the record. It is needed to compare the returned sys domain path for individual Incident Task rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Incident Task row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-id-20d5136a1af8" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_id`

            Sys ID records unique system identifier for the incident task. It is needed to distinguish repeated deliveries of the same Incident Task row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Incident Task and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-mod-count-6f0db7d914ba" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Incident Task record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Incident Task record per row.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is a ServiceNow-reported count at one Incident Task record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-tags-3690784358b6" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-updated-by-58a4c853bcbb" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Incident Task row to the returned person, account, or organization reference.

            * **Enables:** attribute the Incident Task row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-sys-updated-on-58de590e4ba5" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.sys_updated_on`

            Sys Updated On records date/time when the record was last updated (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-time-worked-c76640accac3" title="Time Worked" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.time_worked`

            Time Worked records total time worked on the task (duration field). It is needed to measure the exact duration reported for one Incident Task record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `time_worked` per Incident Task record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-universal-request-f162f4ca627a" title="Universal Request" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.universal_request`

            Universal Request records reference (`sys_id`) to the universal request if applicable. It is needed to refer to the same universal request across records without relying on display text.

            * **Enables:** match `universal_request` to universal request references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-upon-approval-c5e4399bd1cf" title="Upon Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.upon_approval`

            Upon Approval records action to take when the task is approved. Instance-customizable choice; known defaults include: proceed, goto. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-upon-reject-4179de13e80f" title="Upon Reject" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.upon_reject`

            Upon Reject records action to take when the task is rejected. Instance-customizable choice; known defaults include: cancel, goto. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-urgency-b6dbe0257eb3" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.urgency`

            Urgency records urgency level of the incident task. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Incident Task rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Incident Task rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-watch-list-608df60acd49" title="Watch List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.watch_list`

            Watch List records comma-separated list of user `sys_ids` watching this task. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `watch_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is a list of ServiceNow user identifiers at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-work-end-5415dafde254" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.work_end`

            Work End records date/time when work ended on the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-work-notes-12fa5b77314e" title="Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.work_notes`

            Work Notes records work notes added to the task (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is comment or journal text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-work-notes-list-2f03cbcceb7c" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.work_notes_list`

            Work Notes List records comma-separated list of work notes journal entry `sys_ids`. It is needed to refer to the same work notes list across records without relying on display text.

            * **Enables:** match `work_notes_list` to work notes list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is comment or journal text at one Incident Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-incident-task-work-start-a8221edd511b" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `incident_task.work_start`

            Work Start records date/time when work actually started on the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Incident Task records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Incident Task object returned for Incident Task; it is interpreted at one Incident Task record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-problem-efed251edb82" title="Problem" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `problem`

        Problem covers problem records from ServiceNow. Problems represent the root cause of one or more incidents and are used in problem management processes.

        * **Enables:** follow service work from the reported record through its returned assignee, status, priority, and timestamps during triage or fulfillment.
        * **Scope:** Extracts problem records from ServiceNow. Problems represent the root cause of one or more incidents and are used in problem management processes; the connector reads `/api/now/table/problem` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-problem-active-9e83cc85bbcc" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.active`

            Active records whether the problem is currently active. It is needed to distinguish Problem rows by the exact ServiceNow-returned active value.

            * **Enables:** select Problem rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-activity-due-c7b3cb3d3cfb" title="Activity Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.activity_due`

            Activity Due records date/time the next activity is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `activity_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-additional-assignee-list-f5eb7e400d32" title="Additional Assignee List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.additional_assignee_list`

            Additional Assignee List records list of additional assignees. It is needed to attribute this Problem row to the returned person, account, or organization reference.

            * **Enables:** attribute the Problem row to the returned person or account and match the exact `additional_assignee_list` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-approval-14f2ce7a82c0" title="Approval" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.approval`

            Approval records approval status of the problem. It is needed to distinguish Problem rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-approval-history-6e5b9cc24701" title="Approval History" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.approval_history`

            Approval History records history of approval actions. It is needed to distinguish Problem rows by the exact ServiceNow-returned approval history value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `approval_history` label when comparing approval history.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-approval-set-5e8824593c25" title="Approval Set" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.approval_set`

            Approval Set records date/time the approval was set. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `approval_set`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-assigned-to-157f707be858" title="Assigned To" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.assigned_to`

            Assigned To records `Sys_id` of the individual assigned to investigate the problem. It is needed to refer to the same assigned to across records without relying on display text.

            * **Enables:** match `assigned_to` to assigned to references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-assignment-group-a5b06e5a3e74" title="Assignment Group" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.assignment_group`

            Assignment Group records `Sys_id` of the group assigned to investigate the problem. It is needed to refer to the same assignment group across records without relying on display text.

            * **Enables:** match `assignment_group` to assignment group references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-business-duration-e9a6d4517d9a" title="Business Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.business_duration`

            Business Duration records business duration elapsed. It is needed to measure the exact duration reported for one Problem record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_duration` per Problem record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-business-service-540f1428f7b3" title="Business Service" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.business_service`

            Business Service records `Sys_id` of the business service affected by the problem. It is needed to refer to the same business service across records without relying on display text.

            * **Enables:** match `business_service` to business service references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-calendar-duration-ccec66605c6d" title="Calendar Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.calendar_duration`

            Calendar Duration records calendar duration elapsed. It is needed to measure the exact duration reported for one Problem record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_duration` per Problem record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-category-dd32caac65d3" title="Category" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.category`

            Category records category classification. It is needed to distinguish Problem rows by the exact ServiceNow-returned category value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `category` label when comparing category.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-cause-notes-9c4c9c3aa50b" title="Cause Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.cause_notes`

            Cause Notes records root cause analysis notes. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `cause_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-close-notes-a4e1cfcf1975" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.close_notes`

            Close Notes records notes recorded when the problem was closed. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-closed-at-04ebf39b0eed" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.closed_at`

            Closed At records date/time the problem was closed (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-closed-by-dfb4403db6c1" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.closed_by`

            Closed By records `Sys_id` of the user who closed the problem. It is needed to refer to the same closed by across records without relying on display text.

            * **Enables:** match `closed_by` to closed by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-cmdb-ci-896b48fe6dbb" title="Cmdb Ci" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.cmdb_ci`

            Cmdb Ci records `Sys_id` of the configuration item related to the problem. It is needed to refer to the same cmdb ci across records without relying on display text.

            * **Enables:** match `cmdb_ci` to cmdb ci references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-comments-a7a704989d02" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.comments`

            Comments records additional comments (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-comments-and-work-notes-59cd5e1d59a2" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-company-8c6e5c599d94" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.company`

            Company records `Sys_id` of the company associated with the problem. It is needed to refer to the same company across records without relying on display text.

            * **Enables:** match `company` to company references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-confirmed-at-abffdafc492a" title="Confirmed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.confirmed_at`

            Confirmed At records date/time the problem was confirmed (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `confirmed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-confirmed-by-51f5fe2b98fa" title="Confirmed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.confirmed_by`

            Confirmed By records `Sys_id` of the user who confirmed the problem. It is needed to refer to the same confirmed by across records without relying on display text.

            * **Enables:** match `confirmed_by` to confirmed by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-contact-type-ed5becd208b7" title="Contact Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.contact_type`

            Contact Type records how the problem was reported (e.g., phone, email, self-service). It is needed to distinguish Problem rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-correlation-display-acd26151cfce" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.correlation_display`

            Correlation Display records display value for the correlation identifier. It is needed to refer to the same correlation display across records without relying on display text.

            * **Enables:** match `correlation_display` to correlation display references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-correlation-id-6e561cfc9c6a" title="Correlation ID" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.correlation_id`

            Correlation ID records correlation identifier for external integrations. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-description-ec1a43912ac7" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.description`

            Description records detailed description of the problem. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is description text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-due-date-f9097c29c860" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.due_date`

            Due Date records due date for the problem resolution (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-duplicate-of-dff4290370d2" title="Duplicate Of" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.duplicate_of`

            Duplicate Of records `Sys_id` of the problem this is a duplicate of. It is needed to refer to the same duplicate of across records without relying on display text.

            * **Enables:** match `duplicate_of` to duplicate of references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-escalation-163e309a7941" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.escalation`

            Escalation records escalation level of the problem. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Problem rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-expected-start-215510920cda" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.expected_start`

            Expected Start records expected start date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-first-reported-by-task-76ad26a65c83" title="First Reported By Task" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.first_reported_by_task`

            First Reported By Task records `Sys_id` of the first task (e.g., incident) that reported this problem. It is needed to refer to the same first reported by task across records without relying on display text.

            * **Enables:** match `first_reported_by_task` to first reported by task references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-fix-at-dea0ae6fa524" title="Fix At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.fix_at`

            Fix At records date/time the fix was applied (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `fix_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-fix-by-2a357c593e8e" title="Fix By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.fix_by`

            Fix By records `Sys_id` of the user who applied the fix. It is needed to refer to the same fix by across records without relying on display text.

            * **Enables:** match `fix_by` to fix by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-fix-communicated-at-fd48987e2846" title="Fix Communicated At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.fix_communicated_at`

            Fix Communicated At records date/time the fix was communicated. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `fix_communicated_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-fix-communicated-by-155afea93feb" title="Fix Communicated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.fix_communicated_by`

            Fix Communicated By records `Sys_id` of the user who communicated the fix. It is needed to refer to the same fix communicated by across records without relying on display text.

            * **Enables:** match `fix_communicated_by` to fix communicated by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-fix-notes-511ad98c3945" title="Fix Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.fix_notes`

            Fix Notes records fix or workaround notes. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `fix_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-follow-up-08aee3b187c3" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.follow_up`

            Follow Up records follow-up date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-group-list-1f5d27dd8367" title="Group List" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.group_list`

            Group List records list of groups associated with the problem. It is needed to preserve the explicit ServiceNow group references attached to this row.

            * **Enables:** split the references in `group_list` and match each returned group identifier to the corresponding ServiceNow group record when available.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is a list of ServiceNow group identifiers at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-impact-0568c726731f" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.impact`

            Impact records impact level of the problem. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Problem rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-knowledge-fba3e7152724" title="Knowledge" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.knowledge`

            Knowledge records whether a knowledge article has been created from this problem. It is needed to distinguish Problem rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Problem rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-known-error-0720bd90b09a" title="Known Error" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.known_error`

            Known Error records whether this problem has been identified as a known error. It is needed to distinguish Problem rows by the exact ServiceNow-returned known error value.

            * **Enables:** select Problem rows where `known_error` is true or false when comparing the condition described by Known Error.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-location-0461db94aaf2" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `problem.location`

            Location records `Sys_id` of the location associated with the problem. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Problem row.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-made-sla-e09bf14499a5" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.made_sla`

            Made Sla records whether the problem met its SLA requirements. It is needed to distinguish Problem rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Problem rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-major-problem-2daea4e1fd3b" title="Major Problem" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.major_problem`

            Major Problem records whether this is classified as a major problem. It is needed to distinguish Problem rows by the exact ServiceNow-returned major problem value.

            * **Enables:** select Problem rows where `major_problem` is true or false when comparing the condition described by Major Problem.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-notify-cd5a0090e3f2" title="Notify" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.notify`

            Notify records notification setting. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to compare the exact notify configuration returned for this Problem record.

            * **Enables:** compare the exact `notify` configuration returned for each Problem record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-number-9344a4179d75" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.number`

            Number records problem number (e.g., PRB0001234). It is needed to refer to the same problem across records without relying on display text.

            * **Enables:** match `number` to problem references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-opened-at-2ef05bb5ac7d" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.opened_at`

            Opened At records date/time the problem was opened (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-opened-by-9517244fc29f" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.opened_by`

            Opened By records `Sys_id` of the user who opened the problem. It is needed to refer to the same opened by across records without relying on display text.

            * **Enables:** match `opened_by` to opened by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-order-89a6aabeacbc" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.order`

            Order records order value for sorting. It is needed to place this Problem row in the order explicitly reported by ServiceNow.

            * **Enables:** order Problem rows by the explicit `order` sequence value returned for each Problem record.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-priority-d08e6679c676" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.priority`

            Priority records priority level of the problem. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Problem rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-problem-state-8f874c6a46c2" title="Problem State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.problem_state`

            Problem State records problem-specific state value. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5, 6, 7. It is needed to distinguish Problem rows by the exact ServiceNow-returned problem state value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `problem_state` label when comparing problem state.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-reassignment-count-e09a4e457bf4" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.reassignment_count`

            Reassignment Count records number of times the problem has been reassigned. It is needed to measure the ServiceNow-reported number of times the problem has been reassigned at one Problem record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the problem has been reassigned in `reassignment_count` at one Problem record per row.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is a ServiceNow-reported count at one Problem record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-related-incidents-70e13a79177b" title="Related Incidents" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.related_incidents`

            Related Incidents records count of related incidents. It is needed to measure the ServiceNow-reported number of related incidents at one Problem record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of related incidents in `related_incidents` at one Problem record per row.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is a ServiceNow-reported count at one Problem record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-reopen-count-849972eee4e9" title="Reopen Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.reopen_count`

            Reopen Count records number of times the problem has been reopened. It is needed to measure the ServiceNow-reported number of times the problem has been reopened at one Problem record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the problem has been reopened in `reopen_count` at one Problem record per row.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is a ServiceNow-reported count at one Problem record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-reopened-at-5c7a55e17968" title="Reopened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.reopened_at`

            Reopened At records date/time the problem was last reopened. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `reopened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-reopened-by-8400c5e64cff" title="Reopened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.reopened_by`

            Reopened By records `Sys_id` of the user who last reopened the problem. It is needed to refer to the same reopened by across records without relying on display text.

            * **Enables:** match `reopened_by` to reopened by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-resolved-at-e3fe8da8ead0" title="Resolved At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.resolved_at`

            Resolved At records date/time the problem was resolved (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `resolved_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-resolved-by-2d847cfbdcea" title="Resolved By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.resolved_by`

            Resolved By records `Sys_id` of the user who resolved the problem. It is needed to refer to the same resolved by across records without relying on display text.

            * **Enables:** match `resolved_by` to resolved by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-review-outcome-580553e43a75" title="Review Outcome" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.review_outcome`

            Review Outcome records outcome of the problem review. It is needed to distinguish Problem rows by the exact ServiceNow-returned review outcome value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `review_outcome` label when comparing review outcome.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-rfc-b3b155a5f091" title="Rfc" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.rfc`

            Rfc records `Sys_id` of the associated change request (Request for Change). It is needed to refer to the same rfc across records without relying on display text.

            * **Enables:** match `rfc` to rfc references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-service-offering-2314a84ccdc9" title="Service Offering" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.service_offering`

            Service Offering records `Sys_id` of the service offering affected. It is needed to refer to the same service offering across records without relying on display text.

            * **Enables:** match `service_offering` to service offering references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-short-description-fac44c7fd2fb" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.short_description`

            Short Description records brief summary of the problem. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is description text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sla-due-e8a4ad3870ca" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sla_due`

            Sla Due records SLA due date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-state-d1aee8a1a0af" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.state`

            State records current state of the problem. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5, 6, 7. It is needed to distinguish Problem rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-subcategory-172fd94e7cd5" title="Subcategory" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.subcategory`

            Subcategory records subcategory classification. It is needed to distinguish Problem rows by the exact ServiceNow-returned subcategory value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `subcategory` label when comparing subcategory.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-class-name-3b5a9a9704a8" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_class_name`

            Sys Class Name records table class name for the record. It is needed to distinguish Problem rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-created-by-0fe546401020" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Problem row to the returned person, account, or organization reference.

            * **Enables:** attribute the Problem row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-created-on-de0ccac332ab" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_created_on`

            Sys Created On records date/time the record was created (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-domain-5dcd0a49c645" title="Sys Domain" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_domain`

            Sys Domain records domain of the record for domain separation. It is needed to compare the returned sys domain for individual Problem rows and select rows with a specific `sys_domain` value.

            * **Enables:** trace the sys domain relationship returned in `sys_domain` from the Problem row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-domain-path-2afaf0829218" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_domain_path`

            Sys Domain Path records domain path of the record. It is needed to compare the returned sys domain path for individual Problem rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Problem row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-id-026bc7ef8d0f" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_id`

            Sys ID records unique system identifier for the problem record. It is needed to distinguish repeated deliveries of the same Problem row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Problem and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-mod-count-e941101dabed" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Problem record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Problem record per row.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is a ServiceNow-reported count at one Problem record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-tags-74cbd781ccca" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Problem rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-updated-by-b6475523660e" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Problem row to the returned person, account, or organization reference.

            * **Enables:** attribute the Problem row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-sys-updated-on-661aff9dfb23" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.sys_updated_on`

            Sys Updated On records date/time the record was last updated (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-time-worked-10ebb3f5a6d1" title="Time Worked" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `problem.time_worked`

            Time Worked records total time worked on the problem (duration). It is needed to measure the exact duration reported for one Problem record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `time_worked` per Problem record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-upon-approval-f1578dda4b8e" title="Upon Approval" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.upon_approval`

            Upon Approval records action to take when the problem is approved. It is needed to distinguish Problem rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-upon-reject-1af2b1bd8959" title="Upon Reject" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `problem.upon_reject`

            Upon Reject records action to take when the problem is rejected. It is needed to distinguish Problem rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-urgency-770652de4d76" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.urgency`

            Urgency records urgency level of the problem. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Problem rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Problem rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-watch-list-9fe10fafca8c" title="Watch List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `problem.watch_list`

            Watch List records list of users watching this problem. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `watch_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is a list of ServiceNow user identifiers at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-work-end-ef14f15d1f56" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.work_end`

            Work End records date/time work ended on the problem. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-work-notes-ec48b975469b" title="Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.work_notes`

            Work Notes records work notes (journal field, internal). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-work-notes-list-4ca4142c039b" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `problem.work_notes_list`

            Work Notes List records list of users notified for work notes. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `work_notes_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is comment or journal text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-work-start-539b62e24032" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `problem.work_start`

            Work Start records date/time work started on the problem. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Problem records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is interpreted at one Problem record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-problem-workaround-bd15bd089b31" title="Workaround" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `problem.workaround`

            Workaround records workaround description for the problem. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `workaround` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Problem object returned for Problem; it is descriptive text at one Problem record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sc-req-item-3135e5765f62" title="Requested Items" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `sc_req_item`

        Requested Items covers requested items (catalog items ordered through the service catalog) from ServiceNow. Each record represents a single line item within a service catalog request, tracking fulfillment status, assigned groups, and approval state.

        * **Enables:** map the ServiceNow accounts and memberships represented by Requested Items records and trace a returned access assignment to its account or group.
        * **Scope:** Extracts requested items (catalog items ordered through the service catalog) from ServiceNow. Each record represents a single line item within a service catalog request, tracking fulfillment status, assigned groups, and approval state; the connector reads `/api/now/table/sc_req_item` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sc-req-item-active-0e0164a8ac50" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.active`

            Active records whether the requested item is active (true/false as string). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned active value.

            * **Enables:** select Requested Items rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-activity-due-9b9ffa383222" title="Activity Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.activity_due`

            Activity Due records date/time when the next SLA activity is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `activity_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-additional-comments-ebc6f06747f8" title="Additional Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.additional_comments`

            Additional Comments records additional customer-visible comments. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `additional_comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is comment or journal text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-approval-d4351bfb7687" title="Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.approval`

            Approval records approval status of the requested item. Instance-customizable choice; known defaults include: not requested, requested, approved, rejected, duplicate. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-assigned-to-96a34c153857" title="Assigned To" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.assigned_to`

            Assigned To records reference (`sys_id`) to the user assigned to fulfill this item. It is needed to refer to the same assigned to across records without relying on display text.

            * **Enables:** match `assigned_to` to assigned to references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-assignment-group-3e30994e869e" title="Assignment Group" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.assignment_group`

            Assignment Group records reference (`sys_id`) to the group assigned to fulfill this item. It is needed to refer to the same assignment group across records without relying on display text.

            * **Enables:** match `assignment_group` to assignment group references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-backordered-e83864a356fc" title="Backordered" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.backordered`

            Backordered records whether the item is backordered (true/false as string). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned backordered value.

            * **Enables:** select Requested Items rows where `backordered` is true or false when comparing the condition described by Backordered.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-billable-0d35e0842880" title="Billable" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.billable`

            Billable records whether the item is billable (true/false as string). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned billable value.

            * **Enables:** select Requested Items rows where `billable` is true or false when comparing the condition described by Billable.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-business-duration-a8d2d1b5d968" title="Business Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.business_duration`

            Business Duration records business duration elapsed for fulfillment. It is needed to measure the exact duration reported for one Sc Req Item record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_duration` per Sc Req Item record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-business-service-07464d5abe75" title="Business Service" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.business_service`

            Business Service records reference (`sys_id`) to the associated business service. It is needed to refer to the same business service across records without relying on display text.

            * **Enables:** match `business_service` to business service references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-calendar-duration-f8831a98e0f1" title="Calendar Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.calendar_duration`

            Calendar Duration records calendar duration elapsed for fulfillment. It is needed to measure the exact duration reported for one Sc Req Item record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_duration` per Sc Req Item record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-cat-item-5587fa23c52c" title="Cat Item" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.cat_item`

            Cat Item records reference (`sys_id`) to the catalog item definition. It is needed to refer to the same cat item across records without relying on display text.

            * **Enables:** match `cat_item` to cat item references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-catalogs-43a111175175" title="Catalogs" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.catalogs`

            Catalogs records comma-separated list of catalog `sys_ids`. It is needed to preserve the explicit ServiceNow catalog references attached to this row.

            * **Enables:** split the references in `catalogs` and match each returned catalog identifier to the corresponding ServiceNow catalog record when available.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is a list of ServiceNow catalog identifiers at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-close-notes-cf64dce2e375" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.close_notes`

            Close Notes records notes recorded when the item was closed. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is comment or journal text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-closed-at-cedbed226625" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.closed_at`

            Closed At records date/time when the requested item was closed (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-closed-by-d41e2dde0e91" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.closed_by`

            Closed By records reference (`sys_id`) to the user who closed this requested item. It is needed to refer to the same closed by across records without relying on display text.

            * **Enables:** match `closed_by` to closed by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-cmdb-ci-ae2dc80d1fc0" title="Cmdb Ci" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.cmdb_ci`

            Cmdb Ci records reference (`sys_id`) to the CMDB configuration item. It is needed to refer to the same cmdb ci across records without relying on display text.

            * **Enables:** match `cmdb_ci` to cmdb ci references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-comments-de61bc152832" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.comments`

            Comments records customer-visible comments (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is comment or journal text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-comments-and-work-notes-d47ed7778484" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is comment or journal text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-company-4e3daef89ab5" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.company`

            Company records reference (`sys_id`) to the company associated with this item. It is needed to refer to the same company across records without relying on display text.

            * **Enables:** match `company` to company references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-configuration-item-5a8b606c8c5a" title="Configuration Item" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.configuration_item`

            Configuration Item records reference (`sys_id`) to the associated configuration item (CMDB CI). It is needed to refer to the same configuration item across records without relying on display text.

            * **Enables:** match `configuration_item` to configuration item references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-contact-type-de89a9739090" title="Contact Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.contact_type`

            Contact Type records how the request was submitted (e.g., phone, email, self-service). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-context-ef9130f930c1" title="Context" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.context`

            Context records reference (`sys_id`) to the workflow context. It is needed to refer to the same context across records without relying on display text.

            * **Enables:** match `context` to context references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-correlation-display-f0f1d3e1b13d" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.correlation_display`

            Correlation Display records display value for the correlation identifier. It is needed to refer to the same correlation display across records without relying on display text.

            * **Enables:** match `correlation_display` to correlation display references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-correlation-id-0baf7ff3d23e" title="Correlation ID" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.correlation_id`

            Correlation ID records correlation identifier for external integrations. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-delivery-plan-7bb0bd893fc1" title="Delivery Plan" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.delivery_plan`

            Delivery Plan records reference (`sys_id`) to the delivery plan. It is needed to refer to the same delivery plan across records without relying on display text.

            * **Enables:** match `delivery_plan` to delivery plan references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is descriptive text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-delivery-task-d5770619bcea" title="Delivery Task" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.delivery_task`

            Delivery Task records reference (`sys_id`) to the delivery task. It is needed to refer to the same delivery task across records without relying on display text.

            * **Enables:** match `delivery_task` to delivery task references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-description-bbafff9335ac" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.description`

            Description records detailed description of the requested item. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is description text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-due-date-4e3da196709d" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.due_date`

            Due Date records due date for fulfillment of the requested item (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-escalation-49b894afe129" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.escalation`

            Escalation records current escalation level. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-estimated-delivery-581a3c018f5c" title="Estimated Delivery" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.estimated_delivery`

            Estimated Delivery records estimated delivery date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `estimated_delivery`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-expected-start-719814bd0b47" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.expected_start`

            Expected Start records expected start date/time for fulfillment. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-follow-up-10c2f55cc744" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.follow_up`

            Follow Up records follow-up date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-impact-f2be9f11db39" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.impact`

            Impact records impact level of the requested item. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-knowledge-bc0e872f852b" title="Knowledge" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.knowledge`

            Knowledge records whether a knowledge article was used (true/false as string). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Requested Items rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-location-9c0e8c657577" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.location`

            Location records reference (`sys_id`) to the location associated with this item. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Sc Req Item row.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-made-sla-807b9ecb6ade" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.made_sla`

            Made Sla records whether the SLA was met (true/false as string). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Requested Items rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-number-ba0d34ac5aaf" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.number`

            Number records display number for the requested item (e.g., RITM0001234). It is needed to refer to the same requested items across records without relying on display text.

            * **Enables:** match `number` to requested items references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-opened-at-67a822d987f9" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.opened_at`

            Opened At records date/time when the requested item was opened (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-opened-by-32eb28f7ee4f" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.opened_by`

            Opened By records reference (`sys_id`) to the user who opened this requested item. It is needed to refer to the same opened by across records without relying on display text.

            * **Enables:** match `opened_by` to opened by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-order-7d296324e255" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.order`

            Order records order value used for sorting or sequencing. It is needed to place this Requested Items row in the order explicitly reported by ServiceNow.

            * **Enables:** order Requested Items rows by the explicit `order` sequence value returned for each Sc Req Item record.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-order-guide-ff781359e7c6" title="Order Guide" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.order_guide`

            Order Guide records reference (`sys_id`) to the order guide used. It is needed to refer to the same order guide across records without relying on display text.

            * **Enables:** match `order_guide` to order guide references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-price-354994c4b346" title="Price" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.price`

            Price records price of the requested item as a decimal string. It is needed to measure the exact commercial amount reported on this record.

            * **Enables:** measure and compare the reported `price` amount for Requested Items records, using the record's currency code when one is returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the ServiceNow response determines the currency or pricing basis; do not infer one when it is absent.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-priority-b81ea9bce734" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.priority`

            Priority records priority level of the requested item. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-quantity-af1567f77732" title="Quantity" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.quantity`

            Quantity records quantity ordered. It is needed to measure the ServiceNow-reported number of quantity at one Sc Req Item record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of quantity in `quantity` at one Sc Req Item record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is a ServiceNow-reported count at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-reassignment-count-b80e5dd22fed" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.reassignment_count`

            Reassignment Count records number of times the item has been reassigned. It is needed to measure the ServiceNow-reported number of times the item has been reassigned at one Sc Req Item record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the item has been reassigned in `reassignment_count` at one Sc Req Item record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is a ServiceNow-reported count at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-recurring-frequency-fdfb97d8320f" title="Recurring Frequency" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.recurring_frequency`

            Recurring Frequency records frequency of recurring charges (e.g., monthly, yearly). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned recurring frequency value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `recurring_frequency` label when comparing recurring frequency.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-recurring-price-7ccbaee26287" title="Recurring Price" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.recurring_price`

            Recurring Price records recurring price for the requested item. It is needed to measure the exact commercial amount reported on this record.

            * **Enables:** measure and compare the reported `recurring_price` amount for Requested Items records, using the record's currency code when one is returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the ServiceNow response determines the currency or pricing basis; do not infer one when it is absent.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-request-40b2cef9bae8" title="Request" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.request`

            Request records reference (`sys_id`) to the parent service catalog request (`sc_request`). It is needed to refer to the same request across records without relying on display text.

            * **Enables:** match `request` to request references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-request-model-7685c0640952" title="Request Model" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.request_model`

            Request Model records reference (`sys_id`) to the request model. It is needed to refer to the same request model across records without relying on display text.

            * **Enables:** match `request_model` to request model references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-requested-for-b1ae3b75c1a0" title="Requested For" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.requested_for`

            Requested For records reference (`sys_id`) to the user the item was requested for. It is needed to refer to the same requested for across records without relying on display text.

            * **Enables:** match `requested_for` to requested for references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sc-catalog-c36bae33d505" title="Sc Catalog" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sc_catalog`

            Sc Catalog records reference (`sys_id`) to the service catalog this item belongs to. It is needed to refer to the same sc catalog across records without relying on display text.

            * **Enables:** match `sc_catalog` to sc catalog references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-short-description-4ad6fe034f05" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.short_description`

            Short Description records brief description of the requested item. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is description text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sla-due-bc0b083d1bb7" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sla_due`

            Sla Due records SLA due date/time. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-stage-64b1c3f3f3cb" title="Stage" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.stage`

            Stage records current stage in the fulfillment workflow. Instance-customizable choice; known defaults include: `waiting_for_approval`, fulfillment, delivery, completed, `request_cancelled`. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned stage value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `stage` label when comparing stage.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-state-b57d123e8449" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.state`

            State records current state of the requested item fulfillment. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 7, 8, 9, 10. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-class-name-2857007a900c" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_class_name`

            Sys Class Name records table class name for the record (e.g., `sc_req_item`). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-created-by-26ad402bc006" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Requested Items row to the returned person, account, or organization reference.

            * **Enables:** attribute the Requested Items row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-created-on-c9a7ee9a5958" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_created_on`

            Sys Created On records date/time when the record was created (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-domain-dfb6d8d24eab" title="Sys Domain" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_domain`

            Sys Domain records domain to which the record belongs. It is needed to compare the returned sys domain for individual Requested Items rows and select rows with a specific `sys_domain` value.

            * **Enables:** trace the sys domain relationship returned in `sys_domain` from the Sc Req Item row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-domain-path-9a904114ab5d" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_domain_path`

            Sys Domain Path records domain path for the record. It is needed to compare the returned sys domain path for individual Requested Items rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Sc Req Item row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-id-148c2940ae76" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_id`

            Sys ID records unique system identifier for the requested item record. It is needed to distinguish repeated deliveries of the same Requested Items row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Requested Items and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-mod-count-456899ca5f70" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Sc Req Item record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Sc Req Item record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is a ServiceNow-reported count at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-tags-ff3833263a67" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-updated-by-29f05f96305b" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Requested Items row to the returned person, account, or organization reference.

            * **Enables:** attribute the Requested Items row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-sys-updated-on-b8b3d4bb2a6e" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.sys_updated_on`

            Sys Updated On records date/time when the record was last updated (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-upon-approval-3fa2fb332a58" title="Upon Approval" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.upon_approval`

            Upon Approval records action to take upon approval (e.g., proceed). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-upon-reject-7e2f595170dd" title="Upon Reject" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.upon_reject`

            Upon Reject records action to take upon rejection (e.g., cancel). It is needed to distinguish Requested Items rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-urgency-24ef32105ebe" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.urgency`

            Urgency records urgency level of the requested item. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Requested Items rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Requested Items rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-variables-910a4bd5eab5" title="Variables" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.variables`

            Variables records catalog item variable values submitted with the request. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `variables` and associate them with the containing Requested Items record.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this ServiceNow response and may vary by object type or ServiceNow configuration.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-work-end-ac313e5095c2" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.work_end`

            Work End records date/time when work ended on the item. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-work-notes-69d5e6ff9ad9" title="Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.work_notes`

            Work Notes records internal work notes (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is comment or journal text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-work-notes-list-626e99ddf27d" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.work_notes_list`

            Work Notes List records comma-separated list of work note `sys_ids`. It is needed to refer to the same work notes list across records without relying on display text.

            * **Enables:** match `work_notes_list` to work notes list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is comment or journal text at one Sc Req Item record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-req-item-work-start-c16ba319ca11" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_req_item.work_start`

            Work Start records date/time when work started on the item. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Requested Items records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Req Item object returned for Requested Items; it is interpreted at one Sc Req Item record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sc-request-285c82407840" title="Service Requests" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `sc_request`

        Service Requests covers service catalog requests (`sc_request` table) from ServiceNow. These represent user-initiated requests for services, hardware, software, or other catalog items.

        * **Enables:** follow service work from the reported record through its returned assignee, status, priority, and timestamps during triage or fulfillment.
        * **Scope:** Extracts service catalog requests (`sc_request` table) from ServiceNow. These represent user-initiated requests for services, hardware, software, or other catalog items; the connector reads `/api/now/table/sc_request` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sc-request-active-5ba7d80a5e1c" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.active`

            Active records whether the request is active (true/false as string when `sysparm_display_value`=false). It is needed to distinguish Service Requests rows by the exact ServiceNow-returned active value.

            * **Enables:** select Service Requests rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-activity-due-b710e353ae72" title="Activity Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.activity_due`

            Activity Due records date/time the next SLA activity is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `activity_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-additional-assignee-list-f8405b1acaef" title="Additional Assignee List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.additional_assignee_list`

            Additional Assignee List records list of additional assignees. It is needed to attribute this Service Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Service Requests row to the returned person or account and match the exact `additional_assignee_list` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-approval-585b0068cdb0" title="Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.approval`

            Approval records approval status of the request. Instance-customizable choice; known defaults include: not requested, requested, approved, rejected, cancelled, duplicate. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-assigned-to-06260de48e85" title="Assigned To" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.assigned_to`

            Assigned To records individual assigned to the request (`sys_id` reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `assigned_to` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-assignment-group-9df1fee75f06" title="Assignment Group" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.assignment_group`

            Assignment Group records group assigned to fulfill the request (`sys_id` reference to `sys_user_group`). It is needed to refer to the same `sys_user_group` across records without relying on display text.

            * **Enables:** match `assignment_group` to `sys_user_group` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-business-duration-5e8ddf55a98e" title="Business Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.business_duration`

            Business Duration records business duration in display format. It is needed to measure the exact duration reported for one Sc Request record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_duration` per Sc Request record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-business-stc-ff828132616d" title="Business Stc" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.business_stc`

            Business Stc records business duration in seconds. It is needed to measure the exact duration reported for one Sc Request record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_stc` per Sc Request record in seconds.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-calendar-duration-ce64d56be09f" title="Calendar Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.calendar_duration`

            Calendar Duration records calendar duration in display format. It is needed to measure the exact duration reported for one Sc Request record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_duration` per Sc Request record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-calendar-stc-0ee0e7c1b477" title="Calendar Stc" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.calendar_stc`

            Calendar Stc records calendar duration in seconds. It is needed to measure the exact duration reported for one Sc Request record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_stc` per Sc Request record in seconds.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-category-d4f1f219247b" title="Category" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.category`

            Category records category of the request. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned category value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `category` label when comparing category.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-close-notes-141169f80639" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.close_notes`

            Close Notes records notes recorded when the request was closed. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is comment or journal text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-closed-at-99dd17b20a6d" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.closed_at`

            Closed At records date/time the request was closed (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-closed-by-e822d71322be" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.closed_by`

            Closed By records user who closed the request (`sys_id` reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `closed_by` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-comments-d10120d62d0f" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.comments`

            Comments records additional comments (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is comment or journal text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-comments-and-work-notes-efa4bf555bf5" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is comment or journal text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-company-954ab0bd49f9" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.company`

            Company records company associated with the request (`sys_id` reference to `core_company`). It is needed to refer to the same `core_company` across records without relying on display text.

            * **Enables:** match `company` to `core_company` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-contact-type-f04797b8c0f5" title="Contact Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.contact_type`

            Contact Type records how the request was initiated (e.g., phone, email, self-service). It is needed to distinguish Service Requests rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-correlation-display-da031e221862" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.correlation_display`

            Correlation Display records display value for the correlation. It is needed to compare the returned correlation display for individual Service Requests rows and select rows with a specific `correlation_display` value.

            * **Enables:** locate Service Requests rows whose returned correlation display exactly matches `correlation_display` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-correlation-id-e5d823b4ff61" title="Correlation ID" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.correlation_id`

            Correlation ID records correlation ID for external integrations. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-delivery-address-d3c41122923a" title="Delivery Address" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.delivery_address`

            Delivery Address records delivery address for physical items. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `delivery_address` for individual Service Requests rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-delivery-plan-548febee988d" title="Delivery Plan" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.delivery_plan`

            Delivery Plan records delivery plan associated with the request (`sys_id` reference). It is needed to refer to the same delivery plan across records without relying on display text.

            * **Enables:** match `delivery_plan` to delivery plan references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is descriptive text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-delivery-task-24d53cf838f2" title="Delivery Task" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.delivery_task`

            Delivery Task records current delivery task (`sys_id` reference). It is needed to refer to the same delivery task across records without relying on display text.

            * **Enables:** match `delivery_task` to delivery task references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-department-61c4dcec2aca" title="Department" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.department`

            Department records department associated with the request (`sys_id` reference to `cmn_department`). It is needed to refer to the same `cmn_department` across records without relying on display text.

            * **Enables:** match `department` to `cmn_department` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-description-d745f299c1a4" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.description`

            Description records detailed description of the request. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is description text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-due-date-f81ab6d06751" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.due_date`

            Due Date records due date for the request (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-escalation-e9e645b14fdd" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.escalation`

            Escalation records escalation level of the request. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-expected-start-5a0af7564553" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.expected_start`

            Expected Start records expected start date (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-follow-up-862f55c94c47" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.follow_up`

            Follow Up records follow-up date (format: yyyy-MM-dd). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-impact-549685e91b3b" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.impact`

            Impact records impact level of the request. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-knowledge-75129aa38d1f" title="Knowledge" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.knowledge`

            Knowledge records whether knowledge was used (true/false). It is needed to distinguish Service Requests rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Service Requests rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-location-431e54e25aec" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.location`

            Location records location associated with the request (`sys_id` reference to `cmn_location`). It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Sc Request row.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-made-sla-7013d8810a09" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.made_sla`

            Made Sla records whether the request met its SLA (true/false). It is needed to distinguish Service Requests rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Service Requests rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-notify-cb29d285ebca" title="Notify" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.notify`

            Notify records notification setting. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to compare the exact notify configuration returned for this Sc Request record.

            * **Enables:** compare the exact `notify` configuration returned for each Sc Request record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-number-607caf885cee" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.number`

            Number records request number (e.g., REQ0010001). It is needed to refer to the same service requests across records without relying on display text.

            * **Enables:** match `number` to service requests references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-opened-at-3ebe7bd133a3" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.opened_at`

            Opened At records date/time the request was opened (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-opened-by-169798ee9e29" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.opened_by`

            Opened By records user who opened the request (`sys_id` reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `opened_by` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-order-72e219ae8970" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.order`

            Order records order value for sorting. It is needed to place this Service Requests row in the order explicitly reported by ServiceNow.

            * **Enables:** order Service Requests rows by the explicit `order` sequence value returned for each Sc Request record.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-parent-d91d7e41b33e" title="Parent" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.parent`

            Parent records parent record `sys_id`. It is needed to refer to the same parent across records without relying on display text.

            * **Enables:** match `parent` to parent references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-price-a3379259479b" title="Price" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.price`

            Price records total price of the request. It is needed to measure the exact commercial amount reported on this record.

            * **Enables:** measure and compare the reported `price` amount for Service Requests records, using the record's currency code when one is returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the ServiceNow response determines the currency or pricing basis; do not infer one when it is absent.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-priority-becee68ce48e" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.priority`

            Priority records priority level of the request. Instance-customizable choice; known defaults include: 1, 2, 3, 4. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-reassignment-count-5399ee2bced9" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.reassignment_count`

            Reassignment Count records number of times the request has been reassigned. It is needed to measure the ServiceNow-reported number of times the request has been reassigned at one Sc Request record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the request has been reassigned in `reassignment_count` at one Sc Request record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is a ServiceNow-reported count at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-request-date-1032063d9fc0" title="Request Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.request_date`

            Request Date records date the request was submitted. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `request_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-request-state-fbc97d207d3c" title="Request State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.request_state`

            Request State records current state of the request. Instance-customizable choice; known defaults include: draft, `pending_approval`, approved, sourcing, `in_process`, complete, `closed_complete`, `closed_incomplete`, `closed_cancelled`, `closed_rejected`. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned request state value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `request_state` label when comparing request state.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-requested-date-6ab506bda6f0" title="Requested Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.requested_date`

            Requested Date records date the service or item is requested for. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `requested_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-requested-for-6a3bd14cfb38" title="Requested For" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.requested_for`

            Requested For records user the request is for (`sys_id` reference to `sys_user`). It is needed to refer to the same `sys_user` across records without relying on display text.

            * **Enables:** match `requested_for` to `sys_user` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-route-reason-2fe0c8b77240" title="Route Reason" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.route_reason`

            Route Reason records reason for routing the request. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned route reason value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `route_reason` label when comparing route reason.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-service-offering-858b25f2ee84" title="Service Offering" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.service_offering`

            Service Offering records service offering associated with the request (`sys_id` reference). It is needed to refer to the same service offering across records without relying on display text.

            * **Enables:** match `service_offering` to service offering references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-short-description-56fdb0f9b3ad" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.short_description`

            Short Description records brief description of the request. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is description text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sla-due-0b57efd51d54" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sla_due`

            Sla Due records SLA due date (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-special-instructions-9c208d48e32b" title="Special Instructions" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.special_instructions`

            Special Instructions records special instructions for the request. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `special_instructions` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is descriptive text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-stage-8fa7cde34e97" title="Stage" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.stage`

            Stage records stage of the request workflow. Instance-customizable choice; known defaults include: `waiting_for_approval`, `request_approved`, fulfillment, delivery, completed, closed. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned stage value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `stage` label when comparing stage.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-state-d46ff451c0a0" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.state`

            State records numeric state of the request task. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 7, 10. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-subcategory-179d7aca0b77" title="Subcategory" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.subcategory`

            Subcategory records subcategory of the request. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned subcategory value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `subcategory` label when comparing subcategory.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-class-name-611d23fe6153" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_class_name`

            Sys Class Name records table class name for the record. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-created-by-9afe6a883eee" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_created_by`

            Sys Created By records user who created the record. It is needed to attribute this Service Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Service Requests row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-created-on-b1572c9951af" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_created_on`

            Sys Created On records record creation timestamp (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-domain-235985e93085" title="Sys Domain" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_domain`

            Sys Domain records domain of the record (`sys_id` reference). It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-domain-path-5ad3791d683e" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_domain_path`

            Sys Domain Path records domain path of the record. It is needed to compare the returned sys domain path for individual Service Requests rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Sc Request row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-id-352d39466479" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_id`

            Sys ID records unique system identifier for the request record. It is needed to distinguish repeated deliveries of the same Service Requests row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Service Requests and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-mod-count-28080680eda9" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Sc Request record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Sc Request record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is a ServiceNow-reported count at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-tags-9776edd7864d" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-updated-by-1293ac195e40" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_updated_by`

            Sys Updated By records user who last updated the record. It is needed to attribute this Service Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Service Requests row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-sys-updated-on-e30577863f52" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.sys_updated_on`

            Sys Updated On records record last update timestamp (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-universal-request-3521a8f15053" title="Universal Request" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.universal_request`

            Universal Request records reference to universal request record. It is needed to refer to the same `universal` across records without relying on display text.

            * **Enables:** match `universal_request` to `universal` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-upon-approval-a7782371e8d2" title="Upon Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.upon_approval`

            Upon Approval records action to take when the request is approved. Instance-customizable choice; known defaults include: proceed, `do_nothing`. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-upon-reject-13c8591ca69e" title="Upon Reject" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.upon_reject`

            Upon Reject records action to take when the request is rejected. Instance-customizable choice; known defaults include: cancel, goto. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-urgency-4f754439d6d9" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.urgency`

            Urgency records urgency level of the request. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Service Requests rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Service Requests rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-user-input-6109a119fd96" title="User Input" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.user_input`

            User Input records user input captured during request submission. It is needed to attribute this Service Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Service Requests row to the returned person or account and match the exact `user_input` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-variables-2883878f11ea" title="Variables" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.variables`

            Variables records serialized catalog variables associated with the request. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `variables` and associate them with the containing Service Requests record.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row; keys and availability follow this ServiceNow response and may vary by object type or ServiceNow configuration.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-watch-list-d3768dcdcbd7" title="Watch List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.watch_list`

            Watch List records list of users watching this request. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `watch_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is a list of ServiceNow user identifiers at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-work-end-f95e89ea0c41" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.work_end`

            Work End records actual work end date (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-work-notes-a92c3e0ab2bf" title="Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.work_notes`

            Work Notes records work notes (journal field, internal). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is comment or journal text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-work-notes-list-70e1800897bc" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.work_notes_list`

            Work Notes List records list of users notified for work notes. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `work_notes_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is comment or journal text at one Sc Request record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-request-work-start-3fddccdd1b07" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_request.work_start`

            Work Start records actual work start date (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Service Requests records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Request object returned for Service Requests; it is interpreted at one Sc Request record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sc-task-e3112ab84aaa" title="Catalog Tasks" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `sc_task`

        Catalog Tasks covers catalog tasks from ServiceNow. Catalog tasks are work items created to fulfill requested items from the service catalog, representing individual steps in the fulfillment process.

        * **Enables:** follow service work from the reported record through its returned assignee, status, priority, and timestamps during triage or fulfillment.
        * **Scope:** Extracts catalog tasks from ServiceNow. Catalog tasks are work items created to fulfill requested items from the service catalog, representing individual steps in the fulfillment process; the connector reads `/api/now/table/sc_task` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sc-task-active-020412e81584" title="Active" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.active`

            Active records whether the catalog task is currently active. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned active value.

            * **Enables:** select Catalog Tasks rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-activity-due-dc3b64fa1c9f" title="Activity Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.activity_due`

            Activity Due records date/time when the next SLA activity is due. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `activity_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-additional-assignee-list-66797964c302" title="Additional Assignee List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.additional_assignee_list`

            Additional Assignee List records comma-separated list of additional assignee user `sys_ids`. It is needed to refer to the same additional assignee list across records without relying on display text.

            * **Enables:** match `additional_assignee_list` to additional assignee list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-approval-5485b2760fe7" title="Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.approval`

            Approval records approval status of the catalog task. Instance-customizable choice; known defaults include: not requested, requested, approved, rejected, cancelled. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned approval value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `approval` label when comparing approval.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-approval-history-fcc08607c231" title="Approval History" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.approval_history`

            Approval History records history of approval actions on this task. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned approval history value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `approval_history` label when comparing approval history.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-approval-set-8d7fbbb3687a" title="Approval Set" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.approval_set`

            Approval Set records date/time when the approval status was last set. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `approval_set`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-assigned-to-17bae4bc8067" title="Assigned To" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.assigned_to`

            Assigned To records reference (`sys_id`) to the user assigned to this task. It is needed to refer to the same assigned to across records without relying on display text.

            * **Enables:** match `assigned_to` to assigned to references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-assignment-group-7baeadd583f2" title="Assignment Group" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.assignment_group`

            Assignment Group records reference (`sys_id`) to the group assigned to this task. It is needed to refer to the same assignment group across records without relying on display text.

            * **Enables:** match `assignment_group` to assignment group references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-business-duration-9e83a78c8cdc" title="Business Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.business_duration`

            Business Duration records elapsed business time for the task (duration field). It is needed to measure the exact duration reported for one Sc Task record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `business_duration` per Sc Task record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-business-service-23fd062cb854" title="Business Service" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.business_service`

            Business Service records reference (`sys_id`) to the business service related to this task. It is needed to refer to the same business service across records without relying on display text.

            * **Enables:** match `business_service` to business service references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-calendar-duration-0f622226e438" title="Calendar Duration" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.calendar_duration`

            Calendar Duration records elapsed calendar time for the task (duration field). It is needed to measure the exact duration reported for one Sc Task record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `calendar_duration` per Sc Task record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-cat-item-e1be5e3f2927" title="Cat Item" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.cat_item`

            Cat Item records reference (`sys_id`) to the catalog item associated with this task. It is needed to refer to the same cat item across records without relying on display text.

            * **Enables:** match `cat_item` to cat item references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-close-notes-a6d800dc8125" title="Close Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.close_notes`

            Close Notes records notes entered when the task was closed. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `close_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is comment or journal text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-closed-at-c415bcb41f12" title="Closed At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.closed_at`

            Closed At records date/time when the task was closed (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `closed_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-closed-by-b8d7bb8a45fe" title="Closed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.closed_by`

            Closed By records reference (`sys_id`) to the user who closed this task. It is needed to refer to the same closed by across records without relying on display text.

            * **Enables:** match `closed_by` to closed by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-cmdb-ci-379ca78d12af" title="Cmdb Ci" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.cmdb_ci`

            Cmdb Ci records reference (`sys_id`) to the configuration item related to this task. It is needed to refer to the same cmdb ci across records without relying on display text.

            * **Enables:** match `cmdb_ci` to cmdb ci references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-comments-b40f947d0057" title="Comments" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.comments`

            Comments records additional comments on the task (customer-visible journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is comment or journal text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-comments-and-work-notes-4ad8bd335769" title="Comments And Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.comments_and_work_notes`

            Comments And Work Notes records combined comments and work notes. It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `comments_and_work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is comment or journal text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-company-0bf3b0a15f73" title="Company" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.company`

            Company records reference (`sys_id`) to the company associated with this task. It is needed to refer to the same company across records without relying on display text.

            * **Enables:** match `company` to company references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-contact-type-431953594d3b" title="Contact Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.contact_type`

            Contact Type records how the task was initiated (e.g., phone, email, self-service). It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned contact type value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `contact_type` label when comparing contact type.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-correlation-display-d6e860792000" title="Correlation Display" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.correlation_display`

            Correlation Display records display value for the correlation identifier. It is needed to refer to the same correlation display across records without relying on display text.

            * **Enables:** match `correlation_display` to correlation display references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-correlation-id-282cfb84b379" title="Correlation ID" icon="link" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.correlation_id`

            Correlation ID records correlation identifier for linking related records across systems. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-description-563afc42e975" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.description`

            Description records detailed description of the catalog task. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is description text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-due-date-ee5981d6f019" title="Due Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.due_date`

            Due Date records due date for the catalog task (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `due_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Temporal.Date` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-escalation-aa183afab44e" title="Escalation" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.escalation`

            Escalation records current escalation level of the task. Instance-customizable choice; known defaults include: 0, 1, 2, 3. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned escalation value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `escalation` label when comparing escalation.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-expected-start-5da36f9b1f07" title="Expected Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.expected_start`

            Expected Start records expected start date/time for the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `expected_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-follow-up-96952867c861" title="Follow Up" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.follow_up`

            Follow Up records follow-up date/time for the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `follow_up`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-group-list-18825c204724" title="Group List" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.group_list`

            Group List records comma-separated list of group `sys_ids` that have visibility. It is needed to preserve the explicit ServiceNow group references attached to this row.

            * **Enables:** split the references in `group_list` and match each returned group identifier to the corresponding ServiceNow group record when available.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is a list of ServiceNow group identifiers at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-impact-8953782ed68e" title="Impact" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.impact`

            Impact records impact level of the catalog task. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned impact value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `impact` label when comparing impact.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-knowledge-596589eeed8c" title="Knowledge" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.knowledge`

            Knowledge records whether a knowledge article was used or flagged for creation. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned knowledge value.

            * **Enables:** select Catalog Tasks rows where `knowledge` is true or false when comparing the condition described by Knowledge.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-location-82f38de7d0c9" title="Location" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.location`

            Location records reference (`sys_id`) to the location associated with this task. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Sc Task row.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-made-sla-33bbfc2b485b" title="Made Sla" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.made_sla`

            Made Sla records whether the task met its SLA requirements. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned made sla value.

            * **Enables:** select Catalog Tasks rows where `made_sla` is true or false when comparing the condition described by Made Sla.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-number-bd0587f51fde" title="Number" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.number`

            Number records display number for the catalog task (e.g., SCTASK0001234). It is needed to refer to the same catalog tasks across records without relying on display text.

            * **Enables:** match `number` to catalog tasks references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-opened-at-fc7d254b5747" title="Opened At" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.opened_at`

            Opened At records date/time when the task was opened (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `opened_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-opened-by-fa84797feb1b" title="Opened By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.opened_by`

            Opened By records reference (`sys_id`) to the user who opened this task. It is needed to refer to the same opened by across records without relying on display text.

            * **Enables:** match `opened_by` to opened by references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-order-90710b26249a" title="Order" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.order`

            Order records execution order of the catalog task within the request item fulfillment. It is needed to place this Catalog Tasks row in the order explicitly reported by ServiceNow.

            * **Enables:** order Catalog Tasks rows by the explicit `order` sequence value returned for each Sc Task record.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-parent-47a939d73582" title="Parent" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.parent`

            Parent records reference (`sys_id`) to the parent task. It is needed to refer to the same parent across records without relying on display text.

            * **Enables:** match `parent` to parent references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-priority-dd3d1c9d8e44" title="Priority" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.priority`

            Priority records priority level of the catalog task. Instance-customizable choice; known defaults include: 1, 2, 3, 4, 5. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned priority value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `priority` label when comparing priority.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-reassignment-count-2558f8392b8f" title="Reassignment Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.reassignment_count`

            Reassignment Count records number of times the task has been reassigned. It is needed to measure the ServiceNow-reported number of times the task has been reassigned at one Sc Task record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the task has been reassigned in `reassignment_count` at one Sc Task record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is a ServiceNow-reported count at one Sc Task record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-request-22435afd5720" title="Request" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.request`

            Request records reference (`sys_id`) to the parent service catalog request (`sc_request`). It is needed to refer to the same request across records without relying on display text.

            * **Enables:** match `request` to request references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-request-item-3d26922efe08" title="Request Item" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.request_item`

            Request Item records reference (`sys_id`) to the parent requested item (`sc_req_item`). It is needed to refer to the same request item across records without relying on display text.

            * **Enables:** match `request_item` to request item references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-route-reason-a1647655a361" title="Route Reason" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.route_reason`

            Route Reason records reason code for the routing of the task. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned route reason value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `route_reason` label when comparing route reason.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Generic.Int64` scalar; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sc-catalog-9d89435b9b68" title="Sc Catalog" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sc_catalog`

            Sc Catalog records reference (`sys_id`) to the service catalog. It is needed to refer to the same sc catalog across records without relying on display text.

            * **Enables:** match `sc_catalog` to sc catalog references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-short-description-3a23b4dcef04" title="Short Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.short_description`

            Short Description records brief description of the catalog task. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `short_description` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is description text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sla-due-62bf49bce138" title="Sla Due" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sla_due`

            Sla Due records SLA due date/time for the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `sla_due`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-state-3a60163dba6f" title="State" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.state`

            State records current state of the catalog task. Instance-customizable choice; known defaults include: -5, 1, 2, 3, 4, 7. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned state value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `state` label when comparing state.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-class-name-574a7e0249f7" title="Sys Class Name" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_class_name`

            Sys Class Name records table class name for the record (e.g., `sc_task`). It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-created-by-dd9443926928" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Catalog Tasks row to the returned person, account, or organization reference.

            * **Enables:** attribute the Catalog Tasks row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-created-on-d059e2ec5302" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_created_on`

            Sys Created On records date/time when the record was created (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-domain-bb729bfa517b" title="Sys Domain" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_domain`

            Sys Domain records domain to which this record belongs (for domain-separated instances). It is needed to compare the returned sys domain for individual Catalog Tasks rows and select rows with a specific `sys_domain` value.

            * **Enables:** trace the sys domain relationship returned in `sys_domain` from the Sc Task row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-domain-path-64ffa45aa622" title="Sys Domain Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_domain_path`

            Sys Domain Path records domain path for the record. It is needed to compare the returned sys domain path for individual Catalog Tasks rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Sc Task row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-id-cd39629d1c76" title="Sys ID" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_id`

            Sys ID records unique system identifier for the catalog task. It is needed to distinguish repeated deliveries of the same Catalog Tasks row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Catalog Tasks and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-mod-count-6704ec66c19c" title="Sys Mod Count" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Sc Task record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Sc Task record per row.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is a ServiceNow-reported count at one Sc Task record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-tags-2132a7bd5b95" title="Sys Tags" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-updated-by-afd6350ac2d0" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Catalog Tasks row to the returned person, account, or organization reference.

            * **Enables:** attribute the Catalog Tasks row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-sys-updated-on-37f704a52e62" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.sys_updated_on`

            Sys Updated On records date/time when the record was last updated (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-time-worked-42ed3b5a9a57" title="Time Worked" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.time_worked`

            Time Worked records total time worked on the task (duration field). It is needed to measure the exact duration reported for one Sc Task record using the ServiceNow duration encoding described by the field.

            * **Enables:** measure and compare `time_worked` per Sc Task record in the source duration encoding described by this field.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; its unit or granularity is the source duration encoding described by this field.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-universal-request-e0d5d7b92f54" title="Universal Request" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.universal_request`

            Universal Request records reference (`sys_id`) to the universal request if applicable. It is needed to refer to the same universal request across records without relying on display text.

            * **Enables:** match `universal_request` to universal request references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-upon-approval-6b20b2ffd8a5" title="Upon Approval" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.upon_approval`

            Upon Approval records action to take when the task is approved. Instance-customizable choice; known defaults include: proceed, goto. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned upon approval value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `upon_approval` label when comparing upon approval.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-upon-reject-28926291589a" title="Upon Reject" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.upon_reject`

            Upon Reject records action to take when the task is rejected. Instance-customizable choice; known defaults include: cancel, goto. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned upon reject value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `upon_reject` label when comparing upon reject.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-urgency-b726e6a16941" title="Urgency" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.urgency`

            Urgency records urgency level of the catalog task. Instance-customizable choice; known defaults include: 1, 2, 3. It is needed to distinguish Catalog Tasks rows by the exact ServiceNow-returned urgency value.

            * **Enables:** separate Catalog Tasks rows by the exact ServiceNow-returned `urgency` label when comparing urgency.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the allowed labels can differ by ServiceNow instance; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-variables-409fb53ff446" title="Variables" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.variables`

            Variables records catalog item variables and their values associated with this task. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `variables` and associate them with the containing Catalog Tasks record.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this ServiceNow response and may vary by object type or ServiceNow configuration.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-watch-list-688c30f434b4" title="Watch List" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.watch_list`

            Watch List records comma-separated list of user `sys_ids` watching this task. It is needed to preserve the explicit ServiceNow user references attached to this row.

            * **Enables:** split the references in `watch_list` and match each returned user identifier to the corresponding ServiceNow user record when available.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is a list of ServiceNow user identifiers at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-work-end-3fc8f4ff85fa" title="Work End" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.work_end`

            Work End records date/time when work ended on the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `work_end`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-work-notes-722baa289902" title="Work Notes" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.work_notes`

            Work Notes records work notes added to the task (journal field). It is needed to inspect the exact comment or journal text included with this record.

            * **Enables:** inspect the comment or journal text returned in `work_notes` and attribute it to the same record's record number, assignee, state, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is comment or journal text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-work-notes-list-6a59afb6d61b" title="Work Notes List" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.work_notes_list`

            Work Notes List records comma-separated list of work notes journal entry `sys_ids`. It is needed to refer to the same work notes list across records without relying on display text.

            * **Enables:** match `work_notes_list` to work notes list references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is comment or journal text at one Sc Task record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sc-task-work-start-812e65556bac" title="Work Start" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sc_task.work_start`

            Work Start records date/time when work actually started on the task. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalog Tasks records by `work_start`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sc Task object returned for Catalog Tasks; it is interpreted at one Sc Task record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sys-audit-57cdb3a74b00" title="Audit Changes" icon="shield-check" iconType="sharp-duotone-solid">
        Developer identifier: `sys_audit`

        Audit Changes covers audit log records from the `sys_audit` table. Each record captures a single field-level change on an audited record, providing a detailed who-changed-what-when trail across the platform.

        * **Enables:** reconstruct an Audit Changes timeline and correlate each returned actor, target, action, and timestamp during an investigation.
        * **Scope:** Extracts audit log records from the `sys_audit` table. Each record captures a single field-level change on an audited record, providing a detailed who-changed-what-when trail across the platform; the connector reads `/api/now/table/sys_audit` as an event stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sys-audit-documentkey-8c086e7a4ce4" title="Documentkey" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.documentkey`

            Documentkey records `sys_id` of the record that was changed. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `documentkey` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is an identifier, not a measured quantity; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-fieldname-00e1c21acf21" title="Fieldname" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.fieldname`

            Fieldname records name of the field that was changed. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `fieldname` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-newvalue-e4e6ae988e1f" title="Newvalue" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.newvalue`

            Newvalue records new value of the field after the change. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `newvalue` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-oldvalue-24d714159459" title="Oldvalue" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.oldvalue`

            Oldvalue records previous value of the field before the change. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `oldvalue` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-reason-7da79ec8313b" title="Reason" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.reason`

            Reason records reason for the change if provided. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Audit Changes investigation evidence with the exact `reason` result, permission, or ServiceNow classification being examined.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-record-checkpoint-22cb8d5c693f" title="Record Checkpoint" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.record_checkpoint`

            Record Checkpoint records checkpoint for the audit record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `record_checkpoint` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-sys-created-by-c010c69465b6" title="Sys Created By" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.sys_created_by`

            Sys Created By records system user who created the audit record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_created_by` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-sys-created-on-588c23f87308" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.sys_created_on`

            Sys Created On records date/time when the audit record was created. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_created_on` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; the connector also declares it for record ordering; the schema assigns the `event_time` semantic role; the schema uses the `Temporal.DateTime` scalar; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-sys-id-76395858ee67" title="Sys ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.sys_id`

            Sys ID records unique system identifier for the audit record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_id` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-tablename-025e522ee982" title="Tablename" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.tablename`

            Tablename records table name of the record that was changed. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `tablename` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-user-9adc15a87345" title="User" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit.user`

            User records user who made the change. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `user` with the returned actor, target, action, request, or session identifiers on the same Audit Changes evidence record.
            * **Interpretation:** ServiceNow reports this value on the Servicenow Sys Audit object returned for Audit Changes; it is interpreted at one Servicenow Sys Audit record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sys-audit-delete-43530407cd83" title="Deleted Record Audit" icon="shield-check" iconType="sharp-duotone-solid">
        Developer identifier: `sys_audit_delete`

        Deleted Record Audit covers deleted record audit entries from ServiceNow. Tracks records that have been deleted from audited tables, enabling detection of deletions for incremental sync.

        * **Enables:** reconstruct a Deleted Record Audit timeline and correlate each returned actor, target, action, and timestamp during an investigation.
        * **Scope:** Extracts deleted record audit entries from ServiceNow. Tracks records that have been deleted from audited tables, enabling detection of deletions for incremental sync; the connector reads `/api/now/table/sys_audit_delete` as an event stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-display-value-3a00b70226d4" title="Display Value" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.display_value`

            Display Value records the display value (human-readable label) of the deleted record at the time of deletion. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `display_value` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-documentkey-235f5fe25e62" title="Documentkey" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.documentkey`

            Documentkey records the `sys_id` of the record that was deleted from the source table. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `documentkey` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is an identifier, not a measured quantity; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-record-checkpoint-ec815f8e0293" title="Record Checkpoint" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.record_checkpoint`

            Record Checkpoint records checkpoint value associated with the deleted record, used for tracking replication or synchronization state. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `record_checkpoint` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-record-class-924274dfabd0" title="Record Class" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.record_class`

            Record Class records the class or type of the deleted record, particularly relevant for tables with class hierarchies (e.g., task extensions). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Deleted Record Audit investigation evidence with the exact `record_class` result, permission, or ServiceNow classification being examined.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-created-by-e3cb000b3561" title="Sys Created By" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_created_by`

            Sys Created By records the username of the user who performed the deletion. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_created_by` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-created-on-bf7a840ba1ca" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_created_on`

            Sys Created On records date and time when the deletion was recorded in the audit table. Format: YYYY-MM-DD HH:mm:ss. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_created_on` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; the schema assigns the `event_time` semantic role; the schema uses the `Temporal.DateTime` scalar; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-id-d1ccabd4995a" title="Sys ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_id`

            Sys ID records unique system identifier for the audit delete record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_id` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-mod-count-df977a501538" title="Sys Mod Count" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_mod_count`

            Sys Mod Count records number of times this audit delete record has been modified. Typically 0 for audit entries. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_mod_count` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is a ServiceNow-reported count at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-tags-af247831c90e" title="Sys Tags" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_tags`

            Sys Tags records tags associated with this audit delete record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Deleted Record Audit investigation evidence with the exact `sys_tags` result, permission, or ServiceNow classification being examined.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-updated-by-0d5ec9f1c548" title="Sys Updated By" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_updated_by`

            Sys Updated By records the username of the user who last updated this audit delete record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_updated_by` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-sys-updated-on-f35f014d521a" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.sys_updated_on`

            Sys Updated On records date and time when this audit delete record was last updated. Format: YYYY-MM-DD HH:mm:ss. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `sys_updated_on` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-audit-delete-tablename-23f04aa1d5c0" title="Tablename" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_audit_delete.tablename`

            Tablename records the name of the table from which the record was deleted (e.g., incident, `sys_user`, `cmdb_ci`). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `tablename` with the returned actor, target, action, request, or session identifiers on the same Deleted Record Audit evidence record.
            * **Interpretation:** ServiceNow reports this value on the Sys Audit Delete object returned for Deleted Record Audit; it is interpreted at one Sys Audit Delete record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sys-user-661a84ac5985" title="Users" icon="people-group" iconType="sharp-duotone-solid">
        Developer identifier: `sys_user`

        Users covers user records from ServiceNow `sys_user` table, including name, email, roles, department, manager, active status, and system metadata.

        * **Enables:** map the ServiceNow accounts and memberships represented by Users records and trace a returned access assignment to its account or group.
        * **Scope:** Extracts all user records from ServiceNow `sys_user` table, including name, email, roles, department, manager, active status, and system metadata; the connector reads `/api/now/table/sys_user` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sys-user-accumulated-roles-7577798ed1a2" title="Accumulated Roles" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.accumulated_roles`

            Accumulated Roles records all roles accumulated including inherited roles. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `accumulated_roles` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-active-640dfce8d6ea" title="Active" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.active`

            Active records whether the user account is active. It is needed to distinguish Users rows by the exact ServiceNow-returned active value.

            * **Enables:** select Users rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-avatar-bb956935c077" title="Avatar" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.avatar`

            Avatar records avatar image reference. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact ServiceNow resource referenced by `avatar` while retaining the containing Users record as provenance.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is link at one Sys User record per row; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-building-89df35bfea75" title="Building" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.building`

            Building records reference to building record (`sys_id`). It is needed to refer to the same `building` across records without relying on display text.

            * **Enables:** match `building` to `building` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-calendar-integration-ee717d5bdf9f" title="Calendar Integration" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.calendar_integration`

            Calendar Integration records calendar integration setting. It is needed to compare the exact calendar integration configuration returned for this Sys User record.

            * **Enables:** compare the exact `calendar_integration` configuration returned for each Sys User record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-city-3a2961728240" title="City" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.city`

            City records city from the user's address. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `city` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-company-d0b53a08a580" title="Company" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.company`

            Company records reference to company record (`sys_id`). It is needed to refer to the same `company` across records without relying on display text.

            * **Enables:** match `company` to `company` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-correlation-id-2df15e2fcc4c" title="Correlation ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.correlation_id`

            Correlation ID records correlation ID used for external system mapping. It is needed to refer to the same correlation across records without relying on display text.

            * **Enables:** match `correlation_id` to correlation references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-cost-center-22a39cea6af7" title="Cost Center" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.cost_center`

            Cost Center records reference to cost center record (`sys_id`). It is needed to refer to the same `cost` across records without relying on display text.

            * **Enables:** match `cost_center` to `cost` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-country-a822b037b3b6" title="Country" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.country`

            Country records country code or name. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `country` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-date-format-04190e4caa87" title="Date Format" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.date_format`

            Date Format records user's preferred date format. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Users records by `date_format`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-default-perspective-ad8e784365f2" title="Default Perspective" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.default_perspective`

            Default Perspective records default UI perspective for the user. It is needed to distinguish Users rows by the exact ServiceNow-returned default perspective value.

            * **Enables:** separate Users rows by the exact ServiceNow-returned `default_perspective` label when comparing default perspective.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-department-e2f625589cc0" title="Department" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.department`

            Department records reference to department record (`sys_id`). It is needed to refer to the same `department` across records without relying on display text.

            * **Enables:** match `department` to `department` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-edu-status-5ad9b1090a9f" title="Edu Status" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.edu_status`

            Edu Status records education status of the user. It is needed to distinguish Users rows by the exact ServiceNow-returned edu status value.

            * **Enables:** separate Users rows by the exact ServiceNow-returned `edu_status` label when comparing edu status.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-email-26944bb9e960" title="Email" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.email`

            Email records user's primary email address. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `email` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-employee-number-1967bc6ec9bc" title="Employee Number" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.employee_number`

            Employee Number records employee number. It is needed to refer to the same employee number across records without relying on display text.

            * **Enables:** match `employee_number` to employee number references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-enable-multifactor-authn-f26831e90772" title="Enable Multifactor Authn" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.enable_multifactor_authn`

            Enable Multifactor Authn records whether multi-factor authentication is enabled for the user. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Users rows with the exact `enable_multifactor_authn` access-related value being investigated.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-failed-attempts-5bb1dad953b0" title="Failed Attempts" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.failed_attempts`

            Failed Attempts records number of consecutive failed login attempts. It is needed to measure the ServiceNow-reported number of consecutive failed login attempts at one Sys User record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of consecutive failed login attempts in `failed_attempts` at one Sys User record per row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is a ServiceNow-reported count at one Sys User record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-first-name-ca5d453dcf22" title="First Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.first_name`

            First Name records user's first name. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `first_name` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-gender-7951fc82bb66" title="Gender" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.gender`

            Gender records user's gender. It is needed to distinguish Users rows by the exact ServiceNow-returned gender value.

            * **Enables:** separate Users rows by the exact ServiceNow-returned `gender` label when comparing gender.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-hashed-user-id-a9188dcbb535" title="Hashed User ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.hashed_user_id`

            Hashed User ID records hashed version of the user identifier. It is needed to refer to the same hashed user across records without relying on display text.

            * **Enables:** match `hashed_user_id` to hashed user references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-home-phone-7a8a6e8ce83a" title="Home Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.home_phone`

            Home Phone records user's home phone number. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `home_phone` to the same Sys User record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-internal-integration-user-a2833c9727bc" title="Internal Integration User" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.internal_integration_user`

            Internal Integration User records whether the user is an internal integration user. It is needed to distinguish Users rows by the exact ServiceNow-returned internal integration user value.

            * **Enables:** select Users rows where `internal_integration_user` is true or false when comparing the condition described by Internal Integration User.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-introduction-c93f75fb0364" title="Introduction" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.introduction`

            Introduction records user introduction or bio text. It is needed to inspect the exact descriptive text included with this record.

            * **Enables:** inspect the descriptive text returned in `introduction` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is descriptive text at one Sys User record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-last-login-16cd708e888e" title="Last Login" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.last_login`

            Last Login records timestamp of the user's last login. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Users records by `last_login`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-last-login-device-1f5ea1b94291" title="Last Login Device" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.last_login_device`

            Last Login Device records device used for the user's last login. It is needed to preserve the ServiceNow-reported client device or software context for the same record.

            * **Enables:** correlate `last_login_device` with the actor, request, or session on the same ServiceNow event without treating it as proof of physical presence.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the value is client device or software context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-last-login-time-1801bfa93419" title="Last Login Time" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.last_login_time`

            Last Login Time records timestamp of the user's last login time. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `last_login_time` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the schema uses the `Temporal.DateTime` scalar; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-last-name-574897ff3de5" title="Last Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.last_name`

            Last Name records user's last name. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `last_name` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-last-password-bbbae68a0eff" title="Last Password" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.last_password`

            Last Password records timestamp or hash of the user's last password change. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `last_password` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-ldap-server-1cbd48cabc23" title="LDAP Server" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.ldap_server`

            LDAP Server records reference to LDAP server used for authentication. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `ldap_server` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-location-3488d099d86f" title="Location" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.location`

            Location records reference to location record (`sys_id`). It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** match `location` to the referenced ServiceNow location or device record carrying the same identifier while retaining the containing Sys User row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-locked-out-5f0df62feffd" title="Locked Out" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.locked_out`

            Locked Out records whether the user account is locked out. It is needed to distinguish Users rows by the exact ServiceNow-returned locked out value.

            * **Enables:** select Users rows where `locked_out` is true or false when comparing the condition described by Locked Out.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-manager-0d6aae5f3e2b" title="Manager" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.manager`

            Manager records reference to manager user record (`sys_id`). It is needed to refer to the same `manager` across records without relying on display text.

            * **Enables:** match `manager` to `manager` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-middle-name-9ec044a0fcc1" title="Middle Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.middle_name`

            Middle Name records user's middle name. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `middle_name` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-mobile-phone-bd6813834db3" title="Mobile Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.mobile_phone`

            Mobile Phone records user's mobile phone number. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `mobile_phone` to the same Sys User record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-name-0e5a7e4ad9d2" title="Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.name`

            Name records full display name of the user. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `name` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-notification-7f65fc4b5796" title="Notification" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.notification`

            Notification records notification preference setting. It is needed to compare the exact notification configuration returned for this Sys User record.

            * **Enables:** compare the exact `notification` configuration returned for each Sys User record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-password-needs-reset-31a65fc02964" title="Password Needs Reset" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.password_needs_reset`

            Password Needs Reset records whether the user must reset their password on next login. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Users rows with the exact `password_needs_reset` access-related value being investigated.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-phone-aace62bb70c0" title="Phone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.phone`

            Phone records user's phone number. It is needed to preserve the exact ServiceNow-reported contact number for the person, company, or location represented by this row.

            * **Enables:** match the exact contact number in `phone` to the same Sys User record without treating it as an account identifier.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-photo-1e055a2e2ad9" title="Photo" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.photo`

            Photo records attachment `sys_id` or path for the user's photo. It is needed to refer to the same photo across records without relying on display text.

            * **Enables:** match `photo` to photo references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-preferred-language-5fd5a332e3f4" title="Preferred Language" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.preferred_language`

            Preferred Language records user's preferred language setting. It is needed to compare the exact preferred language configuration returned for this Sys User record.

            * **Enables:** compare the exact `preferred_language` configuration returned for each Sys User record and select records with the configuration under review.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-roles-50e1aee3ab0f" title="Roles" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.roles`

            Roles records comma-separated list of assigned roles. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `roles` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-schedule-cc5c8ddb2099" title="Schedule" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.schedule`

            Schedule records reference to the user's schedule record (`sys_id`). It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `schedule` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-source-022c8d3b7301" title="Source" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.source`

            Source records source system or integration that created the user record. It is needed to distinguish Users rows by the exact ServiceNow-returned source value.

            * **Enables:** separate Users rows by the exact ServiceNow-returned `source` label when comparing source.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-state-5af200aafa1b" title="State" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.state`

            State records state or province from the user's address. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `state` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-street-3e7a365b0efc" title="Street" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.street`

            Street records street address. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `street` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-class-name-238e24d2aee9" title="Sys Class Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_class_name`

            Sys Class Name records table class name for the record. It is needed to distinguish Users rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate Users rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-created-by-43fa63316aa6" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_created_by`

            Sys Created By records username of the user who created the record. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-created-on-dc1ce4eb57c6" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_created_on`

            Sys Created On records timestamp when the record was created (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Users records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-domain-e5d88da6158d" title="Sys Domain" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_domain`

            Sys Domain records domain to which the record belongs (`sys_id`). It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-domain-path-ab3bb85cb6ca" title="Sys Domain Path" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_domain_path`

            Sys Domain Path records domain path for domain-separated instances. It is needed to compare the returned sys domain path for individual Users rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Sys User row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-id-fd8a0fa8455f" title="Sys ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_id`

            Sys ID records unique system identifier (GUID) for the user record. It is needed to distinguish repeated deliveries of the same Users row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Users and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-mod-count-6e7387e9ab8a" title="Sys Mod Count" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_mod_count`

            Sys Mod Count records number of times the record has been modified. It is needed to measure the ServiceNow-reported number of times the record has been modified at one Sys User record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified in `sys_mod_count` at one Sys User record per row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is a ServiceNow-reported count at one Sys User record per row; the schema uses the `Generic.Int64` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-tags-ff962e55e12d" title="Sys Tags" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_tags`

            Sys Tags records tags associated with the record. It is needed to distinguish Users rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Users rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-updated-by-9083c2b55c2c" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_updated_by`

            Sys Updated By records username of the user who last updated the record. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-sys-updated-on-8ca0cf8968ac" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.sys_updated_on`

            Sys Updated On records timestamp when the record was last updated (format: yyyy-MM-dd HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Users records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-time-format-33e6f2abafc4" title="Time Format" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.time_format`

            Time Format records user's preferred time format. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Users records by `time_format`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-time-zone-b58343bbfcef" title="Time Zone" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.time_zone`

            Time Zone records user's configured time zone. It is needed to preserve the ServiceNow-reported timezone or locale setting for the same record.

            * **Enables:** compare the ServiceNow-reported timezone or locale setting in `time_zone` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the schema uses the `Temporal.TimeZone` scalar; the value is timezone or locale setting; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-title-3806a656f2fb" title="Title" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.title`

            Title records job title. It is needed to preserve the business or job title reported for the person represented by this row.

            * **Enables:** select Users rows by the exact business or job title in `title` without treating the title as an authorization role.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-user-name-0613ebca618b" title="User Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.user_name`

            User Name records login username. It is needed to attribute this Users row to the returned person, account, or organization reference.

            * **Enables:** attribute the Users row to the returned person or account and match the exact `user_name` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-user-password-bdb4ec2d0d9b" title="User Password" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.user_password`

            User Password records hashed user password (write-only in practice). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `user_password` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-vip-5e85438f66f0" title="Vip" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.vip`

            Vip records whether the user is flagged as a VIP. It is needed to distinguish Users rows by the exact ServiceNow-returned vip value.

            * **Enables:** select Users rows where `vip` is true or false when comparing the condition described by Vip.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-web-service-access-only-4ed41bde9d12" title="Web Service Access Only" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.web_service_access_only`

            Web Service Access Only records whether the user can only access ServiceNow via web services. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Users rows with the exact `web_service_access_only` access-related value being investigated.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-zip-a38af920c42c" title="Zip" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user.zip`

            Zip records postal or ZIP code. It is needed to preserve the ServiceNow-reported configured or derived address and place context for the same record.

            * **Enables:** compare the ServiceNow-reported configured or derived address and place context in `zip` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** ServiceNow reports this value on the Sys User object returned for Users; it is interpreted at one Sys User record per row; the value is configured or derived address and place context; this ServiceNow-reported or configured context does not establish residency or verified physical presence.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sys-user-grmember-5758a3d967e5" title="Group Memberships" icon="people-group" iconType="sharp-duotone-solid">
        Developer identifier: `sys_user_grmember`

        Group Memberships covers user-to-group membership records from ServiceNow `sys_user_grmember` table, linking users to their groups.

        * **Enables:** map the ServiceNow accounts and memberships represented by Group Memberships records and trace a returned access assignment to its account or group.
        * **Scope:** Extracts user-to-group membership records from ServiceNow `sys_user_grmember` table, linking users to their groups; the connector reads `/api/now/table/sys_user_grmember` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-group-0fffd2c4ebba" title="Group" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.group`

            Group records reference to the group record (`sys_id` of the `sys_user_group`). Identifies which group the user belongs to. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `group` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-created-by-a89d7ef8b745" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_created_by`

            Sys Created By records username of the user or system process that created this membership record. It is needed to attribute this Group Memberships row to the returned person, account, or organization reference.

            * **Enables:** attribute the Group Memberships row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is interpreted at one Sys User Grmember record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-created-on-90b55b82b281" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_created_on`

            Sys Created On records timestamp when the membership record was created, in ServiceNow datetime format (YYYY-MM-DD HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Group Memberships records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is interpreted at one Sys User Grmember record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-domain-85b471b307e1" title="Sys Domain" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_domain`

            Sys Domain records domain identifier for domain-separated instances. References the `sys_user_group` domain or global domain. It is needed to refer to the same sys domain across records without relying on display text.

            * **Enables:** match `sys_domain` to sys domain references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-domain-path-a5ac52e25e8b" title="Sys Domain Path" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_domain_path`

            Sys Domain Path records the hierarchical domain path for domain-separated instances (e.g., '/' for global). It is needed to compare the returned sys domain path for individual Group Memberships rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Sys User Grmember row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is interpreted at one Sys User Grmember record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-id-905ced5ee609" title="Sys ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_id`

            Sys ID records unique system identifier (GUID) for the group membership record. It is needed to distinguish repeated deliveries of the same Group Memberships row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for Group Memberships and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-mod-count-5d41474deabd" title="Sys Mod Count" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_mod_count`

            Sys Mod Count records number of times this record has been modified. Returned as a string from the API. It is needed to measure the ServiceNow-reported number of times this record has been modified. Returned as a string from the API at one Sys User Grmember record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times this record has been modified. Returned as a string from the API in `sys_mod_count` at one Sys User Grmember record per row.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is a ServiceNow-reported count at one Sys User Grmember record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-tags-a7cd10a469c0" title="Sys Tags" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_tags`

            Sys Tags records tags associated with this record, if any. It is needed to distinguish Group Memberships rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate Group Memberships rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is interpreted at one Sys User Grmember record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-updated-by-1ce9b58f27cb" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_updated_by`

            Sys Updated By records username of the user or system process that last updated this membership record. It is needed to attribute this Group Memberships row to the returned person, account, or organization reference.

            * **Enables:** attribute the Group Memberships row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is interpreted at one Sys User Grmember record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-sys-updated-on-b1a1f621c0b0" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.sys_updated_on`

            Sys Updated On records timestamp when the membership record was last updated, in ServiceNow datetime format (YYYY-MM-DD HH:mm:ss). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Group Memberships records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is interpreted at one Sys User Grmember record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-grmember-user-6c328378ceb4" title="User" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_grmember.user`

            User records reference to the user record (`sys_id` of the `sys_user`). Identifies which user belongs to the group. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `user` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Grmember object returned for Group Memberships; it is an identifier, not a measured quantity.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-servicenow-sys-user-group-c33fdf38b407" title="User Groups" icon="people-group" iconType="sharp-duotone-solid">
        Developer identifier: `sys_user_group`

        User Groups covers user group records from ServiceNow `sys_user_group` table, including group name, description, manager, parent group, and type.

        * **Enables:** map the ServiceNow accounts and memberships represented by User Groups records and trace a returned access assignment to its account or group.
        * **Scope:** Extracts all user group records from ServiceNow `sys_user_group` table, including group name, description, manager, parent group, and type; the connector reads `/api/now/table/sys_user_group` as a changelog stream in incremental mode. Record and field visibility follow the configured credential's ServiceNow table and field ACLs; restricted values are not returned. This stream has no deletion signal, so a missing row does not establish that the ServiceNow record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-servicenow-sys-user-group-active-16cfd0cb5785" title="Active" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.active`

            Active records whether the group is active. Returns 'true' or 'false' as string when `sysparm_display_value` is false. It is needed to distinguish User Groups rows by the exact ServiceNow-returned active value.

            * **Enables:** select User Groups rows where `active` is true or false when comparing the condition described by Active.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-cost-center-0a89920ac567" title="Cost Center" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.cost_center`

            Cost Center records `sys_id` reference to the cost center associated with this group. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `cost_center` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-default-assignee-b7229866d10a" title="Default Assignee" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.default_assignee`

            Default Assignee records `sys_id` reference to the default assignee user for tasks assigned to this group. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `default_assignee` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-description-e648a8871f20" title="Description" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.description`

            Description records detailed description of the group's purpose or function. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is description text at one Sys User Group record per row; this is only the content included in the ServiceNow response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-email-16996bd45189" title="Email" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.email`

            Email records email address associated with the group. It is needed to attribute this User Groups row to the returned person, account, or organization reference.

            * **Enables:** attribute the User Groups row to the returned person or account and match the exact `email` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-exclude-manager-393d5e9a8a6c" title="Exclude Manager" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.exclude_manager`

            Exclude Manager records whether to exclude the manager from group membership notifications. Returns 'true' or 'false' as string. It is needed to distinguish User Groups rows by the exact ServiceNow-returned exclude manager value.

            * **Enables:** select User Groups rows where `exclude_manager` is true or false when comparing the condition described by Exclude Manager.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-include-members-430690bbb1c9" title="Include Members" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.include_members`

            Include Members records whether to include group members in notifications. Returns 'true' or 'false' as string. It is needed to distinguish User Groups rows by the exact ServiceNow-returned include members value.

            * **Enables:** select User Groups rows where `include_members` is true or false when comparing the condition described by Include Members.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-manager-bf51d60a2d76" title="Manager" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.manager`

            Manager records `sys_id` reference to the user record of the group manager. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `manager` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-name-984fb0365d85" title="Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.name`

            Name records display name of the group. It is needed to compare the returned name for individual User Groups rows and select rows with a specific `name` value.

            * **Enables:** locate User Groups rows whose returned name exactly matches `name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-parent-d48c2a50a019" title="Parent" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.parent`

            Parent records `sys_id` reference to the parent group for hierarchical grouping. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `parent` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-roles-d8e6736744cd" title="Roles" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.roles`

            Roles records comma-separated list of role `sys_ids` assigned to this group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `roles` access value with the resource, account, or membership represented by the same User Groups row.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-source-99dad6972aef" title="Source" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.source`

            Source records source of the group record, e.g., import or manual creation. It is needed to distinguish User Groups rows by the exact ServiceNow-returned source value.

            * **Enables:** separate User Groups rows by the exact ServiceNow-returned `source` label when comparing source.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-class-name-bb8b69538658" title="Sys Class Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_class_name`

            Sys Class Name records the table class name, typically '`sys_user_group`'. It is needed to distinguish User Groups rows by the exact ServiceNow-returned sys class name value.

            * **Enables:** separate User Groups rows by the exact ServiceNow-returned `sys_class_name` label when comparing sys class name.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-created-by-aae0707a6555" title="Sys Created By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_created_by`

            Sys Created By records username of the user who created the group record. It is needed to attribute this User Groups row to the returned person, account, or organization reference.

            * **Enables:** attribute the User Groups row to the returned person or account and match the exact `sys_created_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-created-on-d6567f3bad3b" title="Sys Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_created_on`

            Sys Created On records timestamp when the group record was created, in format YYYY-MM-DD HH:mm:ss. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound User Groups records by `sys_created_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-domain-ad6e77676c16" title="Sys Domain" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_domain`

            Sys Domain records `sys_id` reference to the domain this group belongs to in domain-separated instances. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `sys_domain` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-domain-path-bcd400b27bd7" title="Sys Domain Path" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_domain_path`

            Sys Domain Path records domain path string for domain-separated instances. It is needed to compare the returned sys domain path for individual User Groups rows and select rows with a specific `sys_domain_path` value.

            * **Enables:** trace the sys domain path relationship returned in `sys_domain_path` from the Sys User Group row to its named ServiceNow context.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-id-d5646fd954f0" title="Sys ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_id`

            Sys ID records unique system identifier (GUID) for the group record. It is needed to distinguish repeated deliveries of the same User Groups row using the declared ingestion key.

            * **Enables:** use `sys_id` as the declared ingestion deduplication key for User Groups and match repeated rows carrying the same ServiceNow identifier.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-mod-count-b43452b81a32" title="Sys Mod Count" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_mod_count`

            Sys Mod Count records number of times the record has been modified, returned as a string. It is needed to measure the ServiceNow-reported number of times the record has been modified, returned as a string at one Sys User Group record per row.

            * **Enables:** measure and compare the ServiceNow-reported number of times the record has been modified, returned as a string in `sys_mod_count` at one Sys User Group record per row.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is a ServiceNow-reported count at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-name-802327fb50a0" title="Sys Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_name`

            Sys Name records system name field for the group record. It is needed to compare the returned sys name for individual User Groups rows and select rows with a specific `sys_name` value.

            * **Enables:** locate User Groups rows whose returned sys name exactly matches `sys_name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-policy-a4e9ba7d40cf" title="Sys Policy" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_policy`

            Sys Policy records read/write policy applied to this record. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `sys_policy` access value with the resource, account, or membership represented by the same User Groups row.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-scope-6f54d31300b9" title="Sys Scope" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_scope`

            Sys Scope records `sys_id` reference to the application scope that owns this group record. It is needed to refer to the same `the` across records without relying on display text.

            * **Enables:** match `sys_scope` to `the` references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-tags-4f644b6c8118" title="Sys Tags" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_tags`

            Sys Tags records tags associated with the group record. It is needed to distinguish User Groups rows by the exact ServiceNow-returned sys tags value.

            * **Enables:** separate User Groups rows by the exact ServiceNow-returned `sys_tags` label when comparing sys tags.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-update-name-cbc975e7715a" title="Sys Update Name" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_update_name`

            Sys Update Name records update name used for tracking the record in update sets. It is needed to compare the returned sys update name for individual User Groups rows and select rows with a specific `sys_update_name` value.

            * **Enables:** locate User Groups rows whose returned sys update name exactly matches `sys_update_name` and retain the ServiceNow identifier for any cross-record match.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-updated-by-c2d8c806809f" title="Sys Updated By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_updated_by`

            Sys Updated By records username of the user who last updated the group record. It is needed to attribute this User Groups row to the returned person, account, or organization reference.

            * **Enables:** attribute the User Groups row to the returned person or account and match the exact `sys_updated_by` value where it recurs in ServiceNow.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-sys-updated-on-3ab9c60982bb" title="Sys Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.sys_updated_on`

            Sys Updated On records timestamp when the group record was last updated, in format YYYY-MM-DD HH:mm:ss. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound User Groups records by `sys_updated_on`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is interpreted at one Sys User Group record per row; the connector also declares it for record ordering; the schema assigns the `metadata_timestamp` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-servicenow-sys-user-group-type-fe14233a6c14" title="Type" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `sys_user_group.type`

            Type records group type classification identifier. It is needed to refer to the same type across records without relying on display text.

            * **Enables:** match `type` to type references carrying the same ServiceNow-issued value in related ServiceNow records.
            * **Interpretation:** ServiceNow reports this value on the Sys User Group object returned for User Groups; it is an identifier, not a measured quantity; classification values are ServiceNow-returned labels rather than a universal taxonomy.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    ### OAuth 2.0 Client Credentials

    | Symptom                      | Likely cause                                                              |
    | ---------------------------- | ------------------------------------------------------------------------- |
    | Token exchange HTTP 401      | Wrong client id/secret, inactive app, or missing Application User binding |
    | Probe / table calls HTTP 403 | Missing role or table ACL on the application user                         |
    | Empty `sys_audit`            | ACL not granted; `snc_read_only` is not enough                            |
    | Unresolved `{instance}`      | Instance field missing from the Provider configuration                    |
  </Tab>
</Tabs>