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

# Databricks

> Databricks is a unified data lakehouse platform that provides data engineering, data science, machine learning, and analytics capabilities. It exposes a SQL Statement Execution REST API for querying data via SQL over HTTP, Unity Catalog APIs for metadata discovery, and workspace management APIs for compute, jobs, pipelines, identity, and audit operations.

Databricks is a unified data lakehouse platform that provides data engineering, data science, machine learning, and analytics capabilities. It exposes a SQL Statement Execution REST API for querying data via SQL over HTTP, Unity Catalog APIs for metadata discovery, and workspace management APIs for compute, jobs, pipelines, identity, and audit operations.

<Tabs>
  <Tab title="Overview">
    Connect Parable to Databricks using a **service principal** and the **OAuth 2.0 client credentials** flow. Parable uses the workspace REST APIs for metadata and identity taps, and the **SQL Statement Execution API** for user-activity taps (`audit_logs`, `query_history`) against Unity Catalog system tables.

    This integration uses **OAuth 2.0 Client Credentials** flow for server-to-server authentication.

    #### How It Works

    1. Parable sends **Client ID** and **Client Secret** to the token endpoint
    2. Databricks returns a short-lived **access token** (typically 1 hour)
    3. Use the access token in API requests
    4. When expired, request a new token (automatic in Parable)

    #### Token Request

    ```bash cURL theme={null}
    curl -X POST "https://&lt;workspace-host&gt;/oidc/v1/token" \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=client_credentials" \
      -d "client_id=YOUR_CLIENT_ID" \
      -d "client_secret=YOUR_CLIENT_SECRET"
    ```

    ```python Python theme={null}

    response = requests.post(
        "https://&lt;workspace-host&gt;/oidc/v1/token",
        data={
            "grant_type": "client_credentials",
            "client_id": "YOUR_CLIENT_ID",
            "client_secret": "YOUR_CLIENT_SECRET"
        }
    )

    access_token = response.json()["access_token"]
    print(f"Access Token: {access_token}")
    ```

    #### Using the Access Token

    ```http theme={null}
    Authorization: Bearer {access_token}
    ```

    > **Info:** Parable automatically handles token refresh, so you don't need to manage token expiration manually.

    #### Metadata & identity

    Unity Catalog catalogs, schemas, tables; SCIM users and groups

    #### User activity

    Audit events and SQL query history from `system.access.audit` and `system.query.history`

    | Tap                                               | Source                 | Enabled by default |
    | ------------------------------------------------- | ---------------------- | ------------------ |
    | `users`, `groups`                                 | SCIM API               | Yes                |
    | `catalogs`, `schemas`, `tables`                   | Unity Catalog API      | Yes                |
    | `audit_logs`                                      | `system.access.audit`  | Yes                |
    | `query_history`                                   | `system.query.history` | Yes                |
    | `jobs`, `job_runs`, `clusters`, `pipelines`, etc. | Workspace APIs         | Opt-in             |

    * [Audit log system table](https://docs.databricks.com/aws/en/admin/system-tables/audit-logs)
    * [Query history system table](https://docs.databricks.com/aws/en/admin/system-tables/query-history)
    * [Statement Execution API](https://docs.databricks.com/api/workspace/statementexecution)

    ## Data streams

    This Provider Plugin defines 14 data streams.

    | Stream               | Description                                                                                                                                                                                                                                                                                                                                                                                                                       | Sync        |
    | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
    | `catalogs`           | Lists all Unity Catalog catalogs available in the Databricks workspace. Provides metadata about each catalog including name, owner, comment, and properties.                                                                                                                                                                                                                                                                      | full        |
    | `schemas`            | Lists all schemas within a specified Unity Catalog catalog. Requires catalog\_name as a parent context field. Provides schema metadata including name, owner, and properties.                                                                                                                                                                                                                                                     | full        |
    | `tables`             | Lists all tables within a specified Unity Catalog catalog and schema. Requires catalog\_name and schema\_name as parent context fields. Provides table metadata including columns, data types, and storage info.                                                                                                                                                                                                                  | full        |
    | `table_summaries`    | Lists table summaries within a catalog, providing a lightweight view of available tables with optional LIKE pattern filtering.                                                                                                                                                                                                                                                                                                    | full        |
    | `clusters`           | Lists all clusters in the Databricks workspace. Provides compute cluster metadata including configuration, state, and resource allocation details.                                                                                                                                                                                                                                                                                | full        |
    | `sql_warehouses`     | Lists all SQL warehouses in the Databricks workspace. Provides SQL warehouse configuration, state, and sizing details.                                                                                                                                                                                                                                                                                                            | full        |
    | `jobs`               | Lists all jobs defined in the Databricks workspace. Provides job configuration, schedule, and metadata. Paginated via next\_page\_token.                                                                                                                                                                                                                                                                                          | full        |
    | `job_runs`           | Lists job runs in the Databricks workspace. Provides run execution details including status, duration, and task results. Paginated via next\_page\_token.                                                                                                                                                                                                                                                                         | full        |
    | `pipelines`          | Lists all Delta Live Tables (DLT) pipelines in the Databricks workspace. Provides pipeline configuration, state, and metadata.                                                                                                                                                                                                                                                                                                    | full        |
    | `users`              | Lists all users in the Databricks workspace via the SCIM v2 API. Provides user identity, email, and group membership information.                                                                                                                                                                                                                                                                                                 | full        |
    | `groups`             | Lists all groups in the Databricks workspace via the SCIM v2 API. Provides group membership and role information.                                                                                                                                                                                                                                                                                                                 | full        |
    | `service_principals` | Lists all service principals in the Databricks workspace via the SCIM v2 API. Provides service principal identity and entitlement information.                                                                                                                                                                                                                                                                                    | full        |
    | `audit_logs`         | Human workspace audit events from system.access.audit (Unity Catalog). Keeps rows with a real user email and drops service-principal / System-User firehose plus token-login, Unity Catalog internals, filesystem signed-URL churn, secrets polling, and lineage/optimization noise. Queried via the SQL Statement Execution API. Requires USE CATALOG on system, USE SCHEMA on system.access, and SELECT on system.access.audit. | incremental |
    | `query_history`      | SQL and serverless compute query execution history from system.query.history. Includes executor identity, statement text, timing, client application, and query\_source linkage to notebooks, jobs, and dashboards. Queried via the SQL Statement Execution API. Requires USE CATALOG on system, USE SCHEMA on system.query, and SELECT on system.query.history.                                                                  | incremental |
  </Tab>

  <Tab title="Setup Guide">
    ### Databricks

    #### What You'll Need

    | Credential             | What it is                                           |
    | ---------------------- | ---------------------------------------------------- |
    | **Client ID**          | Service principal application (client) ID            |
    | **Client Secret**      | OAuth secret generated for the service principal     |
    | **Workspace hostname** | Workspace URL host only (no `https://`)              |
    | **SQL warehouse ID**   | Warehouse used for SQL Statement Execution API calls |
    | **Token endpoint**     | Account- or workspace-level OAuth token URL          |

    > **Info:** **Setup access in Databricks.** These steps require **Account admin or workspace admin**, or a colleague with equivalent permissions who can create credentials for you.
    >
    > If that is not you, ask your Databricks administrator.

    * A Databricks workspace on AWS, Azure, or GCP with **Unity Catalog** enabled
    * At least one **SQL warehouse** (running or auto-start enabled)
    * **System tables** enabled for the account ([Enable system tables](https://docs.databricks.com/aws/en/admin/system-tables/))
    * Network access from Parable to the workspace hostname

    #### Step 1: Create a service principal

    1. Open the Databricks **Account Console**:
       * AWS: [accounts.cloud.databricks.com](https://accounts.cloud.databricks.com)
       * Azure: [accounts.azuredatabricks.net](https://accounts.azuredatabricks.net)
       * GCP: [accounts.gcp.databricks.com](https://accounts.gcp.databricks.com)
    2. Go to **User management → Service principals**.
    3. Click **Add service principal** (for example, `parable-integration`).
    4. Copy the **Application (client) ID**.

    #### Step 2: Assign the service principal to the workspace

    1. In the Account Console, open the service principal → **Workspaces** tab.
    2. Add the target workspace.
    3. Set permission level to **User** (recommended starting point).

    Parable reads users and groups through the workspace SCIM API. If connection tests return **403** on identity taps, change this assignment to **Admin** for this workspace only. Do not grant **account admin** on the service principal.

    #### Step 3: Generate an OAuth secret

    1. Open the service principal in the Account Console.
    2. Go to **OAuth secrets**.
    3. Click **Generate secret**.
    4. Copy the **Client secret** immediately — it is shown only once.

    Save both the **Client ID** and **Client secret** for the Parable connection form.

    #### Step 4: Grant SQL warehouse access

    1. In the workspace, open **SQL → SQL warehouses**.
    2. Select the warehouse Parable will use.
    3. Open **Permissions**.
    4. Grant the service principal **CAN USE** on the warehouse.

    #### Step 5: Grant Unity Catalog metadata access

    Parable lists catalog, schema, and table **metadata** only. Grant **BROWSE** on each catalog Parable should inventory. This allows discovery via the Unity Catalog API without read access to table data.

    Run as a metastore admin or account admin from a Unity Catalog-enabled workspace SQL editor. Replace `` `<service-principal-name>` `` with the service principal display name (for example, `` `parable-integration` ``):

    ```sql theme={null}
    GRANT BROWSE ON CATALOG main TO `<service-principal-name>`;
    GRANT BROWSE ON CATALOG analytics TO `<service-principal-name>`;
    ```

    Repeat for each catalog you want Parable to scan. Do not grant `SELECT`, `MODIFY`, `MANAGE`, or `ALL PRIVILEGES` on customer tables unless you have a separate requirement.

    Catalogs bound only to other workspaces are not visible from this workspace even with `BROWSE`. See [Unity Catalog privileges](https://docs.databricks.com/aws/en/data-governance/unity-catalog/access-control/privileges-reference).

    #### Step 6: Grant system table access (user activity taps)

    Required for **`audit_logs`** and **`query_history`**. Run from a Unity Catalog-enabled workspace as a metastore admin or account admin:

    ```sql theme={null}
    GRANT USE CATALOG ON CATALOG system TO `<service-principal-name>`;
    GRANT USE SCHEMA ON SCHEMA system.access TO `<service-principal-name>`;
    GRANT SELECT ON TABLE system.access.audit TO `<service-principal-name>`;
    GRANT USE SCHEMA ON SCHEMA system.query TO `<service-principal-name>`;
    GRANT SELECT ON TABLE system.query.history TO `<service-principal-name>`;
    ```

    See [Grant access to system tables](https://docs.databricks.com/aws/en/admin/system-tables/#grant-access-to-system-tables).

    #### Step 7: Enter values in Parable

    | Field                                               | Value                                                                                   |
    | --------------------------------------------------- | --------------------------------------------------------------------------------------- |
    | **Client ID** (`clientId`)                          | Service principal application ID                                                        |
    | **Client secret** (`clientSecret`)                  | OAuth secret from the previous step                                                     |
    | **Token endpoint** (`tokenEndpoint`)                | Full HTTPS OAuth token URL (see examples below)                                         |
    | **Workspace instance** (`workspace_instance`)       | Hostname only, e.g. `dbc-abc123.cloud.databricks.com`                                   |
    | **SQL warehouse ID** (`warehouse_id`)               | From SQL warehouse **Connection details**                                               |
    | **Account ID** (`account_id`)                       | Optional; required for account-level OAuth token URLs                                   |
    | **Cloud provider** (`cloud_provider`)               | Optional; `aws`, `azure`, or `gcp` — used with account-level OAuth                      |
    | **Activity workspace ID** (`activity_workspace_id`) | Optional numeric filter for activity taps; leave blank for all workspaces in the region |

    **Token endpoint** is the URL Parable POSTs to for OAuth tokens. Paste the **full URL**, not just the workspace hostname.

    **Workspace-level** (most common — same host as workspace instance):

    ```text theme={null}
    https://dbc-abc123.cloud.databricks.com/oidc/v1/token
    ```

    Pattern: `https://<workspace-hostname>/oidc/v1/token`

    **Account-level** (multi-workspace; replace `<account-id>`):

    | Cloud | Token endpoint                                                              |
    | ----- | --------------------------------------------------------------------------- |
    | AWS   | `https://accounts.cloud.databricks.com/oidc/accounts/<account-id>/v1/token` |
    | Azure | `https://accounts.azuredatabricks.net/oidc/accounts/<account-id>/v1/token`  |
    | GCP   | `https://accounts.gcp.databricks.com/oidc/accounts/<account-id>/v1/token`   |

    OAuth scope: `all-apis` (configured on the Provider; you do not enter it separately).

    #### Step 8: Test connection

    Parable verifies connectivity by executing a SQL statement against the configured warehouse (for example, `SELECT 1` via `/api/2.0/sql/statements`).

    > **Success:** If you received a `200 OK` response with valid data, your credentials are configured correctly. You can now configure this Provider in Parable.

    > **Tip:** Databricks enforces rate limits of **varies by endpoint; Parable defaults to 2–10 requests per second depending on the tap**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

    | Cloud | Account-level token endpoint                                                |
    | ----- | --------------------------------------------------------------------------- |
    | AWS   | `https://accounts.cloud.databricks.com/oidc/accounts/<account-id>/v1/token` |
    | Azure | `https://accounts.azuredatabricks.net/oidc/accounts/<account-id>/v1/token`  |
    | GCP   | `https://accounts.gcp.databricks.com/oidc/accounts/<account-id>/v1/token`   |

    Workspace-level token endpoints also work when the service principal is assigned to that workspace.
  </Tab>

  <Tab title="Permissions">
    ### Databricks

    Parable uses the OAuth scope **`all-apis`** for service principal authentication. That scope is coarse: it allows the service principal to call Databricks REST APIs **for which it has been granted permission** in the workspace and Unity Catalog. Least privilege is enforced with workspace roles, SQL warehouse permissions, and Unity Catalog grants — not with a finer OAuth scope.

    #### Permission layers

    | Layer             | Where to configure                     | What Parable needs                                                            |
    | ----------------- | -------------------------------------- | ----------------------------------------------------------------------------- |
    | **Account**       | Account Console → Service principals   | Dedicated SP, OAuth secret, workspace assignment                              |
    | **Workspace**     | Workspace permissions + SQL warehouses | **User** (or **Admin** if SCIM returns 403); **CAN USE** on one SQL warehouse |
    | **Unity Catalog** | SQL grants or Catalog Explorer         | `BROWSE` on named customer catalogs; read-only grants on `system` tables      |

    Do **not** grant account admin, metastore admin, or **CAN MANAGE** on the SQL warehouse.

    #### Grants by default tap

    | Tap                             | Permission                                                               |
    | ------------------------------- | ------------------------------------------------------------------------ |
    | `audit_logs`                    | **CAN USE** on SQL warehouse + `SELECT` on `system.access.audit`         |
    | `query_history`                 | **CAN USE** on SQL warehouse + `SELECT` on `system.query.history`        |
    | `catalogs`, `schemas`, `tables` | `BROWSE` on each target customer catalog                                 |
    | `users`, `groups`               | Workspace **User**; **Admin** on this workspace if SCIM list returns 403 |

    #### System table grants (reference)

    ```sql theme={null}
    GRANT USE CATALOG ON CATALOG system TO `<service-principal-name>`;
    GRANT USE SCHEMA ON SCHEMA system.access TO `<service-principal-name>`;
    GRANT SELECT ON TABLE system.access.audit TO `<service-principal-name>`;
    GRANT USE SCHEMA ON SCHEMA system.query TO `<service-principal-name>`;
    GRANT SELECT ON TABLE system.query.history TO `<service-principal-name>`;
    ```

    #### Verify permissions

    After generating an OAuth token for the service principal, run these checks (replace placeholders):

    ```bash theme={null}
    TOKEN=<access-token>
    HOST=https://<workspace-host>
    WAREHOUSE_ID=<sql-warehouse-id>
    ```

    ```bash cURL SQL warehouse theme={null}
    curl -s -H "Authorization: Bearer $TOKEN" \
      -H "Content-Type: application/json" \
      -d "{\"statement\":\"SELECT 1\",\"warehouse_id\":\"$WAREHOUSE_ID\"}" \
      "$HOST/api/2.0/sql/statements"
    ```

    ```bash cURL Unity Catalog theme={null}
    curl -s -H "Authorization: Bearer $TOKEN" \
      "$HOST/api/2.1/unity-catalog/catalogs?include_browse=true"
    ```

    ```bash cURL SCIM theme={null}
    curl -s -H "Authorization: Bearer $TOKEN" \
      "$HOST/api/2.0/preview/scim/v2/Users?count=1"
    ```

    A **403** on the SCIM call means the service principal needs workspace **Admin** on this workspace, or identity taps should be disabled in Parable.

    #### Large workspace notes (`tables` tap)

    The `tables` tap fans out from every catalog and schema. In large Unity Catalog estates the first sync can take **15-30+ minutes** and produce **tens of thousands of table metadata rows** (multi-GB bronze). This is expected: Parable paginates the Unity Catalog API and writes one bronze row per table.

    * **First sync:** allow a longer sync window; disable `tables` initially if you only need catalogs/schemas.
    * **Ongoing syncs:** full refresh re-lists table metadata; row counts track catalog growth.
    * **Deadlines:** if your orchestrator enforces a hard per-sync timeout, raise it for the first `tables` run or keep the tap disabled until a maintenance window.

    #### Security review notes

    * **SCIM and workspace Admin (by design):** Parable recommends starting with workspace **User**. If SCIM list calls return **403**, granting **Admin** on this workspace only is the supported escalation so `users` and `groups` taps can sync. Alternatively, leave the service principal at **User** and disable those identity taps in Parable if you do not need them.
    * **`all-apis` is not full admin.** The service principal can only access APIs and data allowed by workspace and Unity Catalog grants.
    * **Customer table data:** `BROWSE` exposes metadata (names, comments, structure), not row contents. Activity taps read platform audit and SQL history tables, not arbitrary customer tables.
    * **No write path:** The grants above do not allow modifying data, jobs, clusters, or permissions.

    <AccordionGroup>
      <Accordion id="provider-permission-tap-databricks-audit-logs-ea8c64450809" title="Audit Logs" icon="shield-check" iconType="sharp-duotone-solid">
        Developer identifier: `audit_logs`

        Audit Logs covers human workspace audit events from system.access.audit (Unity Catalog). Keeps rows with a real user email and drops service-principal / System-User firehose plus token-login, Unity Catalog internals, filesystem signed-URL churn, secrets polling, and lineage/optimization noise. Queried via the SQL Statement Execution API. Requires USE CATALOG on system, USE SCHEMA on system.access, and SELECT on system.access.audit.

        * **Enables:** reconstruct an Audit Logs timeline and correlate each returned actor, target, action, and timestamp during an investigation.
        * **Scope:** Human workspace audit events from system.access.audit (Unity Catalog). Keeps rows with a real user email and drops service-principal / System-User firehose plus token-login, Unity Catalog internals, filesystem signed-URL churn, secrets polling, and lineage/optimization noise. Queried via the SQL Statement Execution API. Requires USE CATALOG on system, USE SCHEMA on system.access, and SELECT on system.access.audit; the connector reads `/api/2.0/sql/statements` as an event stream in incremental mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-audit-logs-account-id-c609048b50f3" title="Account ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.account_id`

            Account ID records Databricks account ID. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `account_id` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; 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-databricks-audit-logs-action-name-05a66d22c9d3" title="Action Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.action_name`

            Action Name records action performed (e.g. login, runNow, commandSubmit). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Audit Logs investigation evidence with the exact `action_name` result, permission, or Databricks classification being examined.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-audit-logs-audit-level-2251365b5bfb" title="Audit Level" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.audit_level`

            Audit Level records `WORKSPACE_LEVEL` or `ACCOUNT_LEVEL`. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `audit_level` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event 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-databricks-audit-logs-event-date-153e8e5c23f2" title="Event Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.event_date`

            Event Date records calendar date of the event. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `event_date` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; the schema uses the `Temporal.Date` 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-databricks-audit-logs-event-id-bfcf7caea74b" title="Event ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.event_id`

            Event ID records unique identifier for the audit event. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `event_id` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; 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-databricks-audit-logs-event-time-aa415dc0902a" title="Event Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.event_time`

            Event Time records UTC timestamp when the event occurred. Used as the incremental sync cursor. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `event_time` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event 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-databricks-audit-logs-identity-metadata-7b0de740a7c4" title="Identity Metadata" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.identity_metadata`

            Identity Metadata records run-as and run-by identity metadata for impersonation scenarios. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `identity_metadata` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is one nested object per containing Databricks Audit Log Event object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-audit-logs-identity-metadata-run-as-620a3ede66fd" title="Run As" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.identity_metadata.run_as`

            Run As records principal whose privileges were used. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `run_as` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Identity Metadata object returned for Audit Logs; it is interpreted at one Databricks Audit Identity Metadata 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-databricks-audit-logs-identity-metadata-run-by-65f275c281ed" title="Run By" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.identity_metadata.run_by`

            Run By records principal that initiated the action. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `run_by` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Identity Metadata object returned for Audit Logs; it is interpreted at one Databricks Audit Identity Metadata 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-databricks-audit-logs-request-id-a30687463daa" title="Request ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.request_id`

            Request ID records unique request identifier. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `request_id` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; 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-databricks-audit-logs-request-params-60386b085364" title="Request Params" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.request_params`

            Request Params records action-specific request parameters. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `request_params` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; the schema uses the `Generic.JSON` 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-databricks-audit-logs-response-c3204b5e865b" title="Response" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.response`

            Response records HTTP response metadata for the audited action (JSON string under the `JSON_ARRAY` result format). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `response` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; the schema uses the `Generic.JSON` 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-databricks-audit-logs-service-name-3425fab060ea" title="Service Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.service_name`

            Service Name records service that handled the request (e.g. notebook, jobs, accounts). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `service_name` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event 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-databricks-audit-logs-session-id-8d5a09d03907" title="Session ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.session_id`

            Session ID records session ID associated with the request. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `session_id` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; 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-databricks-audit-logs-source-ip-address-d8d3e4ad1990" title="Source IP Address" icon="ip" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.source_ip_address`

            Source IP Address records source IP address of the request. It is needed to preserve the Databricks-reported network address context for the same record.

            * **Enables:** correlate `source_ip_address` with the actor, request, or session on the same Databricks event without treating it as proof of physical presence.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; the schema uses the `Network.IpAddress` scalar; the value is network address context; this Databricks-reported or configured context does not establish residency or verified physical presence; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-audit-logs-user-agent-2b284b273028" title="User Agent" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.user_agent`

            User Agent records user agent string from the request. It is needed to preserve the Databricks-reported client device or software context for the same record.

            * **Enables:** correlate `user_agent` with the actor, request, or session on the same Databricks event without treating it as proof of physical presence.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; the value is client device or software context; this Databricks-reported or configured context does not establish residency or verified physical presence; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-audit-logs-user-identity-3fb218114cdb" title="User Identity" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.user_identity`

            User Identity records identity of the user who initiated the request (JSON string under the `JSON_ARRAY` result format). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `user_identity` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event record per row; the schema uses the `Generic.JSON` 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-databricks-audit-logs-version-e6d91c3a507e" title="Version" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.version`

            Version records audit log schema version. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `version` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; it is interpreted at one Databricks Audit Log Event 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-databricks-audit-logs-workspace-id-683054c05b40" title="Workspace ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_logs.workspace_id`

            Workspace ID records workspace ID where the event occurred. Account-level events use 0. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate `workspace_id` with the returned actor, target, action, request, or session identifiers on the same Audit Logs evidence record.
            * **Interpretation:** Databricks reports this value on the Databricks Audit Log Event object returned for Audit Logs; 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>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-databricks-catalogs-e8caa3600fc4" title="Catalogs" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `catalogs`

        Catalogs covers Unity Catalog catalogs available in the Databricks workspace. Provides metadata about each catalog including name, owner, comment, and properties.

        * **Enables:** inventory returned Unity Catalog catalogs and compare their owner, catalog kind, storage reference, and browse-only or Workspace-access flags.
        * **Scope:** Lists all Unity Catalog catalogs available in the Databricks workspace. Provides metadata about each catalog including name, owner, comment, and properties; the connector reads `/api/2.1/unity-catalog/catalogs` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-catalogs-accessible-in-current-worksp-7ad0b3024407" title="Accessible In Current Workspace" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.accessible_in_current_workspace`

            Accessible In Current Workspace records whether the catalog is accessible in the current workspace context. It is needed to distinguish Catalogs rows by the exact Databricks-returned accessible in current workspace value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-browse-only-0f1586e05301" title="Browse Only" icon="database" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.browse_only`

            Browse Only records whether the catalog is browse-only (no data access, metadata only). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Catalogs rows with the exact `browse_only` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is interpreted at one Catalog record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-cache-version-info-bdb5c7121b05" title="Cache Version Info" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.cache_version_info`

            Cache Version Info records cache version metadata for the catalog. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `cache_version_info` and associate them with the containing Catalogs record.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is one nested object per containing Catalog object when present; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-cache-version-info-metastore-2c2105b90ae7" title="Metastore Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.cache_version_info.metastore_version`

            Metastore Version records metastore version cached for this catalog. It is needed to compare the exact metastore version configuration returned for this Cache Version Info record.

            * **Enables:** compare the exact `metastore_version` configuration returned for each Cache Version Info record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Cache Version Info object returned for Catalogs; it is interpreted at one Cache Version Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-catalog-type-873d93d8b77a" title="Catalog Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.catalog_type`

            Catalog Type records type of catalog (e.g., `MANAGED_CATALOG`, `DELTASHARING_CATALOG`). It is needed to distinguish Catalogs rows by the exact Databricks-returned catalog type value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-comment-42095658ab43" title="Comment" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.comment`

            Comment records comment or description for the catalog. It is needed to inspect the exact comment or journal text included with this record.

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

          <Accordion id="provider-permission-field-databricks-catalogs-connection-name-3d14b5c3ca1c" title="Connection Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.connection_name`

            Connection Name records name of the connection, applicable for foreign catalogs. It is needed to compare the returned connection name for individual Catalogs rows and select rows with a specific `connection_name` value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-created-at-82f7c8d82322" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.created_at`

            Created At records timestamp when the catalog was created, in epoch milliseconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalogs records by `created_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-created-by-d5353a8a5763" title="Created By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.created_by`

            Created By records user or principal who created the catalog. It is needed to attribute this Catalogs row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-catalogs-effective-predictive-optimiz-d5b9d50b7d0e" title="Effective Predictive Optimization Flag" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.effective_predictive_optimization_flag`

            Effective Predictive Optimization Flag records effective predictive optimization flag details including value and source. It is needed to preserve the nested effective predictive optimization flag relationship or details on the parent Catalog record.

            * **Enables:** expand `effective_predictive_optimization_flag` to connect the containing Catalog row to its returned effective predictive optimization flag entries.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is one nested object per containing Catalog object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-effective-predictive-optimiz-dc2d5716b871" title="Inherited From Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.effective_predictive_optimization_flag.inherited_from_name`

            Inherited From Name records the name of the object from which this flag was inherited. It is needed to compare the returned inherited from name for individual Catalogs rows and select rows with a specific `inherited_from_name` value.

            * **Enables:** locate Catalogs rows whose returned inherited from name exactly matches `inherited_from_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Effective Predictive Optimization Flag object returned for Catalogs; it is interpreted at one Effective Predictive Optimization Flag record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-effective-predictive-optimiz-aa286fdabeb6" title="Inherited From Type" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.effective_predictive_optimization_flag.inherited_from_type`

            Inherited From Type records the type of object from which this flag was inherited (e.g., CATALOG, SCHEMA, ACCOUNT). It is needed to distinguish Catalogs rows by the exact Databricks-returned inherited from type value.

            * **Enables:** separate Catalogs rows by the exact Databricks-returned `inherited_from_type` label when comparing inherited from type.
            * **Interpretation:** Databricks reports this value on the Effective Predictive Optimization Flag object returned for Catalogs; it is interpreted at one Effective Predictive Optimization Flag record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-effective-predictive-optimiz-d332e1a7142c" title="Value" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.effective_predictive_optimization_flag.value`

            Value records the resolved effective value of predictive optimization. It is needed to distinguish Catalogs rows by the exact Databricks-returned value value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-enable-predictive-optimizati-9c502deaa890" title="Enable Predictive Optimization" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.enable_predictive_optimization`

            Enable Predictive Optimization records whether predictive optimization is enabled for the catalog. It is needed to distinguish Catalogs rows by the exact Databricks-returned enable predictive optimization value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-etag-5c8b678a920b" title="ETag" icon="database" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.etag`

            ETag records entity tag for optimistic concurrency on catalog updates. It is needed to compare the returned e tag for individual Catalogs rows and select rows with a specific `etag` value.

            * **Enables:** trace the e tag relationship returned in `etag` from the Catalog row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is interpreted at one Catalog record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-full-name-e813963c99a3" title="Full Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.full_name`

            Full Name records full name of the catalog, typically the same as name for top-level catalogs. It is needed to compare the returned full name for individual Catalogs rows and select rows with a specific `full_name` value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-id-440d2a830d56" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.id`

            ID records Unity Catalog catalog UUID. It is needed to refer to the same catalog across records without relying on display text.

            * **Enables:** match `id` to catalog references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is an identifier, not a measured quantity; the schema uses the `Identity.UUID` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-isolation-mode-56308e4ba8eb" title="Isolation Mode" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.isolation_mode`

            Isolation Mode records isolation mode of the catalog. It is needed to distinguish Catalogs rows by the exact Databricks-returned isolation mode value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-metastore-id-270bf50d1842" title="Metastore ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.metastore_id`

            Metastore ID records ID of the metastore this catalog belongs to. It is needed to refer to the same metastore across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-catalogs-metastore-version-1d184f8c551e" title="Metastore Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.metastore_version`

            Metastore Version records metastore version associated with this catalog record. It is needed to compare the exact metastore version configuration returned for this Catalog record.

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

          <Accordion id="provider-permission-field-databricks-catalogs-name-c6804928fd67" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.name`

            Name records name of the catalog. Serves as the primary key. It is needed to distinguish repeated deliveries of the same Catalogs row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-catalogs-options-2ae548c928d9" title="Options" icon="database" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.options`

            Options records options for configuring the catalog, such as connection options for foreign catalogs. It is needed to compare the exact options configuration returned for this Catalog record.

            * **Enables:** compare the exact `options` configuration returned for each Catalog record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is interpreted at one Catalog record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-owner-e81862c6e897" title="Owner" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.owner`

            Owner records owner of the catalog. It is needed to attribute this Catalogs row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-catalogs-properties-00246bad31b9" title="Properties" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.properties`

            Properties records key-value properties associated with the catalog. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `properties` and associate them with the containing Catalogs record.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is interpreted at one Catalog record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-provider-name-d6d23f4d717c" title="Provider Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.provider_name`

            Provider Name records name of the provider, applicable for Delta Sharing catalogs. It is needed to compare the returned provider name for individual Catalogs rows and select rows with a specific `provider_name` value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-provisioning-info-672a25a4e33c" title="Provisioning Info" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.provisioning_info`

            Provisioning Info records provisioning state information for the catalog. It is needed to preserve the nested provisioning info relationship or details on the parent Catalog record.

            * **Enables:** expand `provisioning_info` to connect the containing Catalog row to its returned provisioning info entries.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is one nested object per containing Catalog object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-provisioning-info-state-af434dfa203f" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.provisioning_info.state`

            State records current provisioning state of the catalog. It is needed to distinguish Catalogs rows by the exact Databricks-returned state value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-query-federation-attributes-d6e925634bed" title="Query Federation Attributes" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.query_federation_attributes`

            Query Federation Attributes records foreign-catalog federation metadata when `catalog_type` is `FOREIGN_CATALOG`. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `query_federation_attributes` and associate them with the containing Catalogs record.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is one nested object per containing Catalog object when present; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-query-federation-attributes--0bd2b4592875" title="Connection ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.query_federation_attributes.connection_id`

            Connection ID records foreign connection UUID backing the catalog. It is needed to refer to the same connection across records without relying on display text.

            * **Enables:** match `connection_id` to connection references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Query Federation Attributes object returned for Catalogs; it is an identifier, not a measured quantity; the schema uses the `Identity.UUID` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-query-federation-attributes--b78fe3d48b0b" title="Last Refreshed Timestamp" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.query_federation_attributes.last_refreshed_timestamp`

            Last Refreshed Timestamp records epoch milliseconds when federation metadata was last refreshed. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalogs records by `last_refreshed_timestamp`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Query Federation Attributes object returned for Catalogs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-resource-name-02b8352fe172" title="Resource Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.resource_name`

            Resource Name records metastore-relative resource path for the catalog. It is needed to compare the returned resource name for individual Catalogs rows and select rows with a specific `resource_name` value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-securable-kind-ae2b36946012" title="Securable Kind" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.securable_kind`

            Securable Kind records the kind of securable, such as `CATALOG_STANDARD` or `CATALOG_DELTASHARING`. It is needed to distinguish Catalogs rows by the exact Databricks-returned securable kind value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-securable-type-1aa824147f81" title="Securable Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.securable_type`

            Securable Type records the securable type of this object, typically CATALOG. It is needed to distinguish Catalogs rows by the exact Databricks-returned securable type value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-share-name-701147e4069a" title="Share Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.share_name`

            Share Name records name of the share, applicable for Delta Sharing catalogs. It is needed to compare the returned share name for individual Catalogs rows and select rows with a specific `share_name` value.

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

          <Accordion id="provider-permission-field-databricks-catalogs-storage-location-177aac5c79c5" title="Storage Location" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.storage_location`

            Storage Location records storage location URL for the catalog. It is needed to preserve the Databricks-reported resource location link for the same record.

            * **Enables:** correlate the Databricks resource link in `storage_location` with its containing Catalog row without treating the resource path as a statement of data residency.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is interpreted at one Catalog record per row; the schema uses the `Network.Uri` scalar; the value is resource location link; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-storage-root-0a89c15d72aa" title="Storage Root" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.storage_root`

            Storage Root records root storage location for managed tables in this catalog. It is needed to compare the returned storage root for individual Catalogs rows and select rows with a specific `storage_root` value.

            * **Enables:** trace the storage root relationship returned in `storage_root` from the Catalog row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; it is interpreted at one Catalog record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-updated-at-aa4e11d0b7fa" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.updated_at`

            Updated At records timestamp when the catalog was last updated, in epoch milliseconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Catalogs records by `updated_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Catalog object returned for Catalogs; its unit or granularity is epoch milliseconds; the connector also declares it for record ordering; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-catalogs-updated-by-ed70f1e4c95a" title="Updated By" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `catalogs.updated_by`

            Updated By records user or principal who last updated the catalog. It is needed to attribute this Catalogs row to the returned person, account, or organization reference.

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

      <Accordion id="provider-permission-tap-databricks-clusters-09f4f5238ba1" title="Clusters" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `clusters`

        Clusters covers clusters in the Databricks workspace. Provides compute cluster metadata including configuration, state, and resource allocation details.

        * **Enables:** compare returned cluster configuration, lifecycle state, worker allocation, creator, and activity times.
        * **Scope:** Lists all clusters in the Databricks workspace. Provides compute cluster metadata including configuration, state, and resource allocation details; the connector reads `/api/{apiVersion}/clusters/list` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-clusters-autoscale-f96f31e3f6eb" title="Autoscale" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.autoscale`

            Autoscale records autoscale configuration specifying min and max workers. It is needed to measure the Databricks-reported number of autoscale at one Databricks Cluster record per row.

            * **Enables:** measure and compare the Databricks-reported number of autoscale in `autoscale` at one Databricks Cluster record per row.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is a Databricks-reported count at one Databricks Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-autoscale-max-workers-1e06cd8e6010" title="Max Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.autoscale.max_workers`

            Max Workers records maximum number of workers the cluster can scale up to. It is needed to measure the Databricks-reported number of max workers at one Autoscale Config record per row.

            * **Enables:** measure and compare the Databricks-reported number of max workers in `max_workers` at one Autoscale Config record per row.
            * **Interpretation:** Databricks reports this value on the Autoscale Config object returned for Clusters; it is a Databricks-reported count at one Autoscale Config record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-autoscale-min-workers-79ea74ce7ead" title="Min Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.autoscale.min_workers`

            Min Workers records minimum number of workers the cluster can scale down to. It is needed to measure the Databricks-reported number of min workers at one Autoscale Config record per row.

            * **Enables:** measure and compare the Databricks-reported number of min workers in `min_workers` at one Autoscale Config record per row.
            * **Interpretation:** Databricks reports this value on the Autoscale Config object returned for Clusters; it is a Databricks-reported count at one Autoscale Config record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-d5fe348a58e5" title="AWS Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes`

            AWS Attributes records AWS-specific cluster attributes (present for AWS workspaces). It is needed to preserve the nested aws attributes relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `aws_attributes` to connect the containing Databricks Cluster row to its returned aws attributes entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-availability-46d4fa018762" title="Availability" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.availability`

            Availability records availability type for the cluster. It is needed to distinguish Clusters rows by the exact Databricks-returned availability value.

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

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-ebs-volume-co-9905e2f45aa1" title="Ebs Volume Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.ebs_volume_count`

            Ebs Volume Count records number of EBS volumes attached to each node. It is needed to measure the Databricks-reported number of eBS volumes attached to each node at one AWS Attributes record per row.

            * **Enables:** measure and compare the Databricks-reported number of eBS volumes attached to each node in `ebs_volume_count` at one AWS Attributes record per row.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; it is a Databricks-reported count at one AWS Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-ebs-volume-io-1e2635897e2f" title="Ebs Volume Iops" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.ebs_volume_iops`

            Ebs Volume Iops records IOPS for provisioned IOPS EBS volumes. It is needed to compare the numeric ebs volume iops reported for one AWS Attributes record without assuming an unstated unit.

            * **Enables:** compare the numeric `ebs_volume_iops` value per AWS Attributes record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; it is interpreted at one AWS Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-ebs-volume-si-8f9a56f1f2c9" title="Ebs Volume Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.ebs_volume_size`

            Ebs Volume Size records size of each EBS volume in GiB. It is needed to compare the numeric ebs volume size reported for one AWS Attributes record without assuming an unstated unit.

            * **Enables:** compare the numeric `ebs_volume_size` value per AWS Attributes record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; it is interpreted at one AWS Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-ebs-volume-th-b8a34e93a901" title="Ebs Volume Throughput" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.ebs_volume_throughput`

            Ebs Volume Throughput records throughput for gp3 EBS volumes in MiB/s. It is needed to compare the numeric ebs volume throughput reported for one AWS Attributes record without assuming an unstated unit.

            * **Enables:** compare the numeric `ebs_volume_throughput` value per AWS Attributes record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; it is interpreted at one AWS Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-ebs-volume-ty-842cf8a74bcc" title="Ebs Volume Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.ebs_volume_type`

            Ebs Volume Type records EBS volume type (e.g. `GENERAL_PURPOSE_SSD`, `THROUGHPUT_OPTIMIZED_HDD`). It is needed to distinguish Clusters rows by the exact Databricks-returned ebs volume type value.

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

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-first-on-dema-13e1d2c4336a" title="First On Demand" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.first_on_demand`

            First On Demand records number of nodes placed on on-demand instances first. It is needed to measure the Databricks-reported number of nodes placed on on-demand instances first at one AWS Attributes record per row.

            * **Enables:** measure and compare the Databricks-reported number of nodes placed on on-demand instances first in `first_on_demand` at one AWS Attributes record per row.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; it is a Databricks-reported count at one AWS Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-instance-prof-1833ebcb84a9" title="Instance Profile Arn" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.instance_profile_arn`

            Instance Profile Arn records ARN of the instance profile for the cluster. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `instance_profile_arn` among Clusters records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; it is interpreted at one AWS Attributes record per row; the value is a Databricks-returned or configured label at the Aws Attributes grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-spot-bid-pric-e7a2a3316a5b" title="Spot Bid Price Percent" icon="sack-dollar" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.spot_bid_price_percent`

            Spot Bid Price Percent records max bid price as a percentage of on-demand price for spot instances. It is needed to measure the reported spot bid price percent for one aws attributes record.

            * **Enables:** measure and compare `spot_bid_price_percent` per AWS Attributes record in percent.
            * **Interpretation:** Databricks reports this value on the AWS Attributes object returned for Clusters; its unit or granularity is percent.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-aws-attributes-zone-id-b758f8c1cb16" title="Zone ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.aws_attributes.zone_id`

            Zone ID records AWS availability zone ID. It is needed to refer to the same zone across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-clusters-azure-attributes-b39b0f32029f" title="Azure Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.azure_attributes`

            Azure Attributes records azure-specific cluster attributes (present for Azure workspaces). It is needed to preserve the nested azure attributes relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `azure_attributes` to connect the containing Databricks Cluster row to its returned azure attributes entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-azure-attributes-availabilit-bcac2411eb21" title="Availability" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.azure_attributes.availability`

            Availability records availability type for the cluster. It is needed to distinguish Clusters rows by the exact Databricks-returned availability value.

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

          <Accordion id="provider-permission-field-databricks-clusters-azure-attributes-first-on-de-181b850e3cf6" title="First On Demand" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.azure_attributes.first_on_demand`

            First On Demand records number of nodes placed on on-demand instances first. It is needed to measure the Databricks-reported number of nodes placed on on-demand instances first at one Azure Attributes record per row.

            * **Enables:** measure and compare the Databricks-reported number of nodes placed on on-demand instances first in `first_on_demand` at one Azure Attributes record per row.
            * **Interpretation:** Databricks reports this value on the Azure Attributes object returned for Clusters; it is a Databricks-reported count at one Azure Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-azure-attributes-log-analyti-0dbd6a7e2ef5" title="Log Analytics Info" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.azure_attributes.log_analytics_info`

            Log Analytics Info records log Analytics workspace configuration. It is needed to compare the exact log analytics info configuration returned for this Azure Attributes record.

            * **Enables:** compare the exact `log_analytics_info` configuration returned for each Azure Attributes record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Azure Attributes object returned for Clusters; it is interpreted at one Azure Attributes record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-azure-attributes-spot-bid-ma-7e15c731b841" title="Spot Bid Max Price" icon="sack-dollar" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.azure_attributes.spot_bid_max_price`

            Spot Bid Max Price records max bid price for Azure spot instances (-1 for on-demand price). It is needed to measure the exact commercial amount reported on this record.

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

          <Accordion id="provider-permission-field-databricks-clusters-cluster-cores-21d5df782312" title="Cluster Cores" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_cores`

            Cluster Cores records total number of cores available across the cluster. It is needed to measure the Databricks-reported number of cores available across the cluster at one Databricks Cluster record per row.

            * **Enables:** measure and compare the Databricks-reported number of cores available across the cluster in `cluster_cores` at one Databricks Cluster record per row.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is a Databricks-reported count at one Databricks Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-id-2aeb8567b552" title="Cluster ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_id`

            Cluster ID records unique identifier for the cluster. It is needed to distinguish repeated deliveries of the same Clusters row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-05092c013d43" title="Cluster Log Conf" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf`

            Cluster Log Conf records configuration for delivering Spark logs to a destination. It is needed to preserve the nested cluster log conf relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `cluster_log_conf` to connect the containing Databricks Cluster row to its returned cluster log conf entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-dbfs-e2f0463a9cdd" title="Dbfs" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.dbfs`

            Dbfs records DBFS destination for logs. It is needed to preserve the nested dbfs relationship or details on the parent Cluster Log Conf record.

            * **Enables:** expand `dbfs` to connect the containing Cluster Log Conf row to its returned dbfs entries.
            * **Interpretation:** Databricks reports this value on the Cluster Log Conf object returned for Clusters; it is one nested object per containing Cluster Log Conf object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-dbfs-destin-4d5e977c972b" title="Destination" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.dbfs.destination`

            Destination records DBFS path. It is needed to compare the returned destination for individual Clusters rows and select rows with a specific `destination` value.

            * **Enables:** trace the destination relationship returned in `destination` from the Dbfs Storage Info row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Dbfs Storage Info object returned for Clusters; it is interpreted at one Dbfs Storage Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-s3-61b46c037964" title="S3" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3`

            S3 records s3 destination for logs. It is needed to preserve the nested s3 relationship or details on the parent Cluster Log Conf record.

            * **Enables:** expand `s3` to connect the containing Cluster Log Conf row to its returned s3 entries.
            * **Interpretation:** Databricks reports this value on the Cluster Log Conf object returned for Clusters; it is one nested object per containing Cluster Log Conf object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-s3-canned-a-38faa96e1e62" title="Canned Acl" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.canned_acl`

            Canned Acl records canned ACL to apply. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Clusters rows with the exact `canned_acl` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the S3 Storage Info object returned for Clusters; it is interpreted at one S3 Storage Info record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-s3-destinat-6dcaa57fcdb3" title="Destination" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.destination`

            Destination records s3 URI. It is needed to retain the exact Databricks resource or external link reported for this Clusters record.

            * **Enables:** open or correlate the resource named by `destination` while retaining the containing S3 Storage Info row as provenance.
            * **Interpretation:** Databricks reports this value on the S3 Storage Info object returned for Clusters; it is interpreted at one S3 Storage Info 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-databricks-clusters-cluster-log-conf-s3-enable-e-5ad94db5484d" title="Enable Encryption" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.enable_encryption`

            Enable Encryption records whether server-side encryption is enabled. It is needed to distinguish Clusters rows by the exact Databricks-returned enable encryption value.

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

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-s3-encrypti-bf3e441e2b6c" title="Encryption Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.encryption_type`

            Encryption Type records encryption type (e.g. sse-s3). It is needed to distinguish Clusters rows by the exact Databricks-returned encryption type value.

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

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-s3-endpoint-b532f0094a36" title="Endpoint" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.endpoint`

            Endpoint records s3 endpoint URL. It is needed to retain the exact Databricks resource or external link reported for this Clusters record.

            * **Enables:** open or correlate the resource named by `endpoint` while retaining the containing S3 Storage Info row as provenance.
            * **Interpretation:** Databricks reports this value on the S3 Storage Info object returned for Clusters; it is interpreted at one S3 Storage Info 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-databricks-clusters-cluster-log-conf-s3-kms-key-d351e4d4543c" title="Kms Key" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.kms_key`

            Kms Key records KMS key for encryption. It is needed to refer to the same kms across records without relying on display text.

            * **Enables:** match `kms_key` to kms references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the S3 Storage Info object returned for Clusters; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-conf-s3-region-988117333b6f" title="Region" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_conf.s3.region`

            Region records AWS region of the S3 bucket. It is needed to scope the returned S3 storage configuration to the AWS region named for its bucket.

            * **Enables:** combine `region` with the sibling S3 destination and endpoint when reproducing or investigating the same log-storage configuration.
            * **Interpretation:** Databricks reports this value on the S3 Storage Info object returned for Clusters; it is one AWS region label per S3 storage configuration; the label scopes the configured bucket endpoint and does not establish data residency or verified physical storage.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-status-e8a163af8253" title="Cluster Log Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_status`

            Cluster Log Status records status of log delivery for the cluster. It is needed to preserve the nested cluster log status relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `cluster_log_status` to connect the containing Databricks Cluster row to its returned cluster log status entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-status-last-atte-e622818df874" title="Last Attempted" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_status.last_attempted`

            Last Attempted records timestamp (epoch ms) of the last log sync attempt. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `last_attempted`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Log Sync Status object returned for Clusters; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-log-status-last-exce-83ba94278ae6" title="Last Exception" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_log_status.last_exception`

            Last Exception records exception message from the last failed sync attempt. It is needed to inspect the exact exception message returned for this Log Sync Status record.

            * **Enables:** attribute the exception message in `last_exception` to the containing Clusters identifier, owner or author, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Log Sync Status object returned for Clusters; it is interpreted at one Log Sync Status record per row; this is only the exception message included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-memory-mb-db587bbe1299" title="Cluster Memory Mb" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_memory_mb`

            Cluster Memory Mb records total cluster memory in megabytes. It is needed to measure the reported cluster memory mb for one databricks cluster record.

            * **Enables:** measure and compare `cluster_memory_mb` per Databricks Cluster record in megabytes.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; its unit or granularity is megabytes.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-cluster-name-3498b8d49267" title="Cluster Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_name`

            Cluster Name records human-readable name of the cluster. It is needed to compare the returned cluster name for individual Clusters rows and select rows with a specific `cluster_name` value.

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

          <Accordion id="provider-permission-field-databricks-clusters-cluster-source-0062acdd3832" title="Cluster Source" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.cluster_source`

            Cluster Source records source that created the cluster (UI, API, JOB, etc.). It is needed to distinguish Clusters rows by the exact Databricks-returned cluster source value.

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

          <Accordion id="provider-permission-field-databricks-clusters-creator-user-name-4de3a3018c0f" title="Creator User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.creator_user_name`

            Creator User Name records username of the user who created the cluster. It is needed to attribute this Clusters row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-clusters-custom-tags-9a56bd41b973" title="Custom Tags" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.custom_tags`

            Custom Tags records custom user-defined tags applied to the cluster. It is needed to distinguish Clusters rows by the exact Databricks-returned custom tags value.

            * **Enables:** separate Clusters rows by the exact Databricks-returned `custom_tags` label when comparing custom tags.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster record per row; the schema uses the `Generic.JSON` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-data-security-mode-c2151a43a8ac" title="Data Security Mode" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.data_security_mode`

            Data Security Mode records data security mode for the cluster (Unity Catalog access mode). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Clusters rows with the exact `data_security_mode` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-default-tags-bcd4bc5b6619" title="Default Tags" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.default_tags`

            Default Tags records default tags automatically applied to the cluster by Databricks. It is needed to distinguish Clusters rows by the exact Databricks-returned default tags value.

            * **Enables:** separate Clusters rows by the exact Databricks-returned `default_tags` label when comparing default tags.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster record per row; the schema uses the `Generic.JSON` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-fb222f624f86" title="Disk Spec" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec`

            Disk Spec records disk specification for worker nodes. It is needed to preserve the nested disk spec relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `disk_spec` to connect the containing Databricks Cluster row to its returned disk spec entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-count-a39ad1131ebd" title="Disk Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_count`

            Disk Count records number of disks per node. It is needed to measure the Databricks-reported number of disks per node at one Disk Spec record per row.

            * **Enables:** measure and compare the Databricks-reported number of disks per node in `disk_count` at one Disk Spec record per row.
            * **Interpretation:** Databricks reports this value on the Disk Spec object returned for Clusters; it is a Databricks-reported count at one Disk Spec record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-iops-8c47e30c561e" title="Disk Iops" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_iops`

            Disk Iops records IOPS for the disk. It is needed to compare the numeric disk iops reported for one Disk Spec record without assuming an unstated unit.

            * **Enables:** compare the numeric `disk_iops` value per Disk Spec record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the Disk Spec object returned for Clusters; it is interpreted at one Disk Spec record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-size-6fbb80625d52" title="Disk Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_size`

            Disk Size records size of each disk in GiB. It is needed to compare the numeric disk size reported for one Disk Spec record without assuming an unstated unit.

            * **Enables:** compare the numeric `disk_size` value per Disk Spec record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the Disk Spec object returned for Clusters; it is interpreted at one Disk Spec record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-throughput-1e0a42f581f2" title="Disk Throughput" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_throughput`

            Disk Throughput records throughput for the disk in MiB/s. It is needed to compare the numeric disk throughput reported for one Disk Spec record without assuming an unstated unit.

            * **Enables:** compare the numeric `disk_throughput` value per Disk Spec record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the Disk Spec object returned for Clusters; it is interpreted at one Disk Spec record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-type-914e09166d28" title="Disk Type" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_type`

            Disk Type records disk type configuration. It is needed to preserve the nested disk type relationship or details on the parent Disk Spec record.

            * **Enables:** expand `disk_type` to connect the containing Disk Spec row to its returned disk type entries.
            * **Interpretation:** Databricks reports this value on the Disk Spec object returned for Clusters; it is one nested object per containing Disk Spec object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-type-azure-di-412e0af48a64" title="Azure Disk Volume Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_type.azure_disk_volume_type`

            Azure Disk Volume Type records azure managed disk type. It is needed to distinguish Clusters rows by the exact Databricks-returned azure disk volume type value.

            * **Enables:** separate Clusters rows by the exact Databricks-returned `azure_disk_volume_type` label when comparing azure disk volume type.
            * **Interpretation:** Databricks reports this value on the Disk Type object returned for Clusters; it is interpreted at one Disk Type record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-disk-spec-disk-type-ebs-volu-f987453ba314" title="Ebs Volume Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.disk_spec.disk_type.ebs_volume_type`

            Ebs Volume Type records EBS volume type (AWS). It is needed to distinguish Clusters rows by the exact Databricks-returned ebs volume type value.

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

          <Accordion id="provider-permission-field-databricks-clusters-docker-image-6741d41cff66" title="Docker Image" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.docker_image`

            Docker Image records custom Docker image for the cluster (Databricks Container Services). It is needed to preserve the nested docker image relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `docker_image` to connect the containing Databricks Cluster row to its returned docker image entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-docker-image-basic-auth-d7f58fa34531" title="Basic Auth" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.docker_image.basic_auth`

            Basic Auth records basic authentication credentials for the Docker registry. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `basic_auth` to examine the returned basic auth details for the containing Docker Image record.
            * **Interpretation:** Databricks reports this value on the Docker Image object returned for Clusters; it is one nested object per containing Docker Image object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-docker-image-basic-auth-pass-439308750d6d" title="Password" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.docker_image.basic_auth.password`

            Password records docker registry password. 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 `password` access value with the resource, account, or membership represented by the same Clusters row.
            * **Interpretation:** Databricks reports this value on the Docker Basic Auth object returned for Clusters; it is interpreted at one Docker Basic Auth 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-databricks-clusters-docker-image-basic-auth-user-cced2dd98ae5" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.docker_image.basic_auth.username`

            User Name records docker registry username. It is needed to attribute this Clusters row to the returned person, account, or organization reference.

            * **Enables:** attribute the Clusters row to the returned person or account and match the exact `username` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Docker Basic Auth object returned for Clusters; it is interpreted at one Docker Basic Auth record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-docker-image-url-528c33324341" title="URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.docker_image.url`

            URL records docker image URL. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `url` while retaining the containing Clusters record as provenance.
            * **Interpretation:** Databricks reports this value on the Docker Image object returned for Clusters; it is link at one Docker Image record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-7c92f645ad25" title="Driver" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver`

            Driver records information about the driver node. It is needed to preserve the nested driver relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `driver` to connect the containing Databricks Cluster row to its returned driver entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-host-private-ip-ea6d64554658" title="Host Private IP" icon="ip" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.host_private_ip`

            Host Private IP records the private network address of the host underlying the Spark node. It is needed to correlate that host address with the containing cluster and node inventory.

            * **Enables:** compare `host_private_ip` with `private_ip`, `node_id`, `instance_id`, and the containing Clusters record when reconciling returned hosts and Spark nodes.
            * **Interpretation:** Databricks reports this value on the Spark Node object returned for Clusters; it identifies the host's private network address in that cluster inventory.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-instance-id-f72c0ef1802b" title="Instance ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.instance_id`

            Instance ID records cloud provider instance ID. It is needed to refer to the same instance across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-clusters-driver-node-aws-attributes-3510d9dcc972" title="Node AWS Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.node_aws_attributes`

            Node AWS Attributes records AWS-specific node attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `node_aws_attributes` and associate them with the containing Clusters record.
            * **Interpretation:** Databricks reports this value on the Spark Node object returned for Clusters; it is interpreted at one Spark Node record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-node-id-0e5c40e9a3b8" title="Node ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.node_id`

            Node ID records unique identifier for the node. It is needed to refer to the same node across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-clusters-driver-private-ip-6647df18ca89" title="Private IP" icon="ip" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.private_ip`

            Private IP records the private network address assigned to the Spark node. It is needed to correlate that node address with the containing cluster and node inventory.

            * **Enables:** match `private_ip` with `node_id`, `instance_id`, and the containing Clusters record when reconciling returned Spark nodes.
            * **Interpretation:** Databricks reports this value on the Spark Node object returned for Clusters; it identifies the node's private network address in that cluster inventory.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-public-dns-aec7362608aa" title="Public DNS" icon="network-wired" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.public_dns`

            Public DNS records public DNS name of the node. It is needed to distinguish Clusters rows by the exact Databricks-returned public dns value.

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

          <Accordion id="provider-permission-field-databricks-clusters-driver-start-timestamp-997df89350b3" title="Start Timestamp" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver.start_timestamp`

            Start Timestamp records timestamp (epoch ms) when the node was started. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `start_timestamp`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Spark Node object returned for Clusters; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-instance-pool-id-df9932a62236" title="Driver Instance Pool ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver_instance_pool_id`

            Driver Instance Pool ID records ID of the instance pool used for the driver node. It is needed to refer to the same driver instance pool across records without relying on display text.

            * **Enables:** match `driver_instance_pool_id` to driver instance pool references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-driver-node-type-id-5f7c590ebe3e" title="Driver Node Type ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.driver_node_type_id`

            Driver Node Type ID records instance type identifier for the driver node. It is needed to refer to the same driver node type across records without relying on display text.

            * **Enables:** match `driver_node_type_id` to driver node type references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is an identifier, not a measured quantity; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-effective-spark-version-8a031da92202" title="Effective Spark Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.effective_spark_version`

            Effective Spark Version records the effective Spark version after resolution. It is needed to compare the exact effective spark version configuration returned for this Databricks Cluster record.

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

          <Accordion id="provider-permission-field-databricks-clusters-enable-elastic-disk-e2ba111078e2" title="Enable Elastic Disk" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.enable_elastic_disk`

            Enable Elastic Disk records whether autoscaling local storage is enabled. It is needed to distinguish Clusters rows by the exact Databricks-returned enable elastic disk value.

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

          <Accordion id="provider-permission-field-databricks-clusters-enable-local-disk-encryption-41ad1bd5256e" title="Enable Local Disk Encryption" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.enable_local_disk_encryption`

            Enable Local Disk Encryption records whether local disk encryption is enabled. It is needed to distinguish Clusters rows by the exact Databricks-returned enable local disk encryption value.

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

          <Accordion id="provider-permission-field-databricks-clusters-executors-676515bf6ec2" title="Executors" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.executors`

            Executors records list of executor/worker node information. It is needed to preserve the nested executors relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `executors` to connect the containing Databricks Cluster row to its returned executors entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one returned collection per containing Databricks Cluster object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-1acb8993a92d" title="GCP Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes`

            GCP Attributes records GCP-specific cluster attributes (present for GCP workspaces). It is needed to preserve the nested gcp attributes relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `gcp_attributes` to connect the containing Databricks Cluster row to its returned gcp attributes entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-availability-1a49b6b97e22" title="Availability" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes.availability`

            Availability records availability type for the cluster. It is needed to distinguish Clusters rows by the exact Databricks-returned availability value.

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

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-boot-disk-siz-ca01bf78e9eb" title="Boot Disk Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes.boot_disk_size`

            Boot Disk Size records boot disk size in GiB. It is needed to compare the numeric boot disk size reported for one GCP Attributes record without assuming an unstated unit.

            * **Enables:** compare the numeric `boot_disk_size` value per GCP Attributes record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the GCP Attributes object returned for Clusters; it is interpreted at one GCP Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-google-servic-88cdfa9d18b6" title="Google Service Account" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes.google_service_account`

            Google Service Account records google service account email for the cluster. It is needed to attribute this Clusters row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-local-ssd-cou-43e605958e28" title="Local Ssd Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes.local_ssd_count`

            Local Ssd Count records number of local SSDs attached to each node. It is needed to measure the Databricks-reported number of local SSDs attached to each node at one GCP Attributes record per row.

            * **Enables:** measure and compare the Databricks-reported number of local SSDs attached to each node in `local_ssd_count` at one GCP Attributes record per row.
            * **Interpretation:** Databricks reports this value on the GCP Attributes object returned for Clusters; it is a Databricks-reported count at one GCP Attributes record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-use-preemptib-6656bc0463e0" title="Use Preemptible Executors" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes.use_preemptible_executors`

            Use Preemptible Executors records whether to use preemptible VMs for executors. It is needed to distinguish Clusters rows by the exact Databricks-returned use preemptible executors value.

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

          <Accordion id="provider-permission-field-databricks-clusters-gcp-attributes-zone-id-788700773f1c" title="Zone ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.gcp_attributes.zone_id`

            Zone ID records GCP zone ID for the cluster. It is needed to refer to the same zone across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-8b70f762d36f" title="Init Scripts" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts`

            Init Scripts records list of init scripts configured for the cluster. It is needed to preserve the nested init scripts relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `init_scripts` to connect the containing Databricks Cluster row to its returned init scripts entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one returned collection per containing Databricks Cluster object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-abfss-8c8f98eea65b" title="Abfss" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.abfss`

            Abfss records azure ABFSS location for the init script. It is needed to preserve the nested abfss relationship or details on the parent Init Script Info record.

            * **Enables:** expand `abfss` to connect the containing Init Script Info row to its returned abfss entries.
            * **Interpretation:** Databricks reports this value on the Init Script Info object returned for Clusters; it is one nested object per containing Init Script Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-abfss-destinati-62ad592ff2e5" title="Destination" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.abfss.destination`

            Destination records ABFSS URI. It is needed to retain the exact Databricks resource or external link reported for this Clusters record.

            * **Enables:** open or correlate the resource named by `destination` while retaining the containing Abfss Storage Info row as provenance.
            * **Interpretation:** Databricks reports this value on the Abfss Storage Info object returned for Clusters; it is interpreted at one Abfss Storage Info 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-databricks-clusters-init-scripts-dbfs-cd926c97d4e4" title="Dbfs" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.dbfs`

            Dbfs records DBFS path for the init script. It is needed to preserve the nested dbfs relationship or details on the parent Init Script Info record.

            * **Enables:** expand `dbfs` to connect the containing Init Script Info row to its returned dbfs entries.
            * **Interpretation:** Databricks reports this value on the Init Script Info object returned for Clusters; it is one nested object per containing Init Script Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-gcs-82d6e2d3c846" title="Gcs" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.gcs`

            Gcs records GCS location for the init script. It is needed to preserve the nested gcs relationship or details on the parent Init Script Info record.

            * **Enables:** expand `gcs` to connect the containing Init Script Info row to its returned gcs entries.
            * **Interpretation:** Databricks reports this value on the Init Script Info object returned for Clusters; it is one nested object per containing Init Script Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-gcs-destination-14111e12df82" title="Destination" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.gcs.destination`

            Destination records GCS URI. It is needed to retain the exact Databricks resource or external link reported for this Clusters record.

            * **Enables:** open or correlate the resource named by `destination` while retaining the containing Gcs Storage Info row as provenance.
            * **Interpretation:** Databricks reports this value on the Gcs Storage Info object returned for Clusters; it is interpreted at one Gcs Storage Info 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-databricks-clusters-init-scripts-s3-33052b95b625" title="S3" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.s3`

            S3 records s3 location for the init script. It is needed to preserve the nested s3 relationship or details on the parent Init Script Info record.

            * **Enables:** expand `s3` to connect the containing Init Script Info row to its returned s3 entries.
            * **Interpretation:** Databricks reports this value on the Init Script Info object returned for Clusters; it is one nested object per containing Init Script Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-volumes-c30fa6c76fa6" title="Volumes" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.volumes`

            Volumes records Unity Catalog volumes path for the init script. It is needed to preserve the nested volumes relationship or details on the parent Init Script Info record.

            * **Enables:** expand `volumes` to connect the containing Init Script Info row to its returned volumes entries.
            * **Interpretation:** Databricks reports this value on the Init Script Info object returned for Clusters; it is one nested object per containing Init Script Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-volumes-destina-954cbdeac5b6" title="Destination" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.volumes.destination`

            Destination records volumes path. It is needed to compare the returned destination for individual Clusters rows and select rows with a specific `destination` value.

            * **Enables:** trace the destination relationship returned in `destination` from the Volumes Storage Info row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Volumes Storage Info object returned for Clusters; it is interpreted at one Volumes Storage Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-workspace-583ac526bacc" title="Workspace" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.workspace`

            Workspace records workspace file system path for the init script. It is needed to preserve the nested workspace relationship or details on the parent Init Script Info record.

            * **Enables:** expand `workspace` to connect the containing Init Script Info row to its returned workspace entries.
            * **Interpretation:** Databricks reports this value on the Init Script Info object returned for Clusters; it is one nested object per containing Init Script Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-init-scripts-workspace-desti-e5e4ffc1929e" title="Destination" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.init_scripts.workspace.destination`

            Destination records workspace file path. It is needed to compare the returned destination for individual Clusters rows and select rows with a specific `destination` value.

            * **Enables:** trace the destination relationship returned in `destination` from the Workspace Storage Info row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Workspace Storage Info object returned for Clusters; it is interpreted at one Workspace Storage Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-instance-pool-id-ca18c0d564a7" title="Instance Pool ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.instance_pool_id`

            Instance Pool ID records ID of the instance pool used for worker nodes. It is needed to refer to the same instance pool across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-clusters-last-activity-time-abfd9ad94bdd" title="Last Activity Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.last_activity_time`

            Last Activity Time records timestamp (epoch milliseconds) of the last activity on the cluster. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `last_activity_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; its unit or granularity is epoch milliseconds; the connector also declares it for record ordering; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-last-restarted-time-169113a1f930" title="Last Restarted Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.last_restarted_time`

            Last Restarted Time records timestamp (epoch milliseconds) when the cluster was last restarted. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `last_restarted_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-last-state-loss-time-55422b135b4e" title="Last State Loss Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.last_state_loss_time`

            Last State Loss Time records timestamp (epoch milliseconds) of the last state loss event. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `last_state_loss_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-node-type-id-958084dc7c09" title="Node Type ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.node_type_id`

            Node Type ID records instance type identifier for worker nodes. It is needed to refer to the same node type across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-clusters-num-workers-32b8b40956e4" title="Num Workers" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.num_workers`

            Num Workers records fixed number of worker nodes (mutually exclusive with autoscale). It is needed to measure the Databricks-reported number of num workers at one Databricks Cluster record per row.

            * **Enables:** measure and compare the Databricks-reported number of num workers in `num_workers` at one Databricks Cluster record per row.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is a Databricks-reported count at one Databricks Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-policy-id-fb4a731bf8b8" title="Policy ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.policy_id`

            Policy ID records ID of the cluster policy used to create this cluster. 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 `policy_id` access value with the resource, account, or membership represented by the same Clusters row.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; 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-databricks-clusters-runtime-engine-fe60f889f6fc" title="Runtime Engine" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.runtime_engine`

            Runtime Engine records runtime engine type (STANDARD or PHOTON). It is needed to distinguish Clusters rows by the exact Databricks-returned runtime engine value.

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

          <Accordion id="provider-permission-field-databricks-clusters-single-user-name-e9c6409978f8" title="Single User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.single_user_name`

            Single User Name records single user name for single-user access mode clusters. 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 `single_user_name` access value with the resource, account, or membership represented by the same Clusters row.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster 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-databricks-clusters-spark-conf-d064fe0b978f" title="Spark Conf" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.spark_conf`

            Spark Conf records spark configuration key-value pairs set on the cluster. It is needed to compare the exact spark conf configuration returned for this Databricks Cluster record.

            * **Enables:** compare the exact `spark_conf` configuration returned for each Databricks Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-spark-env-vars-0a2cfc63eeab" title="Spark Env Vars" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.spark_env_vars`

            Spark Env Vars records environment variables set for Spark processes. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Databricks Cluster record.

            * **Enables:** inspect the keys in `spark_env_vars` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-spark-version-64a520c7e657" title="Spark Version" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.spark_version`

            Spark Version records spark runtime version string (e.g. 13.3.x-scala2.12). It is needed to compare the exact spark version configuration returned for this Databricks Cluster record.

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

          <Accordion id="provider-permission-field-databricks-clusters-spec-e290bf7d41b2" title="Spec" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.spec`

            Spec records the original cluster specification used to create or edit the cluster. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Databricks Cluster record.

            * **Enables:** inspect the keys in `spec` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is interpreted at one Databricks Cluster record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-ssh-public-keys-248acbec6d94" title="SSH Public Keys" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.ssh_public_keys`

            SSH Public Keys records SSH public keys added to the cluster for access. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `ssh_public_keys` to examine the returned ssh public keys details for the containing Databricks Cluster record.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one returned collection per containing Databricks Cluster object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-start-time-397b584806be" title="Start Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.start_time`

            Start Time records timestamp (epoch milliseconds) when the cluster was started. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `start_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-state-6446f3668dd4" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.state`

            State records current lifecycle state of the cluster. It is needed to distinguish Clusters rows by the exact Databricks-returned state value.

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

          <Accordion id="provider-permission-field-databricks-clusters-state-message-4d385826d553" title="State Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.state_message`

            State Message records informational message associated with the current cluster state. It is needed to inspect the exact message text included with this record.

            * **Enables:** inspect the message text returned in `state_message` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is message text at one Databricks Cluster record per row; this is only the content included in the Databricks response for this record; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-terminated-time-1b7641ad9120" title="Terminated Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.terminated_time`

            Terminated Time records timestamp (epoch milliseconds) when the cluster was terminated. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Clusters records by `terminated_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-termination-reason-83754b87df04" title="Termination Reason" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.termination_reason`

            Termination Reason records details about why the cluster was terminated. It is needed to preserve the nested termination reason relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `termination_reason` to connect the containing Databricks Cluster row to its returned termination reason entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-termination-reason-code-1e2c8d0bd23a" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.termination_reason.code`

            Code records termination reason code (e.g. `USER_REQUEST`, INACTIVITY). It is needed to distinguish Clusters rows by the exact Databricks-returned code value.

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

          <Accordion id="provider-permission-field-databricks-clusters-termination-reason-parameter-6dca7256f1c2" title="Parameters" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.termination_reason.parameters`

            Parameters records additional parameters providing context for the termination. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Termination Reason record.

            * **Enables:** inspect the keys in `parameters` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Termination Reason object returned for Clusters; it is interpreted at one Termination Reason record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-termination-reason-type-e6baed18f968" title="Type" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.termination_reason.type`

            Type records termination type (e.g. SUCCESS, `CLIENT_ERROR`, `SERVICE_FAULT`). It is needed to distinguish Clusters rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-clusters-workload-type-eea77b15e5da" title="Workload Type" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.workload_type`

            Workload Type records workload type configuration for the cluster. It is needed to preserve the nested workload type relationship or details on the parent Databricks Cluster record.

            * **Enables:** expand `workload_type` to connect the containing Databricks Cluster row to its returned workload type entries.
            * **Interpretation:** Databricks reports this value on the Databricks Cluster object returned for Clusters; it is one nested object per containing Databricks Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-workload-type-clients-cc8b13c97224" title="Clients" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.workload_type.clients`

            Clients records client workload types enabled on the cluster. It is needed to preserve the nested clients relationship or details on the parent Workload Type record.

            * **Enables:** expand `clients` to connect the containing Workload Type row to its returned clients entries.
            * **Interpretation:** Databricks reports this value on the Workload Type object returned for Clusters; it is one nested object per containing Workload Type object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-clusters-workload-type-clients-jobs-923cde3392ff" title="Jobs" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.workload_type.clients.jobs`

            Jobs records whether job workloads are enabled. It is needed to distinguish Clusters rows by the exact Databricks-returned jobs value.

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

          <Accordion id="provider-permission-field-databricks-clusters-workload-type-clients-notebo-c61b71ab6813" title="Notebooks" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `clusters.workload_type.clients.notebooks`

            Notebooks records whether notebook workloads are enabled. It is needed to distinguish Clusters rows by the exact Databricks-returned notebooks value.

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

      <Accordion id="provider-permission-tap-databricks-groups-96df55fa22c6" title="Groups" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `groups`

        Groups covers groups in the Databricks workspace via the SCIM v2 API. Provides group membership and role information.

        * **Enables:** map the Databricks accounts and memberships represented by Groups records and trace a returned access assignment to its account or group.
        * **Scope:** Lists all groups in the Databricks workspace via the SCIM v2 API. Provides group membership and role information; the connector reads `/api/{apiVersion}/preview/scim/v2/Groups` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-groups-displayname-91aa42f6556e" title="Display Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.displayName`

            Display Name records display name of the group. It is needed to compare the returned display name for individual Groups rows and select rows with a specific `displayName` value.

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

          <Accordion id="provider-permission-field-databricks-groups-entitlements-8d1fd3dc0216" title="Entitlements" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.entitlements`

            Entitlements records array of entitlements assigned to the group, such as workspace-level permissions. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `entitlements` to examine the returned entitlements details for the containing Databricks Group record.
            * **Interpretation:** Databricks reports this value on the Databricks Group object returned for Groups; it is one returned collection per containing Databricks Group object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-entitlements-value-d77918aa2992" title="Value" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `groups.entitlements.value`

            Value records the entitlement value, e.g., 'allow-cluster-create', 'allow-instance-pool-create', 'databricks-sql-access', 'workspace-access'. 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 `value` access value with the resource, account, or membership represented by the same Groups row.
            * **Interpretation:** Databricks reports this value on the Group Entitlement object returned for Groups; it is interpreted at one Group Entitlement 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-databricks-groups-externalid-c5b4dfb7d065" title="External ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.externalId`

            External ID records external ID from the identity provider (e.g., Azure AD, Okta). It is needed to refer to the same external across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-groups-groups-07e2fc543b61" title="Groups" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.groups`

            Groups records parent groups that this group belongs to (nested group membership). It is needed to preserve the nested groups relationship or details on the parent Databricks Group record.

            * **Enables:** expand `groups` to connect the containing Databricks Group row to its returned groups entries.
            * **Interpretation:** Databricks reports this value on the Databricks Group object returned for Groups; it is one returned collection per containing Databricks Group object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-groups-ref-d1212b4bdade" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.groups.$ref`

            Resource Reference records URI reference to the parent group resource. It is needed to refer to the same `the` across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-groups-groups-display-c4ac32746674" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.groups.display`

            Display records the display name of the parent group. It is needed to compare the returned display for individual Groups rows and select rows with a specific `display` value.

            * **Enables:** locate Groups rows whose returned display exactly matches `display` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Group Reference object returned for Groups; it is interpreted at one Group Reference record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-groups-type-ec432f0eadc6" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `groups.groups.type`

            Type records the type of the reference, typically 'direct' or 'indirect'. It is needed to distinguish Groups rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-groups-groups-value-3fc5657e4a5c" title="Value" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.groups.value`

            Value records the SCIM ID of the parent group. It is needed to compare the returned value for individual Groups rows and select rows with a specific `value` value.

            * **Enables:** trace the value relationship returned in `value` from the Group Reference row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Group Reference object returned for Groups; it is interpreted at one Group Reference record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-id-6450e667329c" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.id`

            ID records unique SCIM identifier for the group. It is needed to distinguish repeated deliveries of the same Groups row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-groups-members-95c9ea584e88" title="Members" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `groups.members`

            Members records array of group members. Each entry references a user or service principal by SCIM ID. It is needed to preserve the nested members relationship or details on the parent Databricks Group record.

            * **Enables:** expand `members` to connect the containing Databricks Group row to its returned members entries.
            * **Interpretation:** Databricks reports this value on the Databricks Group object returned for Groups; it is one returned collection per containing Databricks Group object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-members-ref-7e02ae6966d8" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.members.$ref`

            Resource Reference records the URI reference to the group member resource (for example, `Users/<id>` or `Groups/<id>`). It is needed to identify the exact Databricks user or group represented by each membership.

            * **Enables:** use `$ref` to correlate the membership with the matching Users or Groups record.
            * **Interpretation:** Databricks reports this SCIM resource reference on the Group Member object returned for Groups; it is a relative resource identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-members-display-0454759793c6" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.members.display`

            Display records the display name of the member. It is needed to attribute this Groups row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-groups-members-type-fe5bee5b5270" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `groups.members.type`

            Type records the type of the member resource. It is needed to distinguish Groups rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-groups-members-value-b363cabd0146" title="Value" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `groups.members.value`

            Value records the SCIM ID of the member (user, service principal, or group). It is needed to attribute this Groups row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-groups-meta-e5b336d71287" title="Meta" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.meta`

            Meta records SCIM metadata for the group resource, including resource type and timestamps. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `meta` and associate them with the containing Groups record.
            * **Interpretation:** Databricks reports this value on the Databricks Group object returned for Groups; it is one nested object per containing Databricks Group object when present; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-meta-created-0654342f6041" title="Created" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `groups.meta.created`

            Created records ISO 8601 timestamp when the resource was created. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-databricks-groups-meta-lastmodified-8b3a9ab36aa0" title="Last Modified" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `groups.meta.lastModified`

            Last Modified records ISO 8601 timestamp when the resource was last modified. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-databricks-groups-meta-location-a0db30ca6d81" title="Location" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.meta.location`

            Location records URI location of the resource. It is needed to preserve the Databricks-reported resource location link for the same record.

            * **Enables:** correlate the Databricks resource link in `location` with its containing Scim Meta row without treating the resource path as a statement of data residency.
            * **Interpretation:** Databricks reports this value on the Scim Meta object returned for Groups; it is interpreted at one Scim Meta record per row; the schema uses the `Network.Url` scalar; the value is resource location link; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-meta-resourcetype-6826b587dccd" title="Resource Type" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `groups.meta.resourceType`

            Resource Type records the SCIM resource type (e.g., User, Group). It is needed to distinguish Groups rows by the exact Databricks-returned resource type value.

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

          <Accordion id="provider-permission-field-databricks-groups-meta-version-17dbe0fff6a0" title="Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `groups.meta.version`

            Version records version identifier (ETag) of the resource. It is needed to refer to the same version across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-groups-roles-bb2d35f9ff0f" title="Roles" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.roles`

            Roles records array of roles assigned to the group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `roles` to examine the returned roles details for the containing Databricks Group record.
            * **Interpretation:** Databricks reports this value on the Databricks Group object returned for Groups; it is one returned collection per containing Databricks Group object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-roles-type-a49945b03e8c" title="Type" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.roles.type`

            Type records the type of the role assignment. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Groups rows with the exact `type` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Group Role object returned for Groups; it is interpreted at one Group Role record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-groups-roles-value-c5c56879b956" title="Value" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.roles.value`

            Value records the role value string, e.g., an instance profile ARN or role identifier. 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 `value` access value with the resource, account, or membership represented by the same Groups row.
            * **Interpretation:** Databricks reports this value on the Group Role object returned for 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-databricks-groups-schemas-56ab09b66460" title="Schemas" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `groups.schemas`

            Schemas records SCIM schema URNs that apply to this resource. It is needed to preserve the nested schemas relationship or details on the parent Databricks Group record.

            * **Enables:** expand `schemas` to connect the containing Databricks Group row to its returned schemas entries.
            * **Interpretation:** Databricks reports this value on the Databricks Group object returned for Groups; it is one returned collection per containing Databricks Group object.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-databricks-job-runs-b7a88f950842" title="Job Runs" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `job_runs`

        Job Runs covers job runs in the Databricks workspace. Provides run execution details including status, duration, and task results. Paginated via `next_page_token`.

        * **Enables:** trace each returned job run through its job, trigger, tasks, lifecycle result, start time, and duration.
        * **Scope:** Lists job runs in the Databricks workspace. Provides run execution details including status, duration, and task results. Paginated via `next_page_token`; the connector reads `/api/2.1/jobs/runs/list` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-job-runs-parent-job-id-f017d1a74cb6" title="Parent Job ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs._parent_job_id`

            Parent Job ID records parent key injected by the ingestor from the jobs to `job_runs` traversal parentContextFields. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to refer to the same parent job across records without relying on display text.

            * **Enables:** match `_parent_job_id` to parent job references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks's child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-attempt-number-39b9c12ce29a" title="Attempt Number" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.attempt_number`

            Attempt Number records attempt number of the run, starting from 0. It is needed to measure the Databricks-reported number of attempt number at one Job Run record per row.

            * **Enables:** measure and compare the Databricks-reported number of attempt number in `attempt_number` at one Job Run record per row.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is a Databricks-reported count at one Job Run record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cleanup-duration-e4a7053111ae" title="Cleanup Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cleanup_duration`

            Cleanup Duration records duration of cleanup phase in milliseconds. It is needed to measure the exact duration reported for one Job Run record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `cleanup_duration` per Job Run record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-instance-74f29d66956a" title="Cluster Instance" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_instance`

            Cluster Instance records the cluster instance details attached to this Job Runs record. It is needed to preserve the nested cluster instance relationship or details on the parent Job Run record.

            * **Enables:** expand `cluster_instance` to connect the containing Job Run row to its returned cluster instance entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-instance-cluster-id-017e0f8025ff" title="Cluster ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_instance.cluster_id`

            Cluster ID records ID of the cluster. It is needed to refer to the same cluster across records without relying on display text.

            * **Enables:** match `cluster_id` to cluster references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Cluster Instance object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-instance-spark-conte-f61c64eb5611" title="Spark Context ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_instance.spark_context_id`

            Spark Context ID records ID of the Spark context. It is needed to refer to the same spark context across records without relying on display text.

            * **Enables:** match `spark_context_id` to spark context references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Cluster Instance object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-70698763fd51" title="Cluster Spec" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec`

            Cluster Spec records the cluster spec details attached to this Job Runs record. It is needed to preserve the nested cluster spec relationship or details on the parent Job Run record.

            * **Enables:** expand `cluster_spec` to connect the containing Job Run row to its returned cluster spec entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-existing-cluste-31a7fb6d6189" title="Existing Cluster ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.existing_cluster_id`

            Existing Cluster ID records ID of an existing cluster. It is needed to refer to the same existing cluster across records without relying on display text.

            * **Enables:** match `existing_cluster_id` to existing cluster references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Cluster Spec object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-52a2260a26db" title="Libraries" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries`

            Libraries records libraries to install. It is needed to preserve the nested libraries relationship or details on the parent Cluster Spec record.

            * **Enables:** expand `libraries` to connect the containing Cluster Spec row to its returned libraries entries.
            * **Interpretation:** Databricks reports this value on the Cluster Spec object returned for Job Runs; it is one returned collection per containing Cluster Spec object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-cran-b379bb881bb0" title="Cran" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.cran`

            Cran records the cran details attached to this Job Runs record. It is needed to preserve the nested cran relationship or details on the parent Library record.

            * **Enables:** expand `cran` to connect the containing Library row to its returned cran entries.
            * **Interpretation:** Databricks reports this value on the Library object returned for Job Runs; it is one nested object per containing Library object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-cran--2a24d8b8ac1f" title="Package" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.cran.package`

            Package records CRAN package name. It is needed to reproduce the exact package or entry-point configuration used by this job task.

            * **Enables:** combine `package` with the sibling library type and repository fields to resolve the configured dependency or executable entry point.
            * **Interpretation:** Databricks reports this value on the Cran Library object returned for Job Runs; it is interpreted at one Cran Library record per row; the value names Databricks job configuration and does not prove that the dependency is still available.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-cran--d28c069e2f83" title="Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.cran.repo`

            Repo records custom CRAN repository URL. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Cran Library object returned for Job Runs; it is interpreted at one Cran Library 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-databricks-job-runs-cluster-spec-libraries-egg-8d6326777223" title="Egg" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.egg`

            Egg records URI of the egg. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `egg` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Library object returned for Job Runs; it is interpreted at one Library 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-databricks-job-runs-cluster-spec-libraries-jar-5c67bf26d7dd" title="Jar" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.jar`

            Jar records URI of the JAR. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `jar` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Library object returned for Job Runs; it is interpreted at one Library 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-databricks-job-runs-cluster-spec-libraries-maven-20c2eeebf4b0" title="Maven" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.maven`

            Maven records the maven details attached to this Job Runs record. It is needed to preserve the nested maven relationship or details on the parent Library record.

            * **Enables:** expand `maven` to connect the containing Library row to its returned maven entries.
            * **Interpretation:** Databricks reports this value on the Library object returned for Job Runs; it is one nested object per containing Library object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-maven-0dde4cfc44c8" title="Coordinates" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.maven.coordinates`

            Coordinates records maven coordinates. It is needed to reproduce the exact package or entry-point configuration used by this job task.

            * **Enables:** combine `coordinates` with the sibling library type and repository fields to resolve the configured dependency or executable entry point.
            * **Interpretation:** Databricks reports this value on the Maven Library object returned for Job Runs; its unit or granularity is provider-reported geographic coordinates; the value names Databricks job configuration and does not prove that the dependency is still available.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-maven-ce48213b3c6c" title="Exclusions" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.maven.exclusions`

            Exclusions records maven dependency exclusions. It is needed to preserve the nested exclusions relationship or details on the parent Maven Library record.

            * **Enables:** expand `exclusions` to connect the containing Maven Library row to its returned exclusions entries.
            * **Interpretation:** Databricks reports this value on the Maven Library object returned for Job Runs; it is one returned collection per containing Maven Library object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-maven-76d72ee33048" title="Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.maven.repo`

            Repo records custom Maven repository URL. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Maven Library object returned for Job Runs; it is interpreted at one Maven Library 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-databricks-job-runs-cluster-spec-libraries-pypi-02e5f2d3b4e7" title="Pypi" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.pypi`

            Pypi records the pypi details attached to this Job Runs record. It is needed to preserve the nested pypi relationship or details on the parent Library record.

            * **Enables:** expand `pypi` to connect the containing Library row to its returned pypi entries.
            * **Interpretation:** Databricks reports this value on the Library object returned for Job Runs; it is one nested object per containing Library object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-pypi--5e47c421c028" title="Package" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.pypi.package`

            Package records pyPI package name. It is needed to reproduce the exact package or entry-point configuration used by this job task.

            * **Enables:** combine `package` with the sibling library type and repository fields to resolve the configured dependency or executable entry point.
            * **Interpretation:** Databricks reports this value on the Python Py Pi Library object returned for Job Runs; it is interpreted at one Python Py Pi Library record per row; the value names Databricks job configuration and does not prove that the dependency is still available.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-libraries-pypi--1fb5f8cd7c1d" title="Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.pypi.repo`

            Repo records custom PyPI repository URL. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Python Py Pi Library object returned for Job Runs; it is interpreted at one Python Py Pi Library 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-databricks-job-runs-cluster-spec-libraries-whl-7db338c12a12" title="Whl" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.libraries.whl`

            Whl records URI of the wheel. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `whl` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Library object returned for Job Runs; it is interpreted at one Library 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-databricks-job-runs-cluster-spec-new-cluster-5cb2cb6b5e1d" title="New Cluster" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster`

            New Cluster records the new cluster details attached to this Job Runs record. It is needed to preserve the nested new cluster relationship or details on the parent Cluster Spec record.

            * **Enables:** expand `new_cluster` to connect the containing Cluster Spec row to its returned new cluster entries.
            * **Interpretation:** Databricks reports this value on the Cluster Spec object returned for Job Runs; it is one nested object per containing Cluster Spec object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-aut-017baba6dd80" title="Autoscale" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.autoscale`

            Autoscale records the autoscale details attached to this Job Runs record. It is needed to preserve the nested autoscale relationship or details on the parent New Cluster record.

            * **Enables:** expand `autoscale` to connect the containing New Cluster row to its returned autoscale entries.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is one nested object per containing New Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-aut-ddb1e4a29102" title="Max Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.autoscale.max_workers`

            Max Workers records maximum number of workers. It is needed to measure the Databricks-reported number of max workers at one Auto Scale record per row.

            * **Enables:** measure and compare the Databricks-reported number of max workers in `max_workers` at one Auto Scale record per row.
            * **Interpretation:** Databricks reports this value on the Auto Scale object returned for Job Runs; it is a Databricks-reported count at one Auto Scale record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-aut-ab8238915142" title="Min Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.autoscale.min_workers`

            Min Workers records minimum number of workers. It is needed to measure the Databricks-reported number of min workers at one Auto Scale record per row.

            * **Enables:** measure and compare the Databricks-reported number of min workers in `min_workers` at one Auto Scale record per row.
            * **Interpretation:** Databricks reports this value on the Auto Scale object returned for Job Runs; it is a Databricks-reported count at one Auto Scale record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-aws-9f66fcd4ffe6" title="AWS Attributes" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.aws_attributes`

            AWS Attributes records AWS-specific attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `aws_attributes` and associate them with the containing Job Runs record.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-azu-3bd5e72dc1f4" title="Azure Attributes" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.azure_attributes`

            Azure Attributes records azure-specific attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `azure_attributes` and associate them with the containing Job Runs record.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-clu-72e60ce77ef4" title="Cluster Log Conf" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.cluster_log_conf`

            Cluster Log Conf records cluster log delivery configuration. It is needed to compare the exact cluster log conf configuration returned for this New Cluster record.

            * **Enables:** compare the exact `cluster_log_conf` configuration returned for each New Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-cus-383be226701b" title="Custom Tags" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.custom_tags`

            Custom Tags records custom tags. It is needed to distinguish Job Runs rows by the exact Databricks-returned custom tags value.

            * **Enables:** separate Job Runs rows by the exact Databricks-returned `custom_tags` label when comparing custom tags.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-dat-4cd51c19f1f4" title="Data Security Mode" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.data_security_mode`

            Data Security Mode records data security mode. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Job Runs rows with the exact `data_security_mode` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-dri-5b4d78e3a459" title="Driver Instance Pool ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.driver_instance_pool_id`

            Driver Instance Pool ID records driver instance pool ID. It is needed to refer to the same driver instance pool across records without relying on display text.

            * **Enables:** match `driver_instance_pool_id` to driver instance pool references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-dri-df0e50a59a19" title="Driver Node Type ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.driver_node_type_id`

            Driver Node Type ID records driver node type ID. It is needed to refer to the same driver node type across records without relying on display text.

            * **Enables:** match `driver_node_type_id` to driver node type references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is an identifier, not a measured quantity; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-ena-f31d0858adfe" title="Enable Elastic Disk" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.enable_elastic_disk`

            Enable Elastic Disk records whether elastic disk is enabled. It is needed to distinguish Job Runs rows by the exact Databricks-returned enable elastic disk value.

            * **Enables:** select Job Runs rows where `enable_elastic_disk` is true or false when comparing the condition described by Enable Elastic Disk.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-gcp-74885bba48a7" title="GCP Attributes" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.gcp_attributes`

            GCP Attributes records GCP-specific attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `gcp_attributes` and associate them with the containing Job Runs record.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-ini-7d346cd7c6e8" title="Init Scripts" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.init_scripts`

            Init Scripts records init scripts. It is needed to preserve the nested init scripts relationship or details on the parent New Cluster record.

            * **Enables:** expand `init_scripts` to connect the containing New Cluster row to its returned init scripts entries.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is one returned collection per containing New Cluster object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-ins-655dd419c948" title="Instance Pool ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.instance_pool_id`

            Instance Pool ID records instance pool ID. It is needed to refer to the same instance pool across records without relying on display text.

            * **Enables:** match `instance_pool_id` to instance pool references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-nod-55a6552397dc" title="Node Type ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.node_type_id`

            Node Type ID records node type ID. It is needed to refer to the same node type across records without relying on display text.

            * **Enables:** match `node_type_id` to node type references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is an identifier, not a measured quantity; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-num-d0b32145c47c" title="Num Workers" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.num_workers`

            Num Workers records number of worker nodes. It is needed to measure the Databricks-reported number of worker nodes at one New Cluster record per row.

            * **Enables:** measure and compare the Databricks-reported number of worker nodes in `num_workers` at one New Cluster record per row.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is a Databricks-reported count at one New Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-pol-2625912da5ca" title="Policy ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.policy_id`

            Policy ID records cluster policy ID. 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 `policy_id` access value with the resource, account, or membership represented by the same Job Runs row.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; 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-databricks-job-runs-cluster-spec-new-cluster-run-71c5bedb6006" title="Runtime Engine" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.runtime_engine`

            Runtime Engine records runtime engine (STANDARD or PHOTON). It is needed to compare the exact runtime engine configuration returned for this New Cluster record.

            * **Enables:** compare the exact `runtime_engine` configuration returned for each New Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-spa-f515ea5ae7dd" title="Spark Conf" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.spark_conf`

            Spark Conf records spark configuration key-value pairs. It is needed to compare the exact spark conf configuration returned for this New Cluster record.

            * **Enables:** compare the exact `spark_conf` configuration returned for each New Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-spa-c2b2b5cf8638" title="Spark Env Vars" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.spark_env_vars`

            Spark Env Vars records spark environment variables. It is needed to preserve the exact Databricks configuration or execution metadata attached to this New Cluster record.

            * **Enables:** inspect the keys in `spark_env_vars` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-cluster-spec-new-cluster-spa-71dad592e43e" title="Spark Version" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.cluster_spec.new_cluster.spark_version`

            Spark Version records Databricks Runtime version. It is needed to compare the exact spark version configuration returned for this New Cluster record.

            * **Enables:** compare the exact `spark_version` configuration returned for each New Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the New Cluster object returned for Job Runs; it is interpreted at one New Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-creator-user-name-495383bf073c" title="Creator User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.creator_user_name`

            Creator User Name records user who created or triggered the run. It is needed to attribute this Job Runs row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-job-runs-description-930ff9c86be5" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.description`

            Description records description of the run or job. 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:** Databricks reports this value on the Job Run object returned for Job Runs; it is description text at one Job Run record per row; this is only the content included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-end-time-8e42716bf2cf" title="End Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.end_time`

            End Time records timestamp in epoch ms when the run ended. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Job Runs records by `end_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-execution-duration-08e016c93a7f" title="Execution Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.execution_duration`

            Execution Duration records duration of execution phase in milliseconds. It is needed to measure the exact duration reported for one Job Run record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `execution_duration` per Job Run record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-format-a0e0352b5539" title="Format" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.format`

            Format records the format supplied for this Job Runs record by Databricks. It is needed to distinguish Job Runs rows by the exact Databricks-returned format value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-5714c2e6fc08" title="Git Source" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source`

            Git Source records the git source details attached to this Job Runs record. It is needed to preserve the nested git source relationship or details on the parent Job Run record.

            * **Enables:** expand `git_source` to connect the containing Job Run row to its returned git source entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-branch-4133aa78e611" title="Git Branch" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_branch`

            Git Branch records git branch name. It is needed to link the row to the exact Databricks branch, tag, revision, or work-item reference named by this field.

            * **Enables:** match `git_branch` to the returned branch, tag, commit SHA, or work-item reference on related Databricks records.
            * **Interpretation:** Databricks reports this value on the Git Source object returned for Job Runs; it is interpreted at one Git Source record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-commit-73db9aba63b8" title="Git Commit" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_commit`

            Git Commit records git commit hash. It is needed to link the row to the exact Databricks branch, tag, revision, or work-item reference named by this field.

            * **Enables:** match `git_commit` to the returned branch, tag, commit SHA, or work-item reference on related Databricks records.
            * **Interpretation:** Databricks reports this value on the Git Source object returned for Job Runs; it is interpreted at one Git Source record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-provider-cd613e91a277" title="Git Provider" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_provider`

            Git Provider records git provider name. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `git_provider` among Job Runs records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Git Source object returned for Job Runs; it is interpreted at one Git Source record per row; the value is a Databricks-returned or configured label at the Git Source grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-snapshot-bb181c220093" title="Git Snapshot" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_snapshot`

            Git Snapshot records the git snapshot details attached to this Job Runs record. It is needed to preserve the nested git snapshot relationship or details on the parent Git Source record.

            * **Enables:** expand `git_snapshot` to connect the containing Git Source row to its returned git snapshot entries.
            * **Interpretation:** Databricks reports this value on the Git Source object returned for Job Runs; it is one nested object per containing Git Source object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-snapshot-used-94a2b793c537" title="Used Commit" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_snapshot.used_commit`

            Used Commit records the commit hash actually used for the run. It is needed to link the row to the exact Databricks branch, tag, revision, or work-item reference named by this field.

            * **Enables:** match `used_commit` to the returned branch, tag, commit SHA, or work-item reference on related Databricks records.
            * **Interpretation:** Databricks reports this value on the Git Snapshot object returned for Job Runs; it is interpreted at one Git Snapshot record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-tag-26006816a24d" title="Git Tag" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_tag`

            Git Tag records git tag. It is needed to link the row to the exact Databricks branch, tag, revision, or work-item reference named by this field.

            * **Enables:** match `git_tag` to the returned branch, tag, commit SHA, or work-item reference on related Databricks records.
            * **Interpretation:** Databricks reports this value on the Git Source object returned for Job Runs; it is interpreted at one Git Source record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-git-source-git-url-dd4864650a32" title="Git URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.git_source.git_url`

            Git URL records URL of the Git repository. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `git_url` while retaining the containing Job Runs record as provenance.
            * **Interpretation:** Databricks reports this value on the Git Source object returned for Job Runs; it is link at one Git Source record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-job-clusters-9da05938129e" title="Job Clusters" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_clusters`

            Job Clusters records job-level cluster specifications shared across tasks. It is needed to preserve the nested job clusters relationship or details on the parent Job Run record.

            * **Enables:** expand `job_clusters` to connect the containing Job Run row to its returned job clusters entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one returned collection per containing Job Run object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-job-clusters-job-cluster-key-a8e2c79b42e5" title="Job Cluster Key" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_clusters.job_cluster_key`

            Job Cluster Key records unique key for this job cluster. It is needed to refer to the same job cluster across records without relying on display text.

            * **Enables:** match `job_cluster_key` to job cluster references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Job Cluster object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-job-clusters-new-cluster-bd97e4d42914" title="New Cluster" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_clusters.new_cluster`

            New Cluster records the new cluster details attached to this Job Runs record. It is needed to preserve the nested new cluster relationship or details on the parent Job Cluster record.

            * **Enables:** expand `new_cluster` to connect the containing Job Cluster row to its returned new cluster entries.
            * **Interpretation:** Databricks reports this value on the Job Cluster object returned for Job Runs; it is one nested object per containing Job Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-job-id-4d373334484f" title="Job ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_id`

            Job ID records ID of the job this run belongs to. It is needed to refer to the same job across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-job-runs-job-parameters-84b134a03343" title="Job Parameters" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_parameters`

            Job Parameters records job-level parameters. It is needed to preserve the nested job parameters relationship or details on the parent Job Run record.

            * **Enables:** expand `job_parameters` to connect the containing Job Run row to its returned job parameters entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one returned collection per containing Job Run object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-job-parameters-default-fb0d91935ab1" title="Default" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_parameters.default`

            Default records default value of the parameter. It is needed to distinguish Job Runs rows by the exact Databricks-returned default value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-job-parameters-name-04c02fa4b415" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_parameters.name`

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

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

          <Accordion id="provider-permission-field-databricks-job-runs-job-parameters-value-70bf2286a3df" title="Value" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.job_parameters.value`

            Value records value of the parameter for this run. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Job Parameter record.

            * **Enables:** inspect the keys in `value` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Job Parameter object returned for Job Runs; it is interpreted at one Job Parameter record per row; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-number-in-job-043dc61ce993" title="Number In Job" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.number_in_job`

            Number In Job records sequence number of this run within the job. It is needed to measure the Databricks-reported number of number in job at one Job Run record per row.

            * **Enables:** measure and compare the Databricks-reported number of number in job in `number_in_job` at one Job Run record per row.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is a Databricks-reported count at one Job Run record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-original-attempt-run-id-e8d23fa53207" title="Original Attempt Run ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.original_attempt_run_id`

            Original Attempt Run ID records the `run_id` of the original attempt if this is a retry. It is needed to refer to the same original attempt run across records without relying on display text.

            * **Enables:** match `original_attempt_run_id` to original attempt run references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-26299cf0453c" title="Overriding Parameters" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters`

            Overriding Parameters records the overriding parameters details attached to this Job Runs record. It is needed to preserve the nested overriding parameters relationship or details on the parent Job Run record.

            * **Enables:** expand `overriding_parameters` to connect the containing Job Run row to its returned overriding parameters entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-dbt-co-d853b3176794" title="Dbt Commands" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.dbt_commands`

            Dbt Commands records dbt commands. It is needed to preserve the nested dbt commands relationship or details on the parent Run Parameters record.

            * **Enables:** expand `dbt_commands` to connect the containing Run Parameters row to its returned dbt commands entries.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is one returned collection per containing Run Parameters object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-jar-pa-66c6594caa45" title="Jar Params" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.jar_params`

            Jar Params records JAR parameters. It is needed to preserve the nested jar params relationship or details on the parent Run Parameters record.

            * **Enables:** expand `jar_params` to connect the containing Run Parameters row to its returned jar params entries.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is one returned collection per containing Run Parameters object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-job-pa-dd8cca7a2503" title="Job Parameters" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.job_parameters`

            Job Parameters records job-level parameters. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Run Parameters record.

            * **Enables:** inspect the keys in `job_parameters` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is interpreted at one Run Parameters record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-notebo-ed9a7795a0c3" title="Notebook Params" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.notebook_params`

            Notebook Params records notebook parameters. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Run Parameters record.

            * **Enables:** inspect the keys in `notebook_params` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is interpreted at one Run Parameters record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-pipeli-ca520fce0334" title="Pipeline Params" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.pipeline_params`

            Pipeline Params records pipeline parameters. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Run Parameters record.

            * **Enables:** inspect the keys in `pipeline_params` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is interpreted at one Run Parameters record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-python-55cde1989a71" title="Python Named Params" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.python_named_params`

            Python Named Params records named Python parameters. It is needed to compare the returned python named params for individual Job Runs rows and select rows with a specific `python_named_params` value.

            * **Enables:** locate Job Runs rows whose returned python named params exactly matches `python_named_params` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is interpreted at one Run Parameters record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-python-8d0febb9fba3" title="Python Params" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.python_params`

            Python Params records python parameters. It is needed to preserve the nested python params relationship or details on the parent Run Parameters record.

            * **Enables:** expand `python_params` to connect the containing Run Parameters row to its returned python params entries.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is one returned collection per containing Run Parameters object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-spark--3e97d9baaca4" title="Spark Submit Params" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.spark_submit_params`

            Spark Submit Params records spark submit parameters. It is needed to preserve the nested spark submit params relationship or details on the parent Run Parameters record.

            * **Enables:** expand `spark_submit_params` to connect the containing Run Parameters row to its returned spark submit params entries.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is one returned collection per containing Run Parameters object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-overriding-parameters-sql-pa-7d98bd0ae252" title="SQL Params" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.overriding_parameters.sql_params`

            SQL Params records SQL parameters. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Run Parameters record.

            * **Enables:** inspect the keys in `sql_params` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Run Parameters object returned for Job Runs; it is interpreted at one Run Parameters record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-queue-duration-66e085ce5f7f" title="Queue Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.queue_duration`

            Queue Duration records time in ms the run spent in the queue. It is needed to measure the exact duration reported for one Job Run record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `queue_duration` per Job Run record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-34151f6c4ecb" title="Repair History" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history`

            Repair History records history of repair attempts. It is needed to preserve the nested repair history relationship or details on the parent Job Run record.

            * **Enables:** expand `repair_history` to connect the containing Job Run row to its returned repair history entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one returned collection per containing Job Run object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-end-time-06c33a09a41a" title="End Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.end_time`

            End Time records timestamp in epoch ms when the repair ended. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Job Runs records by `end_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Repair History Item object returned for Job Runs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-id-85feb20f2124" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.id`

            ID records ID of the repair attempt. It is needed to refer to the same repair history item across records without relying on display text.

            * **Enables:** match `id` to repair history item references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Repair History Item object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-start-time-4f56a96c0e0c" title="Start Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.start_time`

            Start Time records timestamp in epoch ms when the repair started. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Job Runs records by `start_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Repair History Item object returned for Job Runs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-state-9c1362f20462" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.state`

            State records the state details attached to this Job Runs record. It is needed to preserve the nested state relationship or details on the parent Repair History Item record.

            * **Enables:** expand `state` to connect the containing Repair History Item row to its returned state entries.
            * **Interpretation:** Databricks reports this value on the Repair History Item object returned for Job Runs; it is one nested object per containing Repair History Item object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-state-life-cy-e74c90eb1d8a" title="Life Cycle State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.state.life_cycle_state`

            Life Cycle State records the life cycle state supplied for this Job Runs record by Databricks. It is needed to distinguish Job Runs rows by the exact Databricks-returned life cycle state value.

            * **Enables:** separate Job Runs rows by the exact Databricks-returned `life_cycle_state` label when comparing life cycle state.
            * **Interpretation:** Databricks reports this value on the Run State object returned for Job Runs; it is interpreted at one Run State record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-state-queue-r-6629a26a910a" title="Queue Reason" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.state.queue_reason`

            Queue Reason records reason the run is queued. It is needed to distinguish Job Runs rows by the exact Databricks-returned queue reason value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-state-result--f3b3dd144191" title="Result State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.state.result_state`

            Result State records the result state supplied for this Job Runs record by Databricks. It is needed to distinguish Job Runs rows by the exact Databricks-returned result state value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-state-state-m-7790808cd51b" title="State Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.state.state_message`

            State Message records descriptive message for the current state. It is needed to inspect the exact message text included with this record.

            * **Enables:** inspect the message text returned in `state_message` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Run State object returned for Job Runs; it is message text at one Run State record per row; this is only the content included in the Databricks response for this record; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-state-user-ca-13a9ef1e4cc2" title="User Cancelled Or Timedout" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.state.user_cancelled_or_timedout`

            User Cancelled Or Timedout records whether the run was cancelled by the user or timed out. It is needed to distinguish Job Runs rows by the exact Databricks-returned user cancelled or timedout value.

            * **Enables:** select Job Runs rows where `user_cancelled_or_timedout` is true or false when comparing the condition described by User Cancelled Or Timedout.
            * **Interpretation:** Databricks reports this value on the Run State object returned for Job Runs; it is interpreted at one Run State record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-task-run-ids-ba179f00f991" title="Task Run IDs" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.task_run_ids`

            Task Run IDs records task run IDs included in this repair. It is needed to preserve the nested task run i ds relationship or details on the parent Repair History Item record.

            * **Enables:** expand `task_run_ids` to connect the containing Repair History Item row to its returned task run i ds entries.
            * **Interpretation:** Databricks reports this value on the Repair History Item object returned for Job Runs; it is one returned collection per containing Repair History Item object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-repair-history-type-8d4979588f21" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.repair_history.type`

            Type records type of repair (ORIGINAL or REPAIR). It is needed to distinguish Job Runs rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-run-duration-3767bfc57c50" title="Run Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.run_duration`

            Run Duration records total duration of the run in milliseconds. It is needed to measure the exact duration reported for one Job Run record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `run_duration` per Job Run record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-run-id-e6cc1117dd3c" title="Run ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.run_id`

            Run ID records unique identifier for the run. It is needed to distinguish repeated deliveries of the same Job Runs row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-job-runs-run-name-ca8bd9ef050a" title="Run Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.run_name`

            Run Name records human-readable name of the run. It is needed to compare the returned run name for individual Job Runs rows and select rows with a specific `run_name` value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-run-page-url-b68d44cd5a68" title="Run Page URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.run_page_url`

            Run Page URL records URL to the run details page in the workspace. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `run_page_url` while retaining the containing Job Runs record as provenance.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is link at one Job Run record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-run-type-0239313275c9" title="Run Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.run_type`

            Run Type records the run type supplied for this Job Runs record by Databricks. It is needed to distinguish Job Runs rows by the exact Databricks-returned run type value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-schedule-a397c6e8ac69" title="Schedule" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.schedule`

            Schedule records the schedule details attached to this Job Runs record. It is needed to preserve the nested schedule relationship or details on the parent Job Run record.

            * **Enables:** expand `schedule` to connect the containing Job Run row to its returned schedule entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-schedule-pause-status-efa59228b21d" title="Pause Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.schedule.pause_status`

            Pause Status records whether the schedule is paused (PAUSED or UNPAUSED). It is needed to distinguish Job Runs rows by the exact Databricks-returned pause status value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-schedule-quartz-cron-express-2b0be066ecfc" title="Quartz Cron Expression" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.schedule.quartz_cron_expression`

            Quartz Cron Expression records quartz cron expression. It is needed to reconstruct the exact schedule or recurrence rule reported for this Cron Schedule record.

            * **Enables:** combine `quartz_cron_expression` with the sibling start time, timezone, interval, or recurrence fields to reproduce the reported schedule.
            * **Interpretation:** Databricks reports this value on the Cron Schedule object returned for Job Runs; it is interpreted at one Cron Schedule record per row; the schema uses the `Temporal.CronExpression` scalar; the value describes a Databricks schedule rule at the containing record grain and does not show whether a future occurrence actually ran.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-schedule-timezone-id-b5ac6c2e59a6" title="Timezone ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.schedule.timezone_id`

            Timezone ID records java timezone ID. It is needed to preserve the Databricks-reported timezone or locale setting for the same record.

            * **Enables:** compare the Databricks-reported timezone or locale setting in `timezone_id` for individual Job Runs rows without treating it as a verified physical location.
            * **Interpretation:** Databricks reports this value on the Cron Schedule object returned for Job Runs; it is an identifier, not a measured quantity; the value is timezone or locale setting; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-setup-duration-31420347466a" title="Setup Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.setup_duration`

            Setup Duration records duration of setup phase in milliseconds. It is needed to measure the exact duration reported for one Job Run record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `setup_duration` per Job Run record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-start-time-dd262bad4eca" title="Start Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.start_time`

            Start Time records timestamp in epoch ms when the run started. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Job Runs records by `start_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; its unit or granularity is epoch milliseconds; the connector also declares it for record ordering; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-state-3d3d66a40a39" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.state`

            State records the state details attached to this Job Runs record. It is needed to preserve the nested state relationship or details on the parent Job Run record.

            * **Enables:** expand `state` to connect the containing Job Run row to its returned state entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-1f1244fb87a2" title="Tasks" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks`

            Tasks records array of task run details. It is needed to preserve the nested tasks relationship or details on the parent Job Run record.

            * **Enables:** expand `tasks` to connect the containing Job Run row to its returned tasks entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one returned collection per containing Job Run object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-attempt-number-70d7e825e98d" title="Attempt Number" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.attempt_number`

            Attempt Number records attempt number for this task. It is needed to refer to the same attempt number across records without relying on display text.

            * **Enables:** match `attempt_number` to attempt number references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-cleanup-duration-a72ec8c8bee1" title="Cleanup Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.cleanup_duration`

            Cleanup Duration records cleanup phase duration in ms. It is needed to measure the exact duration reported for one Run Task record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `cleanup_duration` per Run Task record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-cluster-instance-51b97a01b2af" title="Cluster Instance" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.cluster_instance`

            Cluster Instance records the cluster instance details attached to this Job Runs record. It is needed to preserve the nested cluster instance relationship or details on the parent Run Task record.

            * **Enables:** expand `cluster_instance` to connect the containing Run Task row to its returned cluster instance entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-9fabf15e1e0d" title="Dbt Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task`

            Dbt Task records the dbt task details attached to this Job Runs record. It is needed to preserve the nested dbt task relationship or details on the parent Run Task record.

            * **Enables:** expand `dbt_task` to connect the containing Run Task row to its returned dbt task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-catalog-7a427ab7a506" title="Catalog" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.catalog`

            Catalog records Unity Catalog name. It is needed to compare the returned catalog for individual Job Runs rows and select rows with a specific `catalog` value.

            * **Enables:** trace the catalog relationship returned in `catalog` from the dbt Task row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the dbt Task object returned for Job Runs; it is interpreted at one dbt Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-commands-0dcc0c577d68" title="Commands" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.commands`

            Commands records dbt commands to execute. It is needed to preserve the nested commands relationship or details on the parent dbt Task record.

            * **Enables:** expand `commands` to connect the containing dbt Task row to its returned commands entries.
            * **Interpretation:** Databricks reports this value on the dbt Task object returned for Job Runs; it is one returned collection per containing dbt Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-profiles-dire-bc3adec225d9" title="Profiles Directory" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.profiles_directory`

            Profiles Directory records path to the dbt profiles directory. It is needed to compare the returned profiles directory for individual Job Runs rows and select rows with a specific `profiles_directory` value.

            * **Enables:** trace the profiles directory relationship returned in `profiles_directory` from the dbt Task row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the dbt Task object returned for Job Runs; it is interpreted at one dbt Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-project-direc-2dcafd2548fd" title="Project Directory" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.project_directory`

            Project Directory records path to the dbt project directory. It is needed to compare the returned project directory for individual Job Runs rows and select rows with a specific `project_directory` value.

            * **Enables:** trace the project directory relationship returned in `project_directory` from the dbt Task row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the dbt Task object returned for Job Runs; it is interpreted at one dbt Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-schema-0fa5d4e68098" title="Schema" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.schema`

            Schema records dbt schema. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `schema` among Job Runs records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the dbt Task object returned for Job Runs; it is interpreted at one dbt Task record per row; the value is a Databricks-returned or configured label at the Dbt Task grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-source-1ceaa926fcf7" title="Source" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.source`

            Source records source of the project (WORKSPACE or GIT). It is needed to distinguish Job Runs rows by the exact Databricks-returned source value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-dbt-task-warehouse-id-4b11a43283b7" title="Warehouse ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.dbt_task.warehouse_id`

            Warehouse ID records SQL warehouse ID for dbt. It is needed to refer to the same warehouse across records without relying on display text.

            * **Enables:** match `warehouse_id` to warehouse references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the dbt Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-depends-on-ca664f9466f7" title="Depends On" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.depends_on`

            Depends On records tasks this task depends on. It is needed to preserve the nested depends on relationship or details on the parent Run Task record.

            * **Enables:** expand `depends_on` to connect the containing Run Task row to its returned depends on entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one returned collection per containing Run Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-depends-on-outcome-61014b1c4071" title="Outcome" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.depends_on.outcome`

            Outcome records expected outcome of the dependency. It is needed to distinguish Job Runs rows by the exact Databricks-returned outcome value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-depends-on-task-key-64d194f208ea" title="Task Key" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.depends_on.task_key`

            Task Key records task key of the dependency. It is needed to refer to the same task across records without relying on display text.

            * **Enables:** match `task_key` to task references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Task Dependency object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-description-216aaee68d59" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.description`

            Description records description of the 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 parent record, owner, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is description text at one Run Task record per row; this is only the content included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-end-time-24a20f0f6628" title="End Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.end_time`

            End Time records timestamp in epoch ms when the task ended. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Job Runs records by `end_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-execution-duration-31a2f4a96904" title="Execution Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.execution_duration`

            Execution Duration records execution phase duration in ms. It is needed to measure the exact duration reported for one Run Task record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `execution_duration` per Run Task record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-existing-cluster-id-3342d38ab6e6" title="Existing Cluster ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.existing_cluster_id`

            Existing Cluster ID records ID of an existing cluster. It is needed to refer to the same existing cluster across records without relying on display text.

            * **Enables:** match `existing_cluster_id` to existing cluster references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-job-cluster-key-42163151e489" title="Job Cluster Key" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.job_cluster_key`

            Job Cluster Key records key of the job cluster to use. It is needed to refer to the same job cluster across records without relying on display text.

            * **Enables:** match `job_cluster_key` to job cluster references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-libraries-f9e631715c94" title="Libraries" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.libraries`

            Libraries records libraries installed on the cluster. It is needed to preserve the nested libraries relationship or details on the parent Run Task record.

            * **Enables:** expand `libraries` to connect the containing Run Task row to its returned libraries entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one returned collection per containing Run Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-new-cluster-f83585f82ef9" title="New Cluster" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.new_cluster`

            New Cluster records the new cluster details attached to this Job Runs record. It is needed to preserve the nested new cluster relationship or details on the parent Run Task record.

            * **Enables:** expand `new_cluster` to connect the containing Run Task row to its returned new cluster entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-notebook-task-5e73608959fa" title="Notebook Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.notebook_task`

            Notebook Task records the notebook task details attached to this Job Runs record. It is needed to preserve the nested notebook task relationship or details on the parent Run Task record.

            * **Enables:** expand `notebook_task` to connect the containing Run Task row to its returned notebook task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-notebook-task-base-par-58bbb96e2a9d" title="Base Parameters" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.notebook_task.base_parameters`

            Base Parameters records base parameters. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Notebook Task record.

            * **Enables:** inspect the keys in `base_parameters` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Notebook Task object returned for Job Runs; it is interpreted at one Notebook Task record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-notebook-task-notebook-31af583fba28" title="Notebook Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.notebook_task.notebook_path`

            Notebook Path records absolute path of the notebook. It is needed to compare the returned notebook path for individual Job Runs rows and select rows with a specific `notebook_path` value.

            * **Enables:** trace the notebook path relationship returned in `notebook_path` from the Notebook Task row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Notebook Task object returned for Job Runs; it is interpreted at one Notebook Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-notebook-task-source-832993068533" title="Source" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.notebook_task.source`

            Source records source of the notebook (WORKSPACE or GIT). It is needed to distinguish Job Runs rows by the exact Databricks-returned source value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-pipeline-task-ed85c3610cd8" title="Pipeline Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.pipeline_task`

            Pipeline Task records the pipeline task details attached to this Job Runs record. It is needed to preserve the nested pipeline task relationship or details on the parent Run Task record.

            * **Enables:** expand `pipeline_task` to connect the containing Run Task row to its returned pipeline task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-pipeline-task-full-ref-2b18ba8e461f" title="Full Refresh" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.pipeline_task.full_refresh`

            Full Refresh records whether to perform a full refresh. It is needed to distinguish Job Runs rows by the exact Databricks-returned full refresh value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-pipeline-task-pipeline-c5ca7a7bd385" title="Pipeline ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.pipeline_task.pipeline_id`

            Pipeline ID records ID of the pipeline. It is needed to refer to the same pipeline across records without relying on display text.

            * **Enables:** match `pipeline_id` to pipeline references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Pipeline Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-python-wheel-task-f30b7629e84d" title="Python Wheel Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.python_wheel_task`

            Python Wheel Task records the python wheel task details attached to this Job Runs record. It is needed to preserve the nested python wheel task relationship or details on the parent Run Task record.

            * **Enables:** expand `python_wheel_task` to connect the containing Run Task row to its returned python wheel task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-python-wheel-task-entr-88349d154f1d" title="Entry Point" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.python_wheel_task.entry_point`

            Entry Point records entry point of the package. It is needed to reproduce the exact package or entry-point configuration used by this job task.

            * **Enables:** combine `entry_point` with the sibling library type and repository fields to resolve the configured dependency or executable entry point.
            * **Interpretation:** Databricks reports this value on the Python Wheel Task object returned for Job Runs; it is interpreted at one Python Wheel Task record per row; the value names Databricks job configuration and does not prove that the dependency is still available.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-python-wheel-task-name-ed3b053cb979" title="Named Parameters" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.python_wheel_task.named_parameters`

            Named Parameters records named parameters as key-value pairs. It is needed to compare the returned named parameters for individual Job Runs rows and select rows with a specific `named_parameters` value.

            * **Enables:** locate Job Runs rows whose returned named parameters exactly matches `named_parameters` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Python Wheel Task object returned for Job Runs; it is interpreted at one Python Wheel Task record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-python-wheel-task-pack-4411ef92a5aa" title="Package Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.python_wheel_task.package_name`

            Package Name records name of the Python wheel package. It is needed to compare the returned package name for individual Job Runs rows and select rows with a specific `package_name` value.

            * **Enables:** locate Job Runs rows whose returned package name exactly matches `package_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Python Wheel Task object returned for Job Runs; it is interpreted at one Python Wheel Task record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-python-wheel-task-para-ca4097606000" title="Parameters" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.python_wheel_task.parameters`

            Parameters records command-line parameters. It is needed to preserve the nested parameters relationship or details on the parent Python Wheel Task record.

            * **Enables:** expand `parameters` to connect the containing Python Wheel Task row to its returned parameters entries.
            * **Interpretation:** Databricks reports this value on the Python Wheel Task object returned for Job Runs; it is one returned collection per containing Python Wheel Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-run-id-81ad5a90c64c" title="Run ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.run_id`

            Run ID records unique identifier for this task run. It is needed to refer to the same run across records without relying on display text.

            * **Enables:** match `run_id` to run references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-run-job-task-eab1cd649fcd" title="Run Job Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.run_job_task`

            Run Job Task records the run job task details attached to this Job Runs record. It is needed to preserve the nested run job task relationship or details on the parent Run Task record.

            * **Enables:** expand `run_job_task` to connect the containing Run Task row to its returned run job task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-run-job-task-job-id-fb4633e77b8b" title="Job ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.run_job_task.job_id`

            Job ID records ID of the job to trigger. It is needed to refer to the same job across records without relying on display text.

            * **Enables:** match `job_id` to job references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Run Job Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-run-job-task-job-param-02aa9dcebb1a" title="Job Parameters" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.run_job_task.job_parameters`

            Job Parameters records parameters for the triggered job. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Run Job Task record.

            * **Enables:** inspect the keys in `job_parameters` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Run Job Task object returned for Job Runs; it is interpreted at one Run Job Task record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-run-page-url-79d93e0ab4cf" title="Run Page URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.run_page_url`

            Run Page URL records URL to the task run page. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `run_page_url` while retaining the containing Job Runs record as provenance.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is link at one Run Task record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-setup-duration-f5cb24a098ce" title="Setup Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.setup_duration`

            Setup Duration records setup phase duration in ms. It is needed to measure the exact duration reported for one Run Task record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `setup_duration` per Run Task record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-jar-task-c2a152f773ef" title="Spark Jar Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_jar_task`

            Spark Jar Task records the spark jar task details attached to this Job Runs record. It is needed to preserve the nested spark jar task relationship or details on the parent Run Task record.

            * **Enables:** expand `spark_jar_task` to connect the containing Run Task row to its returned spark jar task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-jar-task-jar-uri-00f649c0ab80" title="Jar URI" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_jar_task.jar_uri`

            Jar URI records URI of the JAR. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `jar_uri` while retaining the containing Job Runs record as provenance.
            * **Interpretation:** Databricks reports this value on the Spark Jar Task object returned for Job Runs; it is link at one Spark Jar Task 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-databricks-job-runs-tasks-spark-jar-task-main-cl-886890cb4f4c" title="Main Class Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_jar_task.main_class_name`

            Main Class Name records full name of the main class. It is needed to distinguish Job Runs rows by the exact Databricks-returned main class name value.

            * **Enables:** separate Job Runs rows by the exact Databricks-returned `main_class_name` label when comparing main class name.
            * **Interpretation:** Databricks reports this value on the Spark Jar Task object returned for Job Runs; it is interpreted at one Spark Jar Task record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-jar-task-paramet-c8cf4e89b792" title="Parameters" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_jar_task.parameters`

            Parameters records parameters passed to the main method. It is needed to preserve the nested parameters relationship or details on the parent Spark Jar Task record.

            * **Enables:** expand `parameters` to connect the containing Spark Jar Task row to its returned parameters entries.
            * **Interpretation:** Databricks reports this value on the Spark Jar Task object returned for Job Runs; it is one returned collection per containing Spark Jar Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-python-task-2097dac08b59" title="Spark Python Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_python_task`

            Spark Python Task records the spark python task details attached to this Job Runs record. It is needed to preserve the nested spark python task relationship or details on the parent Run Task record.

            * **Enables:** expand `spark_python_task` to connect the containing Run Task row to its returned spark python task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-python-task-para-629713d3a045" title="Parameters" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_python_task.parameters`

            Parameters records command-line parameters. It is needed to preserve the nested parameters relationship or details on the parent Spark Python Task record.

            * **Enables:** expand `parameters` to connect the containing Spark Python Task row to its returned parameters entries.
            * **Interpretation:** Databricks reports this value on the Spark Python Task object returned for Job Runs; it is one returned collection per containing Spark Python Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-python-task-pyth-fbf334fd2a6e" title="Python File" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_python_task.python_file`

            Python File records URI of the Python file. It is needed to reproduce the returned code or dependency configuration for this Job Runs record.

            * **Enables:** use `python_file` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Spark Python Task object returned for Job Runs; it is interpreted at one Spark Python Task 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-databricks-job-runs-tasks-spark-python-task-sour-41e86d836609" title="Source" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_python_task.source`

            Source records source of the Python file. It is needed to distinguish Job Runs rows by the exact Databricks-returned source value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-submit-task-e6b444e14cd6" title="Spark Submit Task" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_submit_task`

            Spark Submit Task records the spark submit task details attached to this Job Runs record. It is needed to preserve the nested spark submit task relationship or details on the parent Run Task record.

            * **Enables:** expand `spark_submit_task` to connect the containing Run Task row to its returned spark submit task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-spark-submit-task-para-a8270052d025" title="Parameters" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.spark_submit_task.parameters`

            Parameters records parameters for spark-submit. It is needed to preserve the nested parameters relationship or details on the parent Spark Submit Task record.

            * **Enables:** expand `parameters` to connect the containing Spark Submit Task row to its returned parameters entries.
            * **Interpretation:** Databricks reports this value on the Spark Submit Task object returned for Job Runs; it is one returned collection per containing Spark Submit Task object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-231b1794b8e5" title="SQL Task" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task`

            SQL Task records the sql task details attached to this Job Runs record. It is needed to preserve the nested sql task relationship or details on the parent Run Task record.

            * **Enables:** expand `sql_task` to connect the containing Run Task row to its returned sql task entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-alert-21955621ff92" title="Alert" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.alert`

            Alert records the alert details attached to this Job Runs record. It is needed to preserve the nested alert relationship or details on the parent SQL Task record.

            * **Enables:** expand `alert` to connect the containing SQL Task row to its returned alert entries.
            * **Interpretation:** Databricks reports this value on the SQL Task object returned for Job Runs; it is one nested object per containing SQL Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-alert-alert-i-0eba91fd70f0" title="Alert ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.alert.alert_id`

            Alert ID records ID of the SQL alert. It is needed to refer to the same alert across records without relying on display text.

            * **Enables:** match `alert_id` to alert references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the SQL Task Alert object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-dashboard-930c40882257" title="Dashboard" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.dashboard`

            Dashboard records the dashboard details attached to this Job Runs record. It is needed to preserve the nested dashboard relationship or details on the parent SQL Task record.

            * **Enables:** expand `dashboard` to connect the containing SQL Task row to its returned dashboard entries.
            * **Interpretation:** Databricks reports this value on the SQL Task object returned for Job Runs; it is one nested object per containing SQL Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-dashboard-das-be8a82325d0a" title="Dashboard ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.dashboard.dashboard_id`

            Dashboard ID records ID of the SQL dashboard. It is needed to refer to the same dashboard across records without relying on display text.

            * **Enables:** match `dashboard_id` to dashboard references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the SQL Task Dashboard object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-file-63fef18279ec" title="File" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.file`

            File records the file details attached to this Job Runs record. It is needed to preserve the nested file relationship or details on the parent SQL Task record.

            * **Enables:** expand `file` to connect the containing SQL Task row to its returned file entries.
            * **Interpretation:** Databricks reports this value on the SQL Task object returned for Job Runs; it is one nested object per containing SQL Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-file-path-bcbc78be39cb" title="Path" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.file.path`

            Path records path to the SQL file. It is needed to compare the returned path for individual Job Runs rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the SQL Task File row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the SQL Task File object returned for Job Runs; it is interpreted at one SQL Task File record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-file-source-fee8efb7ca7c" title="Source" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.file.source`

            Source records source of the file. It is needed to distinguish Job Runs rows by the exact Databricks-returned source value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-parameters-38786e4b8b36" title="Parameters" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.parameters`

            Parameters records parameters for the SQL task. It is needed to preserve the exact Databricks configuration or execution metadata attached to this SQL Task record.

            * **Enables:** inspect the keys in `parameters` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the SQL Task object returned for Job Runs; it is interpreted at one SQL Task record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-query-1e5b3361361f" title="Query" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.query`

            Query records the query details attached to this Job Runs record. It is needed to preserve the nested query relationship or details on the parent SQL Task record.

            * **Enables:** expand `query` to connect the containing SQL Task row to its returned query entries.
            * **Interpretation:** Databricks reports this value on the SQL Task object returned for Job Runs; it is one nested object per containing SQL Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-query-query-i-a509d6ad0e0f" title="Query ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.query.query_id`

            Query ID records ID of the SQL query. It is needed to refer to the same query across records without relying on display text.

            * **Enables:** match `query_id` to query references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the SQL Task Query object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-sql-task-warehouse-id-0c4f35c1faf9" title="Warehouse ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.sql_task.warehouse_id`

            Warehouse ID records ID of the SQL warehouse. It is needed to refer to the same warehouse across records without relying on display text.

            * **Enables:** match `warehouse_id` to warehouse references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the SQL Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-start-time-ba3da9275d41" title="Start Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.start_time`

            Start Time records timestamp in epoch ms when the task started. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Job Runs records by `start_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-state-a44080c252e9" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.state`

            State records the state details attached to this Job Runs record. It is needed to preserve the nested state relationship or details on the parent Run Task record.

            * **Enables:** expand `state` to connect the containing Run Task row to its returned state entries.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is one nested object per containing Run Task object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-tasks-task-key-27826da3c63a" title="Task Key" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.tasks.task_key`

            Task Key records unique key identifying the task within the job. It is needed to refer to the same task across records without relying on display text.

            * **Enables:** match `task_key` to task references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Run Task object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-trigger-bf34d6bb7451" title="Trigger" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.trigger`

            Trigger records the trigger supplied for this Job Runs record by Databricks. It is needed to distinguish Job Runs rows by the exact Databricks-returned trigger value.

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

          <Accordion id="provider-permission-field-databricks-job-runs-trigger-info-9b6f43cb8cdf" title="Trigger Info" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.trigger_info`

            Trigger Info records the trigger info details attached to this Job Runs record. It is needed to preserve the nested trigger info relationship or details on the parent Job Run record.

            * **Enables:** expand `trigger_info` to connect the containing Job Run row to its returned trigger info entries.
            * **Interpretation:** Databricks reports this value on the Job Run object returned for Job Runs; it is one nested object per containing Job Run object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-job-runs-trigger-info-run-id-5ace9d6cd62a" title="Run ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `job_runs.trigger_info.run_id`

            Run ID records run ID of the triggering run. It is needed to refer to the same run across records without relying on display text.

            * **Enables:** match `run_id` to run references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Trigger Info object returned for Job Runs; it is an identifier, not a measured quantity.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-databricks-jobs-695c4f5a241e" title="Jobs" icon="list-check" iconType="sharp-duotone-solid">
        Developer identifier: `jobs`

        Jobs covers jobs defined in the Databricks workspace. Provides job configuration, schedule, and metadata. Paginated via `next_page_token`.

        * **Enables:** inventory defined jobs and connect each job to its creator, schedule, tasks, and run-as identity where returned.
        * **Scope:** Lists all jobs defined in the Databricks workspace. Provides job configuration, schedule, and metadata. Paginated via `next_page_token`; the connector reads `/api/2.1/jobs/list` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-jobs-created-time-79512d96dd57" title="Created Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.created_time`

            Created Time records timestamp when the job was created (epoch ms). It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Jobs records by `created_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Jobs object returned for Jobs; its unit or granularity is epoch milliseconds; the connector also declares it for record ordering; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-jobs-creator-user-name-b4b4c6a27f66" title="Creator User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.creator_user_name`

            Creator User Name records user who created the job. It is needed to attribute this Jobs row to the returned person, account, or organization reference.

            * **Enables:** attribute the Jobs row to the returned person or account and match the exact `creator_user_name` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Databricks Jobs object returned for Jobs; it is interpreted at one Databricks Jobs record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-jobs-format-42c82fa4bde5" title="Format" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.format`

            Format records format of the job (`SINGLE_TASK`, `MULTI_TASK`). It is needed to distinguish Jobs rows by the exact Databricks-returned format value.

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

          <Accordion id="provider-permission-field-databricks-jobs-job-id-eb7884d967d6" title="Job ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.job_id`

            Job ID records unique identifier for the job. It is needed to distinguish repeated deliveries of the same Jobs row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-jobs-run-as-owner-0a05e29cb316" title="Run As Owner" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.run_as_owner`

            Run As Owner records whether the job runs as the owner. It is needed to distinguish Jobs rows by the exact Databricks-returned run as owner value.

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

          <Accordion id="provider-permission-field-databricks-jobs-run-as-user-name-e8174c2e2ce0" title="Run As User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.run_as_user_name`

            Run As User Name records user the job runs as. It is needed to attribute this Jobs row to the returned person, account, or organization reference.

            * **Enables:** attribute the Jobs row to the returned person or account and match the exact `run_as_user_name` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Databricks Jobs object returned for Jobs; it is interpreted at one Databricks Jobs record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-jobs-settings-e6e600c0a2af" title="Settings" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.settings`

            Settings records job settings including tasks, schedule, clusters, and notifications. It is needed to compare the exact settings configuration returned for this Databricks Jobs record.

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

          <Accordion id="provider-permission-field-databricks-jobs-trigger-4340edc03cf0" title="Trigger" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `jobs.trigger`

            Trigger records trigger configuration for the job. It is needed to distinguish Jobs rows by the exact Databricks-returned trigger value.

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

      <Accordion id="provider-permission-tap-databricks-pipelines-9e92fed053f9" title="Pipelines" icon="route" iconType="sharp-duotone-solid">
        Developer identifier: `pipelines`

        Pipelines covers delta Live Tables (DLT) pipelines in the Databricks workspace. Provides pipeline configuration, state, and metadata.

        * **Enables:** inventory returned pipeline definitions and compare their creator, configuration, state, and last reported update.
        * **Scope:** Lists all Delta Live Tables (DLT) pipelines in the Databricks workspace. Provides pipeline configuration, state, and metadata; the connector reads `/api/{apiVersion}/pipelines` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-pipelines-budget-policy-id-78891ba27bfb" title="Budget Policy ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.budget_policy_id`

            Budget Policy ID records ID of the budget policy associated with the pipeline. 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 `budget_policy_id` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; 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-databricks-pipelines-catalog-03ccf2af9c54" title="Catalog" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.catalog`

            Catalog records Unity Catalog name associated with the pipeline. It is needed to compare the returned catalog for individual Pipelines rows and select rows with a specific `catalog` value.

            * **Enables:** trace the catalog relationship returned in `catalog` from the Pipeline row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-cause-abbeec49c405" title="Cause" icon="headset" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.cause`

            Cause records cause of the current pipeline state (e.g., `USER_ACTION`, `API_CALL`). It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `cause` among Pipelines records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline record per row; the value is a Databricks-returned or configured label at the Pipeline grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-channel-863d98a8b3c4" title="Channel" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.channel`

            Channel records release channel for the pipeline runtime (e.g., CURRENT, PREVIEW). It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `channel` among Pipelines records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline record per row; the value is a Databricks-returned or configured label at the Pipeline grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-cluster-id-a364de8c94da" title="Cluster ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.cluster_id`

            Cluster ID records ID of the cluster used by the pipeline. It is needed to refer to the same cluster across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-9128a93210e1" title="Clusters" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters`

            Clusters records cluster configurations for the pipeline. It is needed to preserve the nested clusters relationship or details on the parent Pipeline record.

            * **Enables:** expand `clusters` to connect the containing Pipeline row to its returned clusters entries.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one returned collection per containing Pipeline object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-apply-policy-defau-0436b2abc4b2" title="Apply Policy Default Values" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.apply_policy_default_values`

            Apply Policy Default Values records whether to apply default values from the cluster policy. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Pipelines rows with the exact `apply_policy_default_values` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-autoscale-9af8cb630445" title="Autoscale" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.autoscale`

            Autoscale records autoscaling configuration for the cluster. It is needed to preserve the nested autoscale relationship or details on the parent Pipeline Cluster record.

            * **Enables:** expand `autoscale` to connect the containing Pipeline Cluster row to its returned autoscale entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is one nested object per containing Pipeline Cluster object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-autoscale-max-work-2287eba00326" title="Max Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.autoscale.max_workers`

            Max Workers records maximum number of workers. It is needed to measure the Databricks-reported number of max workers at one Autoscale Config record per row.

            * **Enables:** measure and compare the Databricks-reported number of max workers in `max_workers` at one Autoscale Config record per row.
            * **Interpretation:** Databricks reports this value on the Autoscale Config object returned for Pipelines; it is a Databricks-reported count at one Autoscale Config record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-autoscale-min-work-411daca866fc" title="Min Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.autoscale.min_workers`

            Min Workers records minimum number of workers. It is needed to measure the Databricks-reported number of min workers at one Autoscale Config record per row.

            * **Enables:** measure and compare the Databricks-reported number of min workers in `min_workers` at one Autoscale Config record per row.
            * **Interpretation:** Databricks reports this value on the Autoscale Config object returned for Pipelines; it is a Databricks-reported count at one Autoscale Config record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-autoscale-mode-3685f2866387" title="Mode" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.autoscale.mode`

            Mode records autoscale mode (e.g., LEGACY, ENHANCED). It is needed to distinguish Pipelines rows by the exact Databricks-returned mode value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-aws-attributes-8c62ea7efaef" title="AWS Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.aws_attributes`

            AWS Attributes records AWS-specific cluster attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `aws_attributes` and associate them with the containing Pipelines record.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-azure-attributes-2d72ec12820f" title="Azure Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.azure_attributes`

            Azure Attributes records azure-specific cluster attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `azure_attributes` and associate them with the containing Pipelines record.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-custom-tags-c2e8c597ed19" title="Custom Tags" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.custom_tags`

            Custom Tags records custom tags applied to the cluster. It is needed to distinguish Pipelines rows by the exact Databricks-returned custom tags value.

            * **Enables:** separate Pipelines rows by the exact Databricks-returned `custom_tags` label when comparing custom tags.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; the schema uses the `Generic.JSON` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-driver-instance-po-c7c64f2f7205" title="Driver Instance Pool ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.driver_instance_pool_id`

            Driver Instance Pool ID records instance pool ID for the driver. It is needed to refer to the same driver instance pool across records without relying on display text.

            * **Enables:** match `driver_instance_pool_id` to driver instance pool references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-driver-node-type-i-50078c1d1870" title="Driver Node Type ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.driver_node_type_id`

            Driver Node Type ID records node type ID for the cluster driver. It is needed to refer to the same driver node type across records without relying on display text.

            * **Enables:** match `driver_node_type_id` to driver node type references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is an identifier, not a measured quantity; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-gcp-attributes-429c450e734d" title="GCP Attributes" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.gcp_attributes`

            GCP Attributes records GCP-specific cluster attributes. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `gcp_attributes` and associate them with the containing Pipelines record.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-init-scripts-5561f8c69294" title="Init Scripts" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.init_scripts`

            Init Scripts records init scripts for the cluster. It is needed to preserve the nested init scripts relationship or details on the parent Pipeline Cluster record.

            * **Enables:** expand `init_scripts` to connect the containing Pipeline Cluster row to its returned init scripts entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is one returned collection per containing Pipeline Cluster object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-instance-pool-id-4dcf947fda00" title="Instance Pool ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.instance_pool_id`

            Instance Pool ID records instance pool ID for the cluster. It is needed to refer to the same instance pool across records without relying on display text.

            * **Enables:** match `instance_pool_id` to instance pool references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-label-0a2f02f89454" title="Label" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.label`

            Label records label for the cluster configuration (e.g., default, maintenance). It is needed to compare the exact label configuration returned for this Pipeline Cluster record.

            * **Enables:** compare the exact `label` configuration returned for each Pipeline Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-node-type-id-659b7980aad1" title="Node Type ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.node_type_id`

            Node Type ID records node type ID for the cluster workers. It is needed to measure the Databricks-reported number of node type id at one Pipeline Cluster record per row.

            * **Enables:** measure and compare the Databricks-reported number of node type id in `node_type_id` at one Pipeline Cluster record per row.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is a Databricks-reported count at one Pipeline Cluster record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-num-workers-9850b1beef45" title="Num Workers" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.num_workers`

            Num Workers records fixed number of workers for the cluster. It is needed to measure the Databricks-reported number of num workers at one Pipeline Cluster record per row.

            * **Enables:** measure and compare the Databricks-reported number of num workers in `num_workers` at one Pipeline Cluster record per row.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is a Databricks-reported count at one Pipeline Cluster record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-policy-id-f2a02c56bc1c" title="Policy ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.policy_id`

            Policy ID records cluster policy ID. 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 `policy_id` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; 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-databricks-pipelines-clusters-spark-conf-ea8c3a4c0414" title="Spark Conf" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.spark_conf`

            Spark Conf records spark configuration key-value pairs. It is needed to compare the exact spark conf configuration returned for this Pipeline Cluster record.

            * **Enables:** compare the exact `spark_conf` configuration returned for each Pipeline Cluster record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-spark-env-vars-b80debdfaeb0" title="Spark Env Vars" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.spark_env_vars`

            Spark Env Vars records spark environment variables. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Pipeline Cluster record.

            * **Enables:** inspect the keys in `spark_env_vars` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is interpreted at one Pipeline Cluster record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-clusters-ssh-public-keys-398f2840a7e3" title="SSH Public Keys" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.clusters.ssh_public_keys`

            SSH Public Keys records SSH public keys for the cluster. It is needed to preserve the nested ssh public keys relationship or details on the parent Pipeline Cluster record.

            * **Enables:** expand `ssh_public_keys` to connect the containing Pipeline Cluster row to its returned ssh public keys entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Cluster object returned for Pipelines; it is one returned collection per containing Pipeline Cluster object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-configuration-4a578223de49" title="Configuration" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.configuration`

            Configuration records arbitrary key-value configuration settings for the pipeline. It is needed to compare the exact configuration configuration returned for this Pipeline record.

            * **Enables:** compare the exact `configuration` configuration returned for each Pipeline record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-continuous-1633984930ea" title="Continuous" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.continuous`

            Continuous records whether the pipeline runs in continuous mode. It is needed to distinguish Pipelines rows by the exact Databricks-returned continuous value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-creation-time-e199417843a9" title="Creation Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.creation_time`

            Creation Time records timestamp when the pipeline was created, in epoch milliseconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Pipelines records by `creation_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-creator-user-name-256f6d74b766" title="Creator User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.creator_user_name`

            Creator User Name records username of the user who created the pipeline. It is needed to attribute this Pipelines row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-pipelines-development-7aa1a38117ef" title="Development" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.development`

            Development records whether the pipeline is in development mode. It is needed to distinguish Pipelines rows by the exact Databricks-returned development value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-edition-eed9d4072e52" title="Edition" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.edition`

            Edition records product edition of the pipeline (e.g., CORE, PRO, ADVANCED). It is needed to compare the exact edition configuration returned for this Pipeline record.

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

          <Accordion id="provider-permission-field-databricks-pipelines-filters-21ba46f07d97" title="Filters" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.filters`

            Filters records filters applied to the pipeline datasets. It is needed to preserve the nested filters relationship or details on the parent Pipeline record.

            * **Enables:** expand `filters` to connect the containing Pipeline row to its returned filters entries.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one nested object per containing Pipeline object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-filters-exclude-2373286e9488" title="Exclude" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.filters.exclude`

            Exclude records list of dataset name patterns to exclude. It is needed to preserve the nested exclude relationship or details on the parent Pipeline Filters record.

            * **Enables:** expand `exclude` to connect the containing Pipeline Filters row to its returned exclude entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Filters object returned for Pipelines; it is one returned collection per containing Pipeline Filters object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-filters-include-7910bbcf6ca3" title="Include" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.filters.include`

            Include records list of dataset name patterns to include. It is needed to preserve the nested include relationship or details on the parent Pipeline Filters record.

            * **Enables:** expand `include` to connect the containing Pipeline Filters row to its returned include entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Filters object returned for Pipelines; it is one returned collection per containing Pipeline Filters object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-health-de91cbd16e06" title="Health" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.health`

            Health records health status of the pipeline. It is needed to distinguish Pipelines rows by the exact Databricks-returned health value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-last-modified-a591c633b0f8" title="Last Modified" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.last_modified`

            Last Modified records timestamp when the pipeline was last modified. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Pipelines records by `last_modified`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline record per row; the connector also declares it for record ordering.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-29c521aa85b2" title="Latest Updates" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates`

            Latest Updates records latest update details for the pipeline. It is needed to preserve the nested latest updates relationship or details on the parent Pipeline record.

            * **Enables:** expand `latest_updates` to connect the containing Pipeline row to its returned latest updates entries.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one returned collection per containing Pipeline object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-cause-af9d6d629c5f" title="Cause" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.cause`

            Cause records cause that triggered the update. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `cause` among Pipelines records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Pipeline Update object returned for Pipelines; it is interpreted at one Pipeline Update record per row; the value is a Databricks-returned or configured label at the Pipeline Update grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-config-c839717f5289" title="Config" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.config`

            Config records configuration overrides for this update. It is needed to compare the exact config configuration returned for this Pipeline Update record.

            * **Enables:** compare the exact `config` configuration returned for each Pipeline Update record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Pipeline Update object returned for Pipelines; it is interpreted at one Pipeline Update record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-creation-tim-44390a1c4f37" title="Creation Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.creation_time`

            Creation Time records timestamp when the update was created, in epoch milliseconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Pipelines records by `creation_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Pipeline Update object returned for Pipelines; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-full-refresh-70bf3fffadd1" title="Full Refresh" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.full_refresh`

            Full Refresh records whether this update was a full refresh. It is needed to distinguish Pipelines rows by the exact Databricks-returned full refresh value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-full-refresh-e5735183e97d" title="Full Refresh Selection" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.full_refresh_selection`

            Full Refresh Selection records list of tables selected for full refresh. It is needed to preserve the nested full refresh selection relationship or details on the parent Pipeline Update record.

            * **Enables:** expand `full_refresh_selection` to connect the containing Pipeline Update row to its returned full refresh selection entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Update object returned for Pipelines; it is one returned collection per containing Pipeline Update object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-refresh-sele-0251dd990b3d" title="Refresh Selection" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.refresh_selection`

            Refresh Selection records list of tables selected for refresh. It is needed to preserve the nested refresh selection relationship or details on the parent Pipeline Update record.

            * **Enables:** expand `refresh_selection` to connect the containing Pipeline Update row to its returned refresh selection entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Update object returned for Pipelines; it is one returned collection per containing Pipeline Update object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-state-21a047c6746e" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.state`

            State records state of the update. It is needed to distinguish Pipelines rows by the exact Databricks-returned state value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-update-id-067e3810e8f4" title="Update ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.update_id`

            Update ID records unique identifier for the update. It is needed to refer to the same update across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-pipelines-latest-updates-validate-onl-50685d99a938" title="Validate Only" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.latest_updates.validate_only`

            Validate Only records whether the update was a validation-only run. It is needed to distinguish Pipelines rows by the exact Databricks-returned validate only value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-3249d0af4488" title="Libraries" icon="books" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries`

            Libraries records list of library/notebook configurations for the pipeline. It is needed to preserve the nested libraries relationship or details on the parent Pipeline record.

            * **Enables:** expand `libraries` to connect the containing Pipeline row to its returned libraries entries.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one returned collection per containing Pipeline object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-file-efdef700725d" title="File" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.file`

            File records file reference for the library. It is needed to preserve the nested file relationship or details on the parent Pipeline Library record.

            * **Enables:** expand `file` to connect the containing Pipeline Library row to its returned file entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Library object returned for Pipelines; it is one nested object per containing Pipeline Library object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-file-path-a4fe6720c1e4" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.file.path`

            Path records path to the file. It is needed to compare the returned path for individual Pipelines rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the File Reference row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the File Reference object returned for Pipelines; it is interpreted at one File Reference record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-jar-087716abd94f" title="Jar" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.jar`

            Jar records path to a JAR library. It is needed to compare the returned jar for individual Pipelines rows and select rows with a specific `jar` value.

            * **Enables:** trace the jar relationship returned in `jar` from the Pipeline Library row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Pipeline Library object returned for Pipelines; it is interpreted at one Pipeline Library record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-maven-3da54b6ce6fb" title="Maven" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.maven`

            Maven records maven library coordinates. It is needed to preserve the nested maven relationship or details on the parent Pipeline Library record.

            * **Enables:** expand `maven` to connect the containing Pipeline Library row to its returned maven entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Library object returned for Pipelines; its unit or granularity is provider-reported geographic coordinates.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-maven-coordinates-42921417e849" title="Coordinates" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.maven.coordinates`

            Coordinates records maven coordinates (groupId:artifactId:version). It is needed to compare the exact coordinates configuration returned for this Maven Library record.

            * **Enables:** compare the exact `coordinates` configuration returned for each Maven Library record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Maven Library object returned for Pipelines; its unit or granularity is provider-reported geographic coordinates.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-maven-exclusions-162636efb18b" title="Exclusions" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.maven.exclusions`

            Exclusions records list of Maven dependency exclusions. It is needed to preserve the nested exclusions relationship or details on the parent Maven Library record.

            * **Enables:** expand `exclusions` to connect the containing Maven Library row to its returned exclusions entries.
            * **Interpretation:** Databricks reports this value on the Maven Library object returned for Pipelines; it is one returned collection per containing Maven Library object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-maven-repo-da93167ff42a" title="Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.maven.repo`

            Repo records maven repository URL. It is needed to reproduce the returned code or dependency configuration for this Pipelines record.

            * **Enables:** use `repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** Databricks reports this value on the Maven Library object returned for Pipelines; it is interpreted at one Maven Library 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-databricks-pipelines-libraries-notebook-0c9b5ef388f7" title="Notebook" icon="books" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.notebook`

            Notebook records notebook reference for the library. It is needed to preserve the nested notebook relationship or details on the parent Pipeline Library record.

            * **Enables:** expand `notebook` to connect the containing Pipeline Library row to its returned notebook entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Library object returned for Pipelines; it is one nested object per containing Pipeline Library object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-libraries-notebook-path-3aa47260a294" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.libraries.notebook.path`

            Path records workspace path to the notebook. It is needed to compare the returned path for individual Pipelines rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the Notebook Reference row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Notebook Reference object returned for Pipelines; it is interpreted at one Notebook Reference record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-name-ca74c7c57fe1" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.name`

            Name records human-readable name of the pipeline. It is needed to compare the returned name for individual Pipelines rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-notifications-4583e352385e" title="Notifications" icon="megaphone" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.notifications`

            Notifications records notification configurations for pipeline events. It is needed to preserve the nested notifications relationship or details on the parent Pipeline record.

            * **Enables:** expand `notifications` to connect the containing Pipeline row to its returned notifications entries.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one returned collection per containing Pipeline object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-notifications-alerts-7eacf870253d" title="Alerts" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.notifications.alerts`

            Alerts records list of alert types that trigger notifications (e.g., on-update-failure, on-update-success, on-flow-failure). It is needed to preserve the nested alerts relationship or details on the parent Pipeline Notification record.

            * **Enables:** expand `alerts` to connect the containing Pipeline Notification row to its returned alerts entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Notification object returned for Pipelines; it is one returned collection per containing Pipeline Notification object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-notifications-email-recipie-1583796f5172" title="Email Recipients" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.notifications.email_recipients`

            Email Recipients records list of email addresses to notify. It is needed to preserve the nested email recipients relationship or details on the parent Pipeline Notification record.

            * **Enables:** expand `email_recipients` to connect the containing Pipeline Notification row to its returned email recipients entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Notification object returned for Pipelines; it is one returned collection per containing Pipeline Notification object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-permissions-2421951350cb" title="Permissions" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.permissions`

            Permissions records access control permissions for the pipeline. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `permissions` to examine the returned permissions details for the containing Pipeline record.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one returned collection per containing Pipeline object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-permissions-group-name-618aab409197" title="Group Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.permissions.group_name`

            Group Name records group name granted the permission. 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 `group_name` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline Permission object returned for Pipelines; it is interpreted at one Pipeline Permission 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-databricks-pipelines-permissions-permission-leve-498a0fdf4000" title="Permission Level" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.permissions.permission_level`

            Permission Level records permission level (e.g., `CAN_MANAGE`, `CAN_RUN`, `CAN_VIEW`, `IS_OWNER`). 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 `permission_level` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline Permission object returned for Pipelines; it is interpreted at one Pipeline Permission 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-databricks-pipelines-permissions-service-princip-178404990d8b" title="Service Principal Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.permissions.service_principal_name`

            Service Principal Name records service principal name granted the permission. 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 `service_principal_name` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline Permission object returned for Pipelines; it is interpreted at one Pipeline Permission 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-databricks-pipelines-permissions-user-name-37502c174279" title="User Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.permissions.user_name`

            User Name records username granted the permission. 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_name` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline Permission object returned for Pipelines; it is interpreted at one Pipeline Permission 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-databricks-pipelines-photon-722821f9fb4b" title="Photon" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.photon`

            Photon records whether Photon acceleration is enabled for the pipeline. It is needed to distinguish Pipelines rows by the exact Databricks-returned photon value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-pipeline-id-c20d5ae968f9" title="Pipeline ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.pipeline_id`

            Pipeline ID records unique identifier for the pipeline. It is needed to distinguish repeated deliveries of the same Pipelines row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-pipelines-run-as-user-name-320c7d78c7ac" title="Run As User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.run_as_user_name`

            Run As User Name records username of the user the pipeline runs as. It is needed to attribute this Pipelines row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-pipelines-serverless-dac19ed7e1eb" title="Serverless" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.serverless`

            Serverless records whether the pipeline uses serverless compute. It is needed to distinguish Pipelines rows by the exact Databricks-returned serverless value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-spec-aed67407fb8b" title="Spec" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec`

            Spec records full pipeline specification/definition. It is needed to preserve the nested spec relationship or details on the parent Pipeline record.

            * **Enables:** expand `spec` to connect the containing Pipeline row to its returned spec entries.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is one nested object per containing Pipeline object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-budget-policy-id-7498eda1ff9a" title="Budget Policy ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.budget_policy_id`

            Budget Policy ID records budget policy ID. 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 `budget_policy_id` access value with the resource, account, or membership represented by the same Pipelines row.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; 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-databricks-pipelines-spec-catalog-585f41422adf" title="Catalog" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.catalog`

            Catalog records Unity Catalog name. It is needed to compare the returned catalog for individual Pipelines rows and select rows with a specific `catalog` value.

            * **Enables:** trace the catalog relationship returned in `catalog` from the Pipeline Spec row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is interpreted at one Pipeline Spec record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-channel-0cb64fd171b9" title="Channel" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.channel`

            Channel records release channel. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `channel` among Pipelines records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is interpreted at one Pipeline Spec record per row; the value is a Databricks-returned or configured label at the Pipeline Spec grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-clusters-b6ec1aa2f574" title="Clusters" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.clusters`

            Clusters records cluster configurations. It is needed to preserve the nested clusters relationship or details on the parent Pipeline Spec record.

            * **Enables:** expand `clusters` to connect the containing Pipeline Spec row to its returned clusters entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is one returned collection per containing Pipeline Spec object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-configuration-bbcb6d420ced" title="Configuration" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.configuration`

            Configuration records pipeline configuration key-value pairs. It is needed to compare the exact configuration configuration returned for this Pipeline Spec record.

            * **Enables:** compare the exact `configuration` configuration returned for each Pipeline Spec record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is interpreted at one Pipeline Spec record per row; the schema uses the `Generic.JSON` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-continuous-5edb9d4fb4cd" title="Continuous" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.continuous`

            Continuous records whether the pipeline runs continuously. It is needed to distinguish Pipelines rows by the exact Databricks-returned continuous value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-spec-development-16f2d1c0db8c" title="Development" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.development`

            Development records whether the pipeline is in development mode. It is needed to distinguish Pipelines rows by the exact Databricks-returned development value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-spec-edition-d6a1e9475929" title="Edition" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.edition`

            Edition records product edition. It is needed to compare the exact edition configuration returned for this Pipeline Spec record.

            * **Enables:** compare the exact `edition` configuration returned for each Pipeline Spec record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is interpreted at one Pipeline Spec record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-filters-f41bba8d8e89" title="Filters" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.filters`

            Filters records dataset filters. It is needed to preserve the nested filters relationship or details on the parent Pipeline Spec record.

            * **Enables:** expand `filters` to connect the containing Pipeline Spec row to its returned filters entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is one nested object per containing Pipeline Spec object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-id-afcac3ce20ff" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.id`

            ID records pipeline ID in the spec. It is needed to refer to the same pipeline spec across records without relying on display text.

            * **Enables:** match `id` to pipeline spec references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-libraries-6c6a72f1e0c2" title="Libraries" icon="books" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.libraries`

            Libraries records library configurations. It is needed to preserve the nested libraries relationship or details on the parent Pipeline Spec record.

            * **Enables:** expand `libraries` to connect the containing Pipeline Spec row to its returned libraries entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is one returned collection per containing Pipeline Spec object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-name-d47543249a39" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.name`

            Name records pipeline name in the spec. It is needed to compare the returned name for individual Pipelines rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-spec-notifications-5da310279791" title="Notifications" icon="megaphone" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.notifications`

            Notifications records notification configurations. It is needed to preserve the nested notifications relationship or details on the parent Pipeline Spec record.

            * **Enables:** expand `notifications` to connect the containing Pipeline Spec row to its returned notifications entries.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is one returned collection per containing Pipeline Spec object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-spec-photon-e3762c3af8f1" title="Photon" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.photon`

            Photon records whether Photon is enabled. It is needed to distinguish Pipelines rows by the exact Databricks-returned photon value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-spec-serverless-7dd5153284cb" title="Serverless" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.serverless`

            Serverless records whether serverless compute is used. It is needed to distinguish Pipelines rows by the exact Databricks-returned serverless value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-spec-storage-d40f1657f938" title="Storage" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.storage`

            Storage records root storage location. It is needed to retain the exact Databricks resource or external link reported for this Pipelines record.

            * **Enables:** open or correlate the resource named by `storage` while retaining the containing Pipeline Spec row as provenance.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is interpreted at one Pipeline Spec 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-databricks-pipelines-spec-target-4be16a0d15fb" title="Target" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.spec.target`

            Target records target schema or database. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `target` among Pipelines records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Pipeline Spec object returned for Pipelines; it is interpreted at one Pipeline Spec record per row; the value is a Databricks-returned or configured label at the Pipeline Spec grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-state-e4810c30b725" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.state`

            State records current state of the pipeline. It is needed to distinguish Pipelines rows by the exact Databricks-returned state value.

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

          <Accordion id="provider-permission-field-databricks-pipelines-storage-46751bd3acc2" title="Storage" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.storage`

            Storage records root storage location for the pipeline data. It is needed to retain the exact Databricks resource or external link reported for this Pipelines record.

            * **Enables:** open or correlate the resource named by `storage` while retaining the containing Pipeline row as provenance.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline 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-databricks-pipelines-target-fa9d34f7d230" title="Target" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.target`

            Target records target schema or database for the pipeline output. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `target` among Pipelines records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is interpreted at one Pipeline record per row; the value is a Databricks-returned or configured label at the Pipeline grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-pipelines-url-abe97f4c6320" title="URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.url`

            URL records URL to the pipeline in the Databricks workspace UI. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `url` while retaining the containing Pipelines record as provenance.
            * **Interpretation:** Databricks reports this value on the Pipeline object returned for Pipelines; it is link at one Pipeline record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-databricks-query-history-90af3e0d261a" title="Query History" icon="timeline" iconType="sharp-duotone-solid">
        Developer identifier: `query_history`

        Query History covers SQL and serverless compute query execution history from system.query.history. Includes executor identity, statement text, timing, client application, and `query_source` linkage to notebooks, jobs, and dashboards. Queried via the SQL Statement Execution API. Requires USE CATALOG on system, USE SCHEMA on system.query, and SELECT on system.query.history.

        * **Enables:** correlate each returned statement with its executor, compute resource, status, row counts, and execution times.
        * **Scope:** SQL and serverless compute query execution history from system.query.history. Includes executor identity, statement text, timing, client application, and `query_source` linkage to notebooks, jobs, and dashboards. Queried via the SQL Statement Execution API. Requires USE CATALOG on system, USE SCHEMA on system.query, and SELECT on system.query.history; the connector reads `/api/2.0/sql/statements` as an event stream in incremental mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-query-history-account-id-303215c6de2c" title="Account ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.account_id`

            Account ID records Databricks account ID. It is needed to refer to the same account across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-query-history-client-application-989deeae76b2" title="Client Application" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.client_application`

            Client Application records client application that submitted the query. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `client_application` among Query History records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is interpreted at one Databricks Query History record per row; the value is a Databricks-returned or configured label at the Databricks Query History grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-client-driver-8ee9303342a4" title="Client Driver" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.client_driver`

            Client Driver records connector or driver used to run the query. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `client_driver` among Query History records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is interpreted at one Databricks Query History record per row; the value is a Databricks-returned or configured label at the Databricks Query History grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-compute-c461d0cb1a9e" title="Compute" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.compute`

            Compute records compute resource used to run the statement. It is needed to preserve the nested compute relationship or details on the parent Databricks Query History record.

            * **Enables:** expand `compute` to connect the containing Databricks Query History row to its returned compute entries.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is one nested object per containing Databricks Query History object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-compute-cluster-id-80ba93adc5fc" title="Cluster ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.compute.cluster_id`

            Cluster ID records cluster ID when applicable. It is needed to refer to the same cluster across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-query-history-compute-type-62850f0f0cc3" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.compute.type`

            Type records WAREHOUSE or `SERVERLESS_COMPUTE`. It is needed to distinguish Query History rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-query-history-compute-warehouse-id-7d4bda09108b" title="Warehouse ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.compute.warehouse_id`

            Warehouse ID records SQL warehouse ID when applicable. It is needed to refer to the same warehouse across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-query-history-end-time-6ecba646701c" title="End Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.end_time`

            End Time records UTC timestamp when execution ended. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-databricks-query-history-error-message-7734473781f6" title="Error Message" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.error_message`

            Error Message records error message when execution failed. It is needed to inspect the exact error message included with this record.

            * **Enables:** inspect the error message returned in `error_message` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is error message at one Databricks Query History record per row; this is only the content included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-executed-as-251c496a9bbd" title="Executed As" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.executed_as`

            Executed As records user or service principal whose privilege was used. 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 `executed_as` access value with the resource, account, or membership represented by the same Query History row.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is interpreted at one Databricks Query History 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-databricks-query-history-executed-as-user-id-4654299854d8" title="Executed As User ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.executed_as_user_id`

            Executed As User ID records ID of the executed-as principal. It is needed to refer to the same executed as user across records without relying on display text.

            * **Enables:** match `executed_as_user_id` to executed as user references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-executed-by-fb20bf6bcd72" title="Executed By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.executed_by`

            Executed By records email or username of the user who ran the statement. It is needed to attribute this Query History row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-query-history-executed-by-user-id-a11f074fc108" title="Executed By User ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.executed_by_user_id`

            Executed By User ID records user ID of the executor. It is needed to refer to the same executed by user across records without relying on display text.

            * **Enables:** match `executed_by_user_id` to executed by user references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-execution-duration-ms-b7399aea63fa" title="Execution Duration Ms" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.execution_duration_ms`

            Execution Duration Ms records time spent executing the statement in milliseconds. It is needed to measure the exact duration reported for one Databricks Query History record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `execution_duration_ms` per Databricks Query History record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-execution-status-b0e03968d60b" title="Execution Status" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.execution_status`

            Execution Status records FINISHED, FAILED, or CANCELED. It is needed to distinguish Query History rows by the exact Databricks-returned execution status value.

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

          <Accordion id="provider-permission-field-databricks-query-history-produced-rows-f4ae48522839" title="Produced Rows" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.produced_rows`

            Produced Rows records rows returned by the statement. It is needed to measure the Databricks-reported number of produced rows at one Databricks Query History record per row.

            * **Enables:** measure and compare the Databricks-reported number of produced rows in `produced_rows` at one Databricks Query History record per row.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is a Databricks-reported count at one Databricks Query History record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-query-source-0d569c19ec3a" title="Query Source" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.query_source`

            Query Source records Databricks entities involved in the query execution (JSON string under the `JSON_ARRAY` result format). It is needed to distinguish Query History rows by the exact Databricks-returned query source value.

            * **Enables:** separate Query History rows by the exact Databricks-returned `query_source` label when comparing query source.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is interpreted at one Databricks Query History record per row; the schema uses the `Generic.JSON` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-query-tags-7fdb812d275d" title="Query Tags" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.query_tags`

            Query Tags records custom key-value tags applied to the query. It is needed to distinguish Query History rows by the exact Databricks-returned query tags value.

            * **Enables:** separate Query History rows by the exact Databricks-returned `query_tags` label when comparing query tags.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is interpreted at one Databricks Query History record per row; the schema uses the `Generic.JSON` scalar; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-read-rows-69b78da63889" title="Read Rows" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.read_rows`

            Read Rows records rows read by the statement. It is needed to measure the Databricks-reported number of read rows at one Databricks Query History record per row.

            * **Enables:** measure and compare the Databricks-reported number of read rows in `read_rows` at one Databricks Query History record per row.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is a Databricks-reported count at one Databricks Query History record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-session-id-044d8aa04863" title="Session ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.session_id`

            Session ID records spark session ID. 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 `session_id` access value with the resource, account, or membership represented by the same Query History row.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; 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-databricks-query-history-start-time-0dbb740c3e6f" title="Start Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.start_time`

            Start Time records UTC timestamp when execution started. Incremental sync cursor. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Query History records by `start_time`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is interpreted at one Databricks Query History 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.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-statement-id-b21b7fed5634" title="Statement ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.statement_id`

            Statement ID records unique statement execution identifier. It is needed to distinguish repeated deliveries of the same Query History row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-query-history-statement-text-2947ccd44857" title="Statement Text" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.statement_text`

            Statement Text records SQL statement text. May be empty when customer-managed keys encrypt system table fields. It is needed to inspect the exact SQL statement text included with this record.

            * **Enables:** inspect the SQL statement text returned in `statement_text` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; it is SQL statement text at one Databricks Query History record per row; availability and any truncation follow the limitation stated in the field description.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-statement-type-0d9e714b7a16" title="Statement Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.statement_type`

            Statement Type records statement type such as SELECT or INSERT. It is needed to distinguish Query History rows by the exact Databricks-returned statement type value.

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

          <Accordion id="provider-permission-field-databricks-query-history-total-duration-ms-201bc7af504a" title="Total Duration Ms" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.total_duration_ms`

            Total Duration Ms records total execution duration in milliseconds. It is needed to measure the exact duration reported for one Databricks Query History record using the Databricks duration encoding described by the field.

            * **Enables:** measure and compare `total_duration_ms` per Databricks Query History record in milliseconds.
            * **Interpretation:** Databricks reports this value on the Databricks Query History object returned for Query History; its unit or granularity is milliseconds.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-query-history-update-time-6ecd7069c693" title="Update Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.update_time`

            Update Time records last progress update timestamp. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-databricks-query-history-workspace-id-efa4e19dce45" title="Workspace ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `query_history.workspace_id`

            Workspace ID records workspace where the query ran. It is needed to refer to the same workspace across records without relying on display text.

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

      <Accordion id="provider-permission-tap-databricks-schemas-d90952a4f834" title="Schemas" icon="brackets-curly" iconType="sharp-duotone-solid">
        Developer identifier: `schemas`

        Schemas covers schemas within a specified Unity Catalog catalog. Requires `catalog_name` as a parent context field. Provides schema metadata including name, owner, and properties.

        * **Enables:** connect each returned schema to its parent catalog and compare its owner, storage reference, and browse-only or maintenance flags.
        * **Scope:** Lists all schemas within a specified Unity Catalog catalog. Requires `catalog_name` as a parent context field. Provides schema metadata including name, owner, and properties; the connector reads `/api/2.1/unity-catalog/schemas` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-schemas-parent-catalog-name-167b7d4a4742" title="Parent Catalog Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `schemas._parent_catalog_name`

            Parent Catalog Name records parent catalog name injected by the catalogs to schemas traversal parentContextFields. Not part of the upstream API response. It is needed to compare the returned parent catalog name for individual Schemas rows and select rows with a specific `_parent_catalog_name` value.

            * **Enables:** locate Schemas rows whose returned parent catalog name exactly matches `_parent_catalog_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks's child response does not supply this field; the connector injects parent context into each child row; it is interpreted at one Databricks Schema record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-browse-only-8b5cf7a68970" title="Browse Only" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.browse_only`

            Browse Only indicates whether the principal can only browse the schema metadata but cannot access its tables or views. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Schemas rows with the exact `browse_only` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is interpreted at one Databricks Schema record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-cache-version-info-dd360578e5b2" title="Cache Version Info" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.cache_version_info`

            Cache Version Info records the cache version info details attached to this Schemas record. It is needed to preserve the nested cache version info relationship or details on the parent Databricks Schema record.

            * **Enables:** expand `cache_version_info` to connect the containing Databricks Schema row to its returned cache version info entries.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is one nested object per containing Databricks Schema object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-cache-version-info-metastore--e95338997b1f" title="Metastore Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.cache_version_info.metastore_version`

            Metastore Version records metastore version cached for this object. It is needed to compare the exact metastore version configuration returned for this Cache Version Info record.

            * **Enables:** compare the exact `metastore_version` configuration returned for each Cache Version Info record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Cache Version Info object returned for Schemas; it is interpreted at one Cache Version Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-catalog-name-65e4da5a0acf" title="Catalog Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.catalog_name`

            Catalog Name records name of the parent catalog that contains this schema. It is needed to compare the returned catalog name for individual Schemas rows and select rows with a specific `catalog_name` value.

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

          <Accordion id="provider-permission-field-databricks-schemas-catalog-type-dc5abf333ed0" title="Catalog Type" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.catalog_type`

            Catalog Type records type of the parent catalog (e.g., `MANAGED_CATALOG`, `DELTASHARING_CATALOG`). It is needed to distinguish Schemas rows by the exact Databricks-returned catalog type value.

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

          <Accordion id="provider-permission-field-databricks-schemas-comment-27c5d880bfa0" title="Comment" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.comment`

            Comment records user-provided comment or description for the schema. It is needed to inspect the exact comment or journal text included with this record.

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

          <Accordion id="provider-permission-field-databricks-schemas-created-at-a3c165ce805e" title="Created At" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.created_at`

            Created At records timestamp in epoch milliseconds when the schema was created. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Schemas records by `created_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-created-by-368ab7a0fb2e" title="Created By" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.created_by`

            Created By records username or principal that created the schema. It is needed to attribute this Schemas row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-schemas-effective-auto-maintenance-fl-aaa1243ee2e2" title="Effective Auto Maintenance Flag" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_auto_maintenance_flag`

            Effective Auto Maintenance Flag records the effective auto maintenance flag details attached to this Schemas record. It is needed to preserve the nested effective auto maintenance flag relationship or details on the parent Databricks Schema record.

            * **Enables:** expand `effective_auto_maintenance_flag` to connect the containing Databricks Schema row to its returned effective auto maintenance flag entries.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is one nested object per containing Databricks Schema object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-auto-maintenance-fl-9bbb9ae95275" title="Inherited From Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_auto_maintenance_flag.inherited_from_name`

            Inherited From Name records the inherited from name supplied for this Schemas record by Databricks. It is needed to compare the returned inherited from name for individual Schemas rows and select rows with a specific `inherited_from_name` value.

            * **Enables:** locate Schemas rows whose returned inherited from name exactly matches `inherited_from_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Effective Auto Maintenance Flag object returned for Schemas; it is interpreted at one Effective Auto Maintenance Flag record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-auto-maintenance-fl-186824b1263a" title="Inherited From Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_auto_maintenance_flag.inherited_from_type`

            Inherited From Type records the inherited from type supplied for this Schemas record by Databricks. It is needed to distinguish Schemas rows by the exact Databricks-returned inherited from type value.

            * **Enables:** separate Schemas rows by the exact Databricks-returned `inherited_from_type` label when comparing inherited from type.
            * **Interpretation:** Databricks reports this value on the Effective Auto Maintenance Flag object returned for Schemas; it is interpreted at one Effective Auto Maintenance Flag record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-auto-maintenance-fl-857dea46616c" title="Value" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_auto_maintenance_flag.value`

            Value records the effective auto maintenance flag value supplied for this Schemas record by Databricks. It is needed to interpret the effective Databricks automatic-maintenance setting returned for this schema.

            * **Enables:** combine `value` with the sibling inheritance source type and name to explain the effective schema-maintenance setting.
            * **Interpretation:** Databricks reports this value on the Effective Auto Maintenance Flag object returned for Schemas; it is interpreted at one Effective Auto Maintenance Flag record per row; the value is a Databricks setting and inheritance result, not proof that maintenance work executed.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-predictive-optimiza-3d6453187c6d" title="Effective Predictive Optimization Flag" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_predictive_optimization_flag`

            Effective Predictive Optimization Flag records effective predictive optimization settings inherited or set on this schema. It is needed to preserve the nested effective predictive optimization flag relationship or details on the parent Databricks Schema record.

            * **Enables:** expand `effective_predictive_optimization_flag` to connect the containing Databricks Schema row to its returned effective predictive optimization flag entries.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is one nested object per containing Databricks Schema object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-predictive-optimiza-f3d43cb7f902" title="Inherited From Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_predictive_optimization_flag.inherited_from_name`

            Inherited From Name records the name of the object from which this flag was inherited. It is needed to compare the returned inherited from name for individual Schemas rows and select rows with a specific `inherited_from_name` value.

            * **Enables:** locate Schemas rows whose returned inherited from name exactly matches `inherited_from_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Effective Predictive Optimization object returned for Schemas; it is interpreted at one Effective Predictive Optimization record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-predictive-optimiza-733fa8ec373d" title="Inherited From Type" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_predictive_optimization_flag.inherited_from_type`

            Inherited From Type records the type of the object from which this flag was inherited (e.g., CATALOG, SCHEMA). It is needed to distinguish Schemas rows by the exact Databricks-returned inherited from type value.

            * **Enables:** separate Schemas rows by the exact Databricks-returned `inherited_from_type` label when comparing inherited from type.
            * **Interpretation:** Databricks reports this value on the Effective Predictive Optimization object returned for Schemas; it is interpreted at one Effective Predictive Optimization record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-effective-predictive-optimiza-f9c9c8493087" title="Value" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.effective_predictive_optimization_flag.value`

            Value records the effective value of the predictive optimization flag. It is needed to distinguish Schemas rows by the exact Databricks-returned value value.

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

          <Accordion id="provider-permission-field-databricks-schemas-enable-auto-maintenance-972f71d838fa" title="Enable Auto Maintenance" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.enable_auto_maintenance`

            Enable Auto Maintenance records whether auto-maintenance is enabled, disabled, or inherited. It is needed to distinguish Schemas rows by the exact Databricks-returned enable auto maintenance value.

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

          <Accordion id="provider-permission-field-databricks-schemas-enable-predictive-optimizatio-cb1f81fb076b" title="Enable Predictive Optimization" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.enable_predictive_optimization`

            Enable Predictive Optimization records whether predictive optimization is enabled, disabled, or inherited for this schema. It is needed to distinguish Schemas rows by the exact Databricks-returned enable predictive optimization value.

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

          <Accordion id="provider-permission-field-databricks-schemas-etag-8208f700b5bd" title="ETag" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.etag`

            ETag records entity tag for optimistic concurrency. It is needed to correlate the Databricks object version used for optimistic concurrency.

            * **Enables:** compare `etag` across observations of the same Databricks Schema identifier to detect a returned version change before a conditional update.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is interpreted at one Databricks Schema record per row; the entity tag is a version token, not a timestamp or proof that every intermediate update was observed.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-full-name-ccfcb82e46a9" title="Full Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.full_name`

            Full Name records full name of the schema in the format `catalog_name`.`schema_name`. It is needed to distinguish repeated deliveries of the same Schemas row using the declared ingestion key.

            * **Enables:** use `full_name` as the declared ingestion deduplication key for Schemas and match repeated rows carrying the same Databricks identifier.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is interpreted at one Databricks Schema record per row; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-metastore-id-82ebc1d96144" title="Metastore ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.metastore_id`

            Metastore ID records unique identifier of the metastore that contains this schema. It is needed to refer to the same metastore across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-schemas-metastore-version-50bb7b25b765" title="Metastore Version" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.metastore_version`

            Metastore Version records metastore version associated with this schema record. It is needed to compare the exact metastore version configuration returned for this Databricks Schema record.

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

          <Accordion id="provider-permission-field-databricks-schemas-name-5580c04a6ffe" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.name`

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

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

          <Accordion id="provider-permission-field-databricks-schemas-owner-235b3ea045e4" title="Owner" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.owner`

            Owner records owner of the schema (user or group). It is needed to attribute this Schemas row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-schemas-properties-e8b4e4c3f11b" title="Properties" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.properties`

            Properties records key-value properties associated with the schema. Contains arbitrary metadata. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `properties` and associate them with the containing Schemas record.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is interpreted at one Databricks Schema record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-provisioning-info-ba158443259a" title="Provisioning Info" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.provisioning_info`

            Provisioning Info records provisioning status information for the schema. It is needed to preserve the nested provisioning info relationship or details on the parent Databricks Schema record.

            * **Enables:** expand `provisioning_info` to connect the containing Databricks Schema row to its returned provisioning info entries.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is one nested object per containing Databricks Schema object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-provisioning-info-state-51d86537937e" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.provisioning_info.state`

            State records current provisioning state. It is needed to distinguish Schemas rows by the exact Databricks-returned state value.

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

          <Accordion id="provider-permission-field-databricks-schemas-related-entity-hints-51301aa5bc84" title="Related Entity Hints" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.related_entity_hints`

            Related Entity Hints records the related entity hints details attached to this Schemas record. It is needed to preserve the nested related entity hints relationship or details on the parent Databricks Schema record.

            * **Enables:** expand `related_entity_hints` to connect the containing Databricks Schema row to its returned related entity hints entries.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is one nested object per containing Databricks Schema object when present.

            Provider-defined fields may also be returned for this field.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-related-entity-hints-related--d3f082f8ebc5" title="Related Entity ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.related_entity_hints.related_entity_id`

            Related Entity ID records identifier of the related entity. It is needed to refer to the same related entity across records without relying on display text.

            * **Enables:** match `related_entity_id` to related entity references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Related Entity Hints object returned for Schemas; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-related-entity-hints-related--990320a97009" title="Related Entity Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.related_entity_hints.related_entity_type`

            Related Entity Type records type of the related entity. It is needed to distinguish Schemas rows by the exact Databricks-returned related entity type value.

            * **Enables:** separate Schemas rows by the exact Databricks-returned `related_entity_type` label when comparing related entity type.
            * **Interpretation:** Databricks reports this value on the Related Entity Hints object returned for Schemas; it is interpreted at one Related Entity Hints record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-schema-id-9d0cad236af5" title="Schema ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.schema_id`

            Schema ID records unique identifier of the schema. It is needed to refer to the same schema across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-schemas-securable-kind-d2bdce2a50cc" title="Securable Kind" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.securable_kind`

            Securable Kind records the kind of the securable object. It is needed to distinguish Schemas rows by the exact Databricks-returned securable kind value.

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

          <Accordion id="provider-permission-field-databricks-schemas-securable-type-83b21b40e261" title="Securable Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.securable_type`

            Securable Type records the type of the securable object. It is needed to distinguish Schemas rows by the exact Databricks-returned securable type value.

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

          <Accordion id="provider-permission-field-databricks-schemas-storage-location-47c42725c0af" title="Storage Location" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.storage_location`

            Storage Location records storage location URL for the schema. It is needed to preserve the Databricks-reported resource location link for the same record.

            * **Enables:** correlate the Databricks resource link in `storage_location` with its containing Databricks Schema row without treating the resource path as a statement of data residency.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is interpreted at one Databricks Schema record per row; the schema uses the `Network.Uri` scalar; the value is resource location link; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-storage-root-baac5f7baff0" title="Storage Root" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.storage_root`

            Storage Root records storage root URL for managed tables within this schema. It is needed to retain the exact Databricks resource or external link reported for this Schemas record.

            * **Enables:** open or correlate the resource named by `storage_root` while retaining the containing Databricks Schema row as provenance.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; it is interpreted at one Databricks Schema 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-databricks-schemas-updated-at-73bb023c7edb" title="Updated At" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.updated_at`

            Updated At records timestamp in epoch milliseconds when the schema was last updated. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Schemas records by `updated_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Schema object returned for Schemas; its unit or granularity is epoch milliseconds; the connector also declares it for record ordering; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-schemas-updated-by-661b9b375478" title="Updated By" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `schemas.updated_by`

            Updated By records username or principal that last updated the schema. It is needed to attribute this Schemas row to the returned person, account, or organization reference.

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

      <Accordion id="provider-permission-tap-databricks-service-principals-c72412fc6084" title="Service Principals" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `service_principals`

        Service Principals covers service principals in the Databricks workspace via the SCIM v2 API. Provides service principal identity and entitlement information.

        * **Enables:** map the Databricks accounts and memberships represented by Service Principals records and trace a returned access assignment to its account or group.
        * **Scope:** Lists all service principals in the Databricks workspace via the SCIM v2 API. Provides service principal identity and entitlement information; the connector reads `/api/{apiVersion}/preview/scim/v2/ServicePrincipals` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-service-principals-active-78e4b5be6fea" title="Active" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.active`

            Active records whether the service principal is currently active and allowed to authenticate. It is needed to distinguish Service Principals rows by the exact Databricks-returned active value.

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

          <Accordion id="provider-permission-field-databricks-service-principals-applicationid-8124855eacde" title="Application ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.applicationId`

            Application ID records the application (client) ID of the service principal, typically a UUID matching the Azure AD or Databricks application registration. It is needed to refer to the same application across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-service-principals-displayname-8ed8ca875940" title="Display Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.displayName`

            Display Name records human-readable display name of the service principal. It is needed to attribute this Service Principals row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-service-principals-entitlements-3cd3a358e4d6" title="Entitlements" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.entitlements`

            Entitlements records array of entitlements (feature permissions) assigned to the service principal, such as workspace-access or databricks-sql-access. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `entitlements` to examine the returned entitlements details for the containing Service Principal record.
            * **Interpretation:** Databricks reports this value on the Service Principal object returned for Service Principals; it is one returned collection per containing Service Principal object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-service-principals-entitlements-value-53b101e375be" title="Value" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.entitlements.value`

            Value records the entitlement identifier string (e.g., workspace-access, databricks-sql-access, allow-cluster-create). 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 `value` access value with the resource, account, or membership represented by the same Service Principals row.
            * **Interpretation:** Databricks reports this value on the Entitlement Value object returned for Service Principals; 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-databricks-service-principals-externalid-a81b87683219" title="External ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.externalId`

            External ID records external identifier for the service principal, often set by an external identity provider or SCIM provisioning client. It is needed to refer to the same external across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-service-principals-groups-e5f714314604" title="Groups" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.groups`

            Groups records array of groups the service principal belongs to. It is needed to preserve the nested groups relationship or details on the parent Service Principal record.

            * **Enables:** expand `groups` to connect the containing Service Principal row to its returned groups entries.
            * **Interpretation:** Databricks reports this value on the Service Principal object returned for Service Principals; it is one returned collection per containing Service Principal object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-service-principals-groups-ref-c6eff8192ca4" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.groups.$ref`

            Resource Reference records the URI reference for the group resource. It is needed to retain the exact Databricks resource or external link reported for this Service Principals record.

            * **Enables:** open or correlate the resource named by `$ref` while retaining the containing Group Reference row as provenance.
            * **Interpretation:** Databricks reports this value on the Group Reference object returned for Service Principals; it is interpreted at one Group Reference 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-databricks-service-principals-groups-display-a64a49950a8c" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.groups.display`

            Display records the display name of the group. It is needed to compare the returned display for individual Service Principals rows and select rows with a specific `display` value.

            * **Enables:** locate Service Principals rows whose returned display exactly matches `display` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Group Reference object returned for Service Principals; it is interpreted at one Group Reference record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-service-principals-groups-type-e5fb00b73101" title="Type" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.groups.type`

            Type records the type of group membership (e.g., direct). It is needed to distinguish Service Principals rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-service-principals-groups-value-46d3a3fc120a" title="Value" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.groups.value`

            Value records the SCIM id of the group. It is needed to link the service-principal relationship to the exact Databricks SCIM group.

            * **Enables:** match `value` to the Databricks group record carrying the same SCIM identifier.
            * **Interpretation:** Databricks reports this value on the Group Reference object returned for Service Principals; it is interpreted at one Group Reference record per row; the value is a Databricks SCIM group identifier, not a display name or measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-service-principals-id-6205b8ef1075" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.id`

            ID records unique SCIM identifier for the service principal within the Databricks workspace. It is needed to distinguish repeated deliveries of the same Service Principals row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-service-principals-roles-a0da60404c5a" title="Roles" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.roles`

            Roles records array of workspace-level roles assigned to the service principal. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `roles` to examine the returned roles details for the containing Service Principal record.
            * **Interpretation:** Databricks reports this value on the Service Principal object returned for Service Principals; it is one returned collection per containing Service Principal object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-service-principals-roles-type-f72d4c5c7f18" title="Type" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.roles.type`

            Type records the type qualifier for the role assignment. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Service Principals rows with the exact `type` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Role Value object returned for Service Principals; it is interpreted at one Role Value record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-service-principals-roles-value-d474df989c81" title="Value" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.roles.value`

            Value records the role identifier string. 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 `value` access value with the resource, account, or membership represented by the same Service Principals row.
            * **Interpretation:** Databricks reports this value on the Role Value object returned for Service Principals; 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-databricks-service-principals-schemas-9ccd2e6ec1f8" title="Schemas" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `service_principals.schemas`

            Schemas records list of SCIM schema URNs that apply to this resource (e.g., urn:ietf:params:scim:schemas:core:2.0:ServicePrincipal). It is needed to preserve the nested schemas relationship or details on the parent Service Principal record.

            * **Enables:** expand `schemas` to connect the containing Service Principal row to its returned schemas entries.
            * **Interpretation:** Databricks reports this value on the Service Principal object returned for Service Principals; it is one returned collection per containing Service Principal object.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-databricks-sql-warehouses-60280e66d5f2" title="SQL Warehouses" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `sql_warehouses`

        SQL Warehouses covers SQL warehouses in the Databricks workspace. Provides SQL warehouse configuration, state, and sizing details.

        * **Enables:** compare returned SQL warehouse configuration, size, state, creator, and operating times.
        * **Scope:** Lists all SQL warehouses in the Databricks workspace. Provides SQL warehouse configuration, state, and sizing details; the connector reads `/api/{apiVersion}/sql/warehouses` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-sql-warehouses-auto-resume-7fde8bd27c39" title="Auto Resume" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.auto_resume`

            Auto Resume records whether the warehouse automatically resumes when a SQL statement is submitted. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned auto resume value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-auto-stop-mins-030f460c4c3b" title="Auto Stop Mins" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.auto_stop_mins`

            Auto Stop Mins records minutes of inactivity before the warehouse auto-stops. 0 means auto-stop is disabled. It is needed to measure the reported auto stop mins for one sql warehouse record.

            * **Enables:** measure and compare `auto_stop_mins` per SQL Warehouse record in minutes.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; its unit or granularity is minutes.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-channel-8cae294cd39d" title="Channel" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.channel`

            Channel records release channel configuration for the warehouse. It is needed to preserve the nested channel relationship or details on the parent SQL Warehouse record.

            * **Enables:** expand `channel` to connect the containing SQL Warehouse row to its returned channel entries.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is one nested object per containing SQL Warehouse object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-channel-dbsql-version-3b81c0a47783" title="Dbsql Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.channel.dbsql_version`

            Dbsql Version records the DBSQL version associated with this channel. It is needed to compare the exact dbsql version configuration returned for this Channel record.

            * **Enables:** compare the exact `dbsql_version` configuration returned for each Channel record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Channel object returned for SQL Warehouses; it is interpreted at one Channel record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-channel-name-970fb1a148e9" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.channel.name`

            Name records name of the release channel. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned name value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-cluster-size-5358f591b735" title="Cluster Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.cluster_size`

            Cluster Size records size of the warehouse cluster (e.g., 2X-Small, X-Small, Small, Medium, Large, X-Large, 2X-Large, 3X-Large, 4X-Large). It is needed to compare the Databricks-reported compute size selected for the warehouse.

            * **Enables:** filter SQL Warehouses by the exact `cluster_size` size label when reconciling configured warehouse capacity.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is interpreted at one SQL Warehouse record per row; the value is a Databricks size class rather than a direct core, memory, performance, or cost measurement.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-creator-id-e54cb0fb2462" title="Creator ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.creator_id`

            Creator ID records unique identifier of the user who created the warehouse. It is needed to refer to the same creator across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-creator-name-dd43181c04cc" title="Creator Name" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.creator_name`

            Creator Name records username or email of the user who created the warehouse. It is needed to attribute this SQL Warehouses row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-data-source-id-14b46ce7acd7" title="Data Source ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.data_source_id`

            Data Source ID records data source ID used for internal references. It is needed to refer to the same data source across records without relying on display text.

            * **Enables:** match `data_source_id` to data source references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is an identifier, not a measured quantity; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-enable-photon-a480f19e54fe" title="Enable Photon" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.enable_photon`

            Enable Photon records whether the Photon query engine is enabled. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned enable photon value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-enable-serverless-comp-7667f6f97df0" title="Enable Serverless Compute" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.enable_serverless_compute`

            Enable Serverless Compute records whether serverless compute is enabled for this warehouse. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned enable serverless compute value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-2c2eb13154c3" title="Health" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health`

            Health records health status information for the warehouse. It is needed to preserve the nested health relationship or details on the parent SQL Warehouse record.

            * **Enables:** expand `health` to connect the containing SQL Warehouse row to its returned health entries.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is one nested object per containing SQL Warehouse object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-details-3c8c2f5ff165" title="Details" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.details`

            Details records detailed health information. It is needed to inspect the exact health-detail text returned for this Warehouse Health record.

            * **Enables:** attribute the health-detail text in `details` to the containing SQL Warehouses identifier, owner or author, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Warehouse Health object returned for SQL Warehouses; it is interpreted at one Warehouse Health record per row; this is only the health-detail text included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-failure-reason-7bdcfc0adc2f" title="Failure Reason" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.failure_reason`

            Failure Reason records details about a health failure, if applicable. It is needed to preserve the nested failure reason relationship or details on the parent Warehouse Health record.

            * **Enables:** expand `failure_reason` to connect the containing Warehouse Health row to its returned failure reason entries.
            * **Interpretation:** Databricks reports this value on the Warehouse Health object returned for SQL Warehouses; it is one nested object per containing Warehouse Health object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-failure-reason--f0c4a5207f84" title="Code" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.failure_reason.code`

            Code records error code for the failure reason. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned code value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-failure-reason--64a9d6fb690f" title="Parameters" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.failure_reason.parameters`

            Parameters records additional parameters providing context for the failure. It is needed to preserve the exact Databricks configuration or execution metadata attached to this Health Failure Reason record.

            * **Enables:** inspect the keys in `parameters` when reproducing or investigating this record's configuration, parameters, or execution context.
            * **Interpretation:** Databricks reports this value on the Health Failure Reason object returned for SQL Warehouses; it is interpreted at one Health Failure Reason record per row; the schema uses the `Generic.JSON` scalar; metadata keys and availability follow the Databricks response and can vary by resource type or configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-failure-reason--76359974fe40" title="Type" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.failure_reason.type`

            Type records type classification of the failure. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-message-cc70b2eab6c6" title="Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.message`

            Message records human-readable health status message. It is needed to inspect the exact status message included with this record.

            * **Enables:** inspect the status message returned in `message` and attribute it to the same record's parent record, owner, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Warehouse Health object returned for SQL Warehouses; it is status message at one Warehouse Health record per row; this is only the content included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-status-3fb9fec102ba" title="Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.status`

            Status records overall health status of the warehouse. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned status value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-health-summary-69191bec3f47" title="Summary" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.health.summary`

            Summary records summary of the warehouse health. It is needed to inspect the exact summary text included with this record.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-id-112ef8a042d1" title="ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.id`

            ID records unique identifier for the SQL warehouse. It is needed to distinguish repeated deliveries of the same SQL Warehouses row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-instance-profile-arn-d70229026d63" title="Instance Profile Arn" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.instance_profile_arn`

            Instance Profile Arn records AWS instance profile ARN associated with the warehouse (if applicable). It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `instance_profile_arn` among SQL Warehouses records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is interpreted at one SQL Warehouse record per row; the value is a Databricks-returned or configured label at the SQL Warehouse grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-jdbc-url-54f266d3bc05" title="Jdbc URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.jdbc_url`

            Jdbc URL records JDBC connection URL for the warehouse. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `jdbc_url` while retaining the containing SQL Warehouses record as provenance.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is link at one SQL Warehouse record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-max-num-clusters-721dffc875dc" title="Max Num Clusters" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.max_num_clusters`

            Max Num Clusters records maximum number of clusters for auto-scaling. It is needed to measure the Databricks-reported number of max num clusters at one SQL Warehouse record per row.

            * **Enables:** measure and compare the Databricks-reported number of max num clusters in `max_num_clusters` at one SQL Warehouse record per row.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is a Databricks-reported count at one SQL Warehouse record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-min-num-clusters-d6e7f26321c6" title="Min Num Clusters" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.min_num_clusters`

            Min Num Clusters records minimum number of clusters for auto-scaling. It is needed to measure the Databricks-reported number of min num clusters at one SQL Warehouse record per row.

            * **Enables:** measure and compare the Databricks-reported number of min num clusters in `min_num_clusters` at one SQL Warehouse record per row.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is a Databricks-reported count at one SQL Warehouse record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-name-8be79042638e" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.name`

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

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-num-active-sessions-4089eed92fb8" title="Num Active Sessions" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.num_active_sessions`

            Num Active Sessions records number of currently active sessions on the warehouse. It is needed to measure the Databricks-reported number of currently active sessions on the warehouse at one SQL Warehouse record per row.

            * **Enables:** measure and compare the Databricks-reported number of currently active sessions on the warehouse in `num_active_sessions` at one SQL Warehouse record per row.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is a Databricks-reported count at one SQL Warehouse record per row; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-num-clusters-b007d565eedb" title="Num Clusters" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.num_clusters`

            Num Clusters records current number of running clusters for this warehouse. It is needed to measure the Databricks-reported number of num clusters at one SQL Warehouse record per row.

            * **Enables:** measure and compare the Databricks-reported number of num clusters in `num_clusters` at one SQL Warehouse record per row.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is a Databricks-reported count at one SQL Warehouse record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-odbc-params-a69778283141" title="Odbc Params" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.odbc_params`

            Odbc Params records ODBC connection parameters for the warehouse. It is needed to preserve the nested odbc params relationship or details on the parent SQL Warehouse record.

            * **Enables:** expand `odbc_params` to connect the containing SQL Warehouse row to its returned odbc params entries.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is one nested object per containing SQL Warehouse object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-odbc-params-hostname-2dff82ec6a61" title="Hostname" icon="network-wired" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.odbc_params.hostname`

            Hostname records hostname for the ODBC connection. It is needed to compare the returned hostname for individual SQL Warehouses rows and select rows with a specific `hostname` value.

            * **Enables:** locate SQL Warehouses rows whose returned hostname exactly matches `hostname` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the Odbc Params object returned for SQL Warehouses; it is interpreted at one Odbc Params record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-odbc-params-path-4f2e14d77db7" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.odbc_params.path`

            Path records HTTP path for the ODBC connection. It is needed to compare the returned path for individual SQL Warehouses rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the Odbc Params row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Odbc Params object returned for SQL Warehouses; it is interpreted at one Odbc Params record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-odbc-params-port-6e66644b6d25" title="Port" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.odbc_params.port`

            Port records port number for the ODBC connection. It is needed to compare the numeric port reported for one Odbc Params record without assuming an unstated unit.

            * **Enables:** compare the numeric `port` value per Odbc Params record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the Odbc Params object returned for SQL Warehouses; it is interpreted at one Odbc Params record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-odbc-params-protocol-f530ce2b34af" title="Protocol" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.odbc_params.protocol`

            Protocol records protocol used (e.g., https). It is needed to compare the exact protocol configuration returned for this Odbc Params record.

            * **Enables:** compare the exact `protocol` configuration returned for each Odbc Params record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Odbc Params object returned for SQL Warehouses; it is interpreted at one Odbc Params record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-spot-instance-policy-1dc8469c7a66" title="Spot Instance Policy" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.spot_instance_policy`

            Spot Instance Policy records policy for using spot instances. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select SQL Warehouses rows with the exact `spot_instance_policy` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is interpreted at one SQL Warehouse record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-state-2ec71cb4fc6a" title="State" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.state`

            State records current state of the SQL warehouse. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned state value.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-tags-6718e2f91927" title="Tags" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.tags`

            Tags records tags applied to the warehouse. It is needed to preserve the nested tags relationship or details on the parent SQL Warehouse record.

            * **Enables:** expand `tags` to connect the containing SQL Warehouse row to its returned tags entries.
            * **Interpretation:** Databricks reports this value on the SQL Warehouse object returned for SQL Warehouses; it is one nested object per containing SQL Warehouse object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-tags-custom-tags-75f0b2d13778" title="Custom Tags" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.tags.custom_tags`

            Custom Tags records list of custom key-value tag pairs. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `custom_tags` and associate them with the containing SQL Warehouses record.
            * **Interpretation:** Databricks reports this value on the Tags object returned for SQL Warehouses; it is one returned collection per containing Tags object; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-tags-custom-tags-key-f923abf962cb" title="Key" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.tags.custom_tags.key`

            Key records tag key. It is needed to refer to the same tag across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-sql-warehouses-tags-custom-tags-value-0c0a08a7056f" title="Value" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.tags.custom_tags.value`

            Value records tag value. It is needed to inventory the exact Databricks-reported configuration or classification represented by this field.

            * **Enables:** compare `value` among SQL Warehouses records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** Databricks reports this value on the Tag object returned for SQL Warehouses; it is interpreted at one Tag record per row; the value is a Databricks-returned or configured label at the Tag grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-sql-warehouses-warehouse-type-8959f7425d39" title="Warehouse Type" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `sql_warehouses.warehouse_type`

            Warehouse Type records type of the SQL warehouse. It is needed to distinguish SQL Warehouses rows by the exact Databricks-returned warehouse type value.

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

      <Accordion id="provider-permission-tap-databricks-table-summaries-b03f6010085f" title="Table Summaries" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `table_summaries`

        Table Summaries covers table summaries within a catalog, providing a lightweight view of available tables with optional LIKE pattern filtering.

        * **Enables:** connect each returned table to its catalog and schema, then inspect its table kind, columns, owner, and storage metadata where returned.
        * **Scope:** Lists table summaries within a catalog, providing a lightweight view of available tables with optional LIKE pattern filtering; the connector reads `/api/2.1/unity-catalog/table-summaries` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-table-summaries-parent-catalog-name-a7f22f2268b6" title="Parent Catalog Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `table_summaries._parent_catalog_name`

            Parent Catalog Name records parent key injected by the ingestor from the catalogs to `table_summaries` traversal parentContextFields. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to compare the returned parent catalog name for individual Table Summaries rows and select rows with a specific `_parent_catalog_name` value.

            * **Enables:** locate Table Summaries rows whose returned parent catalog name exactly matches `_parent_catalog_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks's child response does not supply this field; the connector injects parent context into each child row; it is interpreted at one Table Summary record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-table-summaries-catalog-name-48d6ef748448" title="Catalog Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `table_summaries.catalog_name`

            Catalog Name records name of the parent catalog containing this table. It is needed to compare the returned catalog name for individual Table Summaries rows and select rows with a specific `catalog_name` value.

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

          <Accordion id="provider-permission-field-databricks-table-summaries-full-name-4be4aa597612" title="Full Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `table_summaries.full_name`

            Full Name records full three-level name of the table in the format catalog.schema.table. Serves as the unique identifier. It is needed to distinguish repeated deliveries of the same Table Summaries row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-databricks-table-summaries-schema-name-a341716a63b0" title="Schema Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `table_summaries.schema_name`

            Schema Name records name of the parent schema (database) containing this table. It is needed to compare the returned schema name for individual Table Summaries rows and select rows with a specific `schema_name` value.

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

          <Accordion id="provider-permission-field-databricks-table-summaries-table-type-39a72fc4de7d" title="Table Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `table_summaries.table_type`

            Table Type records the type of the table. It is needed to distinguish Table Summaries rows by the exact Databricks-returned table type value.

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

      <Accordion id="provider-permission-tap-databricks-tables-75ac755a318f" title="Tables" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `tables`

        Tables covers tables within a specified Unity Catalog catalog and schema. Requires `catalog_name` and `schema_name` as parent context fields. Provides table metadata including columns, data types, and storage info.

        * **Enables:** connect each returned table to its catalog and schema, then inspect its table kind, columns, owner, and storage metadata where returned.
        * **Scope:** Lists all tables within a specified Unity Catalog catalog and schema. Requires `catalog_name` and `schema_name` as parent context fields. Provides table metadata including columns, data types, and storage info; the connector reads `/api/2.1/unity-catalog/tables` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-tables-parent-catalog-name-e1913592063c" title="Parent Catalog Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables._parent_catalog_name`

            Parent Catalog Name records parent catalog name injected by the schemas to tables traversal parentContextFields. Not part of the upstream API response. It is needed to compare the returned parent catalog name for individual Tables rows and select rows with a specific `_parent_catalog_name` value.

            * **Enables:** locate Tables rows whose returned parent catalog name exactly matches `_parent_catalog_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks's child response does not supply this field; the connector injects parent context into each child row; it is interpreted at one Databricks Table record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-parent-schema-name-d36c11c375bf" title="Parent Schema Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables._parent_schema_name`

            Parent Schema Name records parent schema name injected by the schemas to tables traversal parentContextFields. Not part of the upstream API response. It is needed to compare the returned parent schema name for individual Tables rows and select rows with a specific `_parent_schema_name` value.

            * **Enables:** locate Tables rows whose returned parent schema name exactly matches `_parent_schema_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks's child response does not supply this field; the connector injects parent context into each child row; it is interpreted at one Databricks Table record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-access-point-ac8fdf5a537a" title="Access Point" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.access_point`

            Access Point records access point for the table, if applicable. 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 `access_point` access value with the resource, account, or membership represented by the same Tables row.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table 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-databricks-tables-browse-only-669fedf6eb6a" title="Browse Only" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `tables.browse_only`

            Browse Only records whether the user can only browse metadata for this table (no data access). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Tables rows with the exact `browse_only` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-cache-version-info-8dbb6d3015f4" title="Cache Version Info" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `tables.cache_version_info`

            Cache Version Info records the cache version info details attached to this Tables record. It is needed to preserve the nested cache version info relationship or details on the parent Databricks Table record.

            * **Enables:** expand `cache_version_info` to connect the containing Databricks Table row to its returned cache version info entries.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one nested object per containing Databricks Table object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-cache-version-info-metastore-v-42d41d9859a0" title="Metastore Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `tables.cache_version_info.metastore_version`

            Metastore Version records metastore version cached for this object. It is needed to compare the exact metastore version configuration returned for this Cache Version Info record.

            * **Enables:** compare the exact `metastore_version` configuration returned for each Cache Version Info record and select records with the configuration under review.
            * **Interpretation:** Databricks reports this value on the Cache Version Info object returned for Tables; it is interpreted at one Cache Version Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-catalog-id-07de9537b6d1" title="Catalog ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.catalog_id`

            Catalog ID records Unity Catalog catalog UUID. It is needed to refer to the same catalog across records without relying on display text.

            * **Enables:** match `catalog_id` to catalog references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is an identifier, not a measured quantity; the schema uses the `Identity.UUID` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-catalog-name-fcaa617c178d" title="Catalog Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.catalog_name`

            Catalog Name records name of the parent catalog. It is needed to compare the returned catalog name for individual Tables rows and select rows with a specific `catalog_name` value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-a1310e643984" title="Columns" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns`

            Columns records array of column definitions for the table. It is needed to preserve the nested columns relationship or details on the parent Databricks Table record.

            * **Enables:** expand `columns` to connect the containing Databricks Table row to its returned columns entries.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one returned collection per containing Databricks Table object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-columns-comment-561d40834ce1" title="Comment" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.comment`

            Comment records user-provided comment for the column. It is needed to inspect the exact comment or journal text included with this record.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-mask-4420d31d6eef" title="Mask" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.mask`

            Mask records column mask configuration, if any. It is needed to preserve the nested mask relationship or details on the parent Column Info record.

            * **Enables:** expand `mask` to connect the containing Column Info row to its returned mask entries.
            * **Interpretation:** Databricks reports this value on the Column Info object returned for Tables; it is one nested object per containing Column Info object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-columns-mask-function-name-470560b42097" title="Function Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.mask.function_name`

            Function Name records full name of the masking function. It is needed to compare the returned function name for individual Tables rows and select rows with a specific `function_name` value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-mask-using-column-name-55037fc9e28b" title="Using Column Names" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.mask.using_column_names`

            Using Column Names records column names used as inputs to the masking function. It is needed to preserve the nested using column names relationship or details on the parent Column Mask record.

            * **Enables:** expand `using_column_names` to connect the containing Column Mask row to its returned using column names entries.
            * **Interpretation:** Databricks reports this value on the Column Mask object returned for Tables; it is one returned collection per containing Column Mask object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-columns-name-5489b96bbb0f" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.name`

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

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

          <Accordion id="provider-permission-field-databricks-tables-columns-nullable-5057e64553b6" title="Nullable" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.nullable`

            Nullable records whether the column allows null values. It is needed to distinguish Tables rows by the exact Databricks-returned nullable value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-partition-index-789d91990954" title="Partition Index" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.partition_index`

            Partition Index records partition index if this column is a partition column. It is needed to compare the numeric partition index reported for one Column Info record without assuming an unstated unit.

            * **Enables:** compare the numeric `partition_index` value per Column Info record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the Column Info object returned for Tables; it is interpreted at one Column Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-columns-position-02ea14a7e0cd" title="Position" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.position`

            Position records zero-based ordinal position of the column in the table. It is needed to compare the numeric position reported for one Column Info record without assuming an unstated unit.

            * **Enables:** compare the numeric `position` value per Column Info record without assigning a unit not declared by the schema description.
            * **Interpretation:** Databricks reports this value on the Column Info object returned for Tables; it is interpreted at one Column Info record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-columns-type-interval-type-e12988697547" title="Type Interval Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.type_interval_type`

            Type Interval Type records interval type string for INTERVAL columns. It is needed to distinguish Tables rows by the exact Databricks-returned type interval type value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-type-json-1f098ce8d782" title="Type JSON" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.type_json`

            Type JSON records JSON representation of the column's type. It is needed to distinguish Tables rows by the exact Databricks-returned type json value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-type-name-ee681d18a6c8" title="Type Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.type_name`

            Type Name records the top-level type name of the column. It is needed to distinguish Tables rows by the exact Databricks-returned type name value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-type-precision-13688edeaef8" title="Type Precision" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.type_precision`

            Type Precision records precision of the column type (for DECIMAL types). It is needed to distinguish Tables rows by the exact Databricks-returned type precision value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-type-scale-a3bf7a342ad2" title="Type Scale" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.type_scale`

            Type Scale records scale of the column type (for DECIMAL types). It is needed to distinguish Tables rows by the exact Databricks-returned type scale value.

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

          <Accordion id="provider-permission-field-databricks-tables-columns-type-text-8dc6818c6a90" title="Type Text" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.columns.type_text`

            Type Text records the full SQL type declaration for the column (for example, `BIGINT` or `STRUCT<a:INT,b:STRING>`). It is needed to distinguish scalar and nested column types using the exact Databricks-returned text.

            * **Enables:** compare `type_text` across Tables rows when reviewing or reconciling table schemas.
            * **Interpretation:** Databricks reports this value on the Column Info object returned for Tables; it is the SQL type declaration for one column.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-comment-0e18244db2ff" title="Comment" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `tables.comment`

            Comment records user-provided comment or description for the table. It is needed to inspect the exact comment or journal text included with this record.

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

          <Accordion id="provider-permission-field-databricks-tables-created-at-57446657ad0c" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `tables.created_at`

            Created At records timestamp in epoch milliseconds when the table was created. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Tables records by `created_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; its unit or granularity is epoch milliseconds; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-created-by-f44fc002170b" title="Created By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `tables.created_by`

            Created By records user or principal who created the table. It is needed to attribute this Tables row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-tables-data-access-configuration-id-837e53e65cb2" title="Data Access Configuration ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `tables.data_access_configuration_id`

            Data Access Configuration ID records data access configuration UUID when present. 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 `data_access_configuration_id` access value with the resource, account, or membership represented by the same Tables row.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is an identifier, not a measured quantity; the schema uses the `Identity.UUID` 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-databricks-tables-data-source-format-865baf12d1e5" title="Data Source Format" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.data_source_format`

            Data Source Format records data source format of the table. It is needed to distinguish Tables rows by the exact Databricks-returned data source format value.

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

          <Accordion id="provider-permission-field-databricks-tables-delta-runtime-properties-kvpai-5dedbac0c7de" title="Delta Runtime Properties Kvpairs" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `tables.delta_runtime_properties_kvpairs`

            Delta Runtime Properties Kvpairs records delta-specific runtime key-value property pairs. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `delta_runtime_properties_kvpairs` and associate them with the containing Tables record.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-effective-predictive-optimizat-5d75bdfb6108" title="Effective Predictive Optimization Flag" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.effective_predictive_optimization_flag`

            Effective Predictive Optimization Flag records effective predictive optimization setting for the table. It is needed to distinguish Tables rows by the exact Databricks-returned effective predictive optimization flag value.

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

          <Accordion id="provider-permission-field-databricks-tables-enable-predictive-optimization-85936bd69ff2" title="Enable Predictive Optimization" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.enable_predictive_optimization`

            Enable Predictive Optimization records whether predictive optimization is enabled for the table. It is needed to distinguish Tables rows by the exact Databricks-returned enable predictive optimization value.

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

          <Accordion id="provider-permission-field-databricks-tables-encryption-details-7c2dcc55b3a3" title="Encryption Details" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.encryption_details`

            Encryption Details records encryption details for the table. It is needed to preserve the nested encryption details relationship or details on the parent Databricks Table record.

            * **Enables:** expand `encryption_details` to connect the containing Databricks Table row to its returned encryption details entries.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one nested object per containing Databricks Table object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-encryption-details-sse-encrypt-461aab6c525f" title="Sse Encryption Details" icon="server" iconType="sharp-duotone-solid">
            Developer identifier: `tables.encryption_details.sse_encryption_details`

            Sse Encryption Details records server-side encryption details. It is needed to preserve the nested sse encryption details relationship or details on the parent Encryption Details record.

            * **Enables:** expand `sse_encryption_details` to connect the containing Encryption Details row to its returned sse encryption details entries.
            * **Interpretation:** Databricks reports this value on the Encryption Details object returned for Tables; it is one nested object per containing Encryption Details object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-encryption-details-sse-encrypt-732c2e4efe68" title="Algorithm" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `tables.encryption_details.sse_encryption_details.algorithm`

            Algorithm records encryption algorithm used (e.g., `AES_256`). It is needed to inventory the Databricks-reported encryption configuration for this resource.

            * **Enables:** correlate `algorithm` with the same table or compute resource's encryption mode and key reference during configuration review.
            * **Interpretation:** Databricks reports this value on the Sse Encryption Details object returned for Tables; it is interpreted at one Sse Encryption Details record per row; the returned algorithm or key reference is configuration evidence and does not prove encryption enforcement or key availability.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-encryption-details-sse-encrypt-bed4ea7d2773" title="AWS Kms Key Arn" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.encryption_details.sse_encryption_details.aws_kms_key_arn`

            AWS Kms Key Arn records AWS KMS key ARN if using AWS KMS encryption. It is needed to inventory the Databricks-reported encryption configuration for this resource.

            * **Enables:** correlate `aws_kms_key_arn` with the same table or compute resource's encryption mode and key reference during configuration review.
            * **Interpretation:** Databricks reports this value on the Sse Encryption Details object returned for Tables; it is interpreted at one Sse Encryption Details record per row; the returned algorithm or key reference is configuration evidence and does not prove encryption enforcement or key availability.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-etag-dabc6c4298b7" title="ETag" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `tables.etag`

            ETag records entity tag for optimistic concurrency. It is needed to correlate the Databricks object version used for optimistic concurrency.

            * **Enables:** compare `etag` across observations of the same Databricks Table identifier to detect a returned version change before a conditional update.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; the entity tag is a version token, not a timestamp or proof that every intermediate update was observed.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-full-name-99aeeee31705" title="Full Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.full_name`

            Full Name records full three-level name of the table (catalog.schema.table). It is needed to distinguish repeated deliveries of the same Tables row using the declared ingestion key.

            * **Enables:** use `full_name` as the declared ingestion deduplication key for Tables and match repeated rows carrying the same Databricks identifier.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-generation-e43058160fbd" title="Generation" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `tables.generation`

            Generation records generation number of the table, incremented on each metadata change. It is needed to measure the Databricks-reported number of generation at one Databricks Table record per row.

            * **Enables:** measure and compare the Databricks-reported number of generation in `generation` at one Databricks Table record per row.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is a Databricks-reported count at one Databricks Table record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-metastore-id-99e8fe88abe1" title="Metastore ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.metastore_id`

            Metastore ID records unique identifier of the metastore that contains this table. It is needed to refer to the same metastore across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-tables-metastore-version-2468a1e040e0" title="Metastore Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `tables.metastore_version`

            Metastore Version records metastore version associated with this table record. It is needed to compare the exact metastore version configuration returned for this Databricks Table record.

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

          <Accordion id="provider-permission-field-databricks-tables-name-6924339e89ce" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.name`

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

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

          <Accordion id="provider-permission-field-databricks-tables-owner-0a37501c14e3" title="Owner" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `tables.owner`

            Owner records owner of the table. It is needed to attribute this Tables row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-tables-pipeline-id-2b707b0eb4ef" title="Pipeline ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.pipeline_id`

            Pipeline ID records ID of the Delta Live Tables pipeline that manages this table, if any. It is needed to refer to the same pipeline across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-tables-properties-9004c359338e" title="Properties" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.properties`

            Properties records key-value properties/metadata associated with the table. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `properties` and associate them with the containing Tables record.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; the schema uses the `Generic.JSON` scalar; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-row-filter-a50a01a10704" title="Row Filter" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `tables.row_filter`

            Row Filter records row filter configuration applied to the table, if any. It is needed to preserve the nested row filter relationship or details on the parent Databricks Table record.

            * **Enables:** expand `row_filter` to connect the containing Databricks Table row to its returned row filter entries.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one nested object per containing Databricks Table object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-row-filter-input-column-names-62f7a1ad70d0" title="Input Column Names" icon="filter" iconType="sharp-duotone-solid">
            Developer identifier: `tables.row_filter.input_column_names`

            Input Column Names records column names passed as inputs to the row filter function. It is needed to preserve the nested input column names relationship or details on the parent Table Row Filter record.

            * **Enables:** expand `input_column_names` to connect the containing Table Row Filter row to its returned input column names entries.
            * **Interpretation:** Databricks reports this value on the Table Row Filter object returned for Tables; it is one returned collection per containing Table Row Filter object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-row-filter-name-39e834afe508" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.row_filter.name`

            Name records full name of the row filter function. It is needed to compare the returned name for individual Tables rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-databricks-tables-row-filters-bacf8d4e4341" title="Row Filters" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `tables.row_filters`

            Row Filters records row filters applied to the table. It is needed to preserve the nested row filters relationship or details on the parent Databricks Table record.

            * **Enables:** expand `row_filters` to connect the containing Databricks Table row to its returned row filters entries.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one returned collection per containing Databricks Table object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-schema-id-cbd00578b027" title="Schema ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `tables.schema_id`

            Schema ID records Unity Catalog schema UUID. It is needed to refer to the same schema across records without relying on display text.

            * **Enables:** match `schema_id` to schema references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is an identifier, not a measured quantity; the schema uses the `Identity.UUID` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-schema-name-45e792dd7cc2" title="Schema Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.schema_name`

            Schema Name records name of the parent schema. It is needed to compare the returned schema name for individual Tables rows and select rows with a specific `schema_name` value.

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

          <Accordion id="provider-permission-field-databricks-tables-securable-kind-49f8b18b663f" title="Securable Kind" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.securable_kind`

            Securable Kind records the kind of securable object this table represents. It is needed to distinguish Tables rows by the exact Databricks-returned securable kind value.

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

          <Accordion id="provider-permission-field-databricks-tables-securable-type-0f6396c5b49d" title="Securable Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.securable_type`

            Securable Type records the securable type of this object. It is needed to distinguish Tables rows by the exact Databricks-returned securable type value.

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

          <Accordion id="provider-permission-field-databricks-tables-sql-path-7e50d0aed8ea" title="SQL Path" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `tables.sql_path`

            SQL Path records SQL path of the table. It is needed to compare the returned sql path for individual Tables rows and select rows with a specific `sql_path` value.

            * **Enables:** trace the sql path relationship returned in `sql_path` from the Databricks Table row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-storage-credential-name-02cbe15bc017" title="Storage Credential Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `tables.storage_credential_name`

            Storage Credential Name records name of the storage credential used to access the storage location. 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 `storage_credential_name` access value with the resource, account, or membership represented by the same Tables row.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table 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-databricks-tables-storage-location-c78f2d07d78a" title="Storage Location" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `tables.storage_location`

            Storage Location records storage location URL for the table data. It is needed to preserve the Databricks-reported resource location link for the same record.

            * **Enables:** correlate the Databricks resource link in `storage_location` with its containing Databricks Table row without treating the resource path as a statement of data residency.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; the schema uses the `Network.Uri` scalar; the value is resource location link; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-6ded9fe74c00" title="Table Constraints" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints`

            Table Constraints records list of table constraints such as primary key, foreign key, etc. It is needed to refer to the same table constraints across records without relying on display text.

            * **Enables:** match `table_constraints` to table constraints references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one returned collection per containing Databricks Table object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-foreign-key--063e29e68c3a" title="Foreign Key Constraint" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.foreign_key_constraint`

            Foreign Key Constraint records foreign key constraint definition. It is needed to refer to the same foreign  constraint across records without relying on display text.

            * **Enables:** match `foreign_key_constraint` to foreign  constraint references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Table Constraint object returned for Tables; it is one nested object per containing Table Constraint object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-foreign-key--edc1b600470a" title="Child Columns" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.foreign_key_constraint.child_columns`

            Child Columns records column names in the child (referencing) table. It is needed to preserve the nested child columns relationship or details on the parent Foreign Key Constraint record.

            * **Enables:** expand `child_columns` to connect the containing Foreign Key Constraint row to its returned child columns entries.
            * **Interpretation:** Databricks reports this value on the Foreign Key Constraint object returned for Tables; it is one returned collection per containing Foreign Key Constraint object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-foreign-key--f52bcde51ad4" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.foreign_key_constraint.name`

            Name records name of the foreign key constraint. It is needed to refer to the same name across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-foreign-key--4a556f62d870" title="Parent Columns" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.foreign_key_constraint.parent_columns`

            Parent Columns records column names in the parent (referenced) table. It is needed to preserve the nested parent columns relationship or details on the parent Foreign Key Constraint record.

            * **Enables:** expand `parent_columns` to connect the containing Foreign Key Constraint row to its returned parent columns entries.
            * **Interpretation:** Databricks reports this value on the Foreign Key Constraint object returned for Tables; it is one returned collection per containing Foreign Key Constraint object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-foreign-key--eadc2d941064" title="Parent Table" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.foreign_key_constraint.parent_table`

            Parent Table records full name of the parent (referenced) table. It is needed to compare the returned parent table for individual Tables rows and select rows with a specific `parent_table` value.

            * **Enables:** trace the parent table relationship returned in `parent_table` from the Foreign Key Constraint row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Foreign Key Constraint object returned for Tables; it is interpreted at one Foreign Key Constraint record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-named-table--ab9ac36dc20f" title="Named Table Constraint" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.named_table_constraint`

            Named Table Constraint records named table constraint (e.g., CHECK constraint). It is needed to preserve the nested named table constraint relationship or details on the parent Table Constraint record.

            * **Enables:** expand `named_table_constraint` to connect the containing Table Constraint row to its returned named table constraint entries.
            * **Interpretation:** Databricks reports this value on the Table Constraint object returned for Tables; it is one nested object per containing Table Constraint object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-named-table--f2a69e9170a8" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.named_table_constraint.name`

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

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

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-primary-key--9555fbcea34d" title="Primary Key Constraint" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.primary_key_constraint`

            Primary Key Constraint records primary key constraint definition. It is needed to refer to the same primary  constraint across records without relying on display text.

            * **Enables:** match `primary_key_constraint` to primary  constraint references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Table Constraint object returned for Tables; it is one nested object per containing Table Constraint object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-primary-key--eeb86e09e516" title="Child Columns" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.primary_key_constraint.child_columns`

            Child Columns records column names that form the primary key. It is needed to refer to the same child columns across records without relying on display text.

            * **Enables:** match `child_columns` to child columns references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Primary Key Constraint object returned for Tables; it is one returned collection per containing Primary Key Constraint object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-constraints-primary-key--9bbb38a98dc6" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_constraints.primary_key_constraint.name`

            Name records name of the primary key constraint. It is needed to refer to the same name across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-tables-table-id-5bb9adcbeb4f" title="Table ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_id`

            Table ID records unique identifier (UUID) for the table. It is needed to refer to the same table across records without relying on display text.

            * **Enables:** match `table_id` to table references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is an identifier, not a measured quantity; the schema uses the `Identity.UUID` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-table-type-a5615ce3c934" title="Table Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.table_type`

            Table Type records type of the table. It is needed to distinguish Tables rows by the exact Databricks-returned table type value.

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

          <Accordion id="provider-permission-field-databricks-tables-updated-at-3301a5a5f7d0" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `tables.updated_at`

            Updated At records timestamp in epoch milliseconds when the table was last updated. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Tables records by `updated_at`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; its unit or granularity is epoch milliseconds; the connector also declares it for record ordering; the schema declares the `unix_millis` temporal format; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-updated-by-9a0cb7e17627" title="Updated By" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `tables.updated_by`

            Updated By records user or principal who last updated the table. It is needed to attribute this Tables row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-databricks-tables-view-definition-5aa3d2a7587e" title="View Definition" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_definition`

            View Definition records SQL text of the view definition, if the `table_type` is VIEW. It is needed to inspect the exact SQL view definition returned for this Databricks Table record.

            * **Enables:** attribute the SQL view definition in `view_definition` to the containing Tables identifier, owner or author, status, and update time where returned.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is interpreted at one Databricks Table record per row; this is only the SQL view definition included in the Databricks response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-view-dependencies-3b578d78a0ad" title="View Dependencies" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_dependencies`

            View Dependencies records dependencies of the view, if the `table_type` is VIEW. It is needed to preserve the nested view dependencies relationship or details on the parent Databricks Table record.

            * **Enables:** expand `view_dependencies` to connect the containing Databricks Table row to its returned view dependencies entries.
            * **Interpretation:** Databricks reports this value on the Databricks Table object returned for Tables; it is one nested object per containing Databricks Table object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-view-dependencies-dependencies-11608a5203c3" title="Dependencies" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_dependencies.dependencies`

            Dependencies records list of dependency objects for the view. It is needed to preserve the nested dependencies relationship or details on the parent View Dependencies record.

            * **Enables:** expand `dependencies` to connect the containing View Dependencies row to its returned dependencies entries.
            * **Interpretation:** Databricks reports this value on the View Dependencies object returned for Tables; it is one returned collection per containing View Dependencies object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-view-dependencies-dependencies-194c70e9c8fe" title="Function" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_dependencies.dependencies.function`

            Function records function dependency reference. It is needed to preserve the nested function relationship or details on the parent View Dependency record.

            * **Enables:** expand `function` to connect the containing View Dependency row to its returned function entries.
            * **Interpretation:** Databricks reports this value on the View Dependency object returned for Tables; it is one nested object per containing View Dependency object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-view-dependencies-dependencies-6f3fe24b7777" title="Function Full Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_dependencies.dependencies.function.function_full_name`

            Function Full Name records full name of the dependent function. It is needed to compare the returned function full name for individual Tables rows and select rows with a specific `function_full_name` value.

            * **Enables:** locate Tables rows whose returned function full name exactly matches `function_full_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the View Dependency Function object returned for Tables; it is interpreted at one View Dependency Function record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-view-dependencies-dependencies-175b87559811" title="Table" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_dependencies.dependencies.table`

            Table records table dependency reference. It is needed to preserve the nested table relationship or details on the parent View Dependency record.

            * **Enables:** expand `table` to connect the containing View Dependency row to its returned table entries.
            * **Interpretation:** Databricks reports this value on the View Dependency object returned for Tables; it is one nested object per containing View Dependency object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-tables-view-dependencies-dependencies-781c1088609b" title="Table Full Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `tables.view_dependencies.dependencies.table.table_full_name`

            Table Full Name records full three-level name of the dependent table. It is needed to compare the returned table full name for individual Tables rows and select rows with a specific `table_full_name` value.

            * **Enables:** locate Tables rows whose returned table full name exactly matches `table_full_name` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the View Dependency Table object returned for Tables; it is interpreted at one View Dependency Table record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-databricks-users-8017bc21edbb" title="Users" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `users`

        Users covers users in the Databricks workspace via the SCIM v2 API. Provides user identity, email, and group membership information.

        * **Enables:** map the Databricks accounts and memberships represented by Users records and trace a returned access assignment to its account or group.
        * **Scope:** Lists all users in the Databricks workspace via the SCIM v2 API. Provides user identity, email, and group membership information; the connector reads `/api/{apiVersion}/preview/scim/v2/Users` as a snapshot stream in full mode. The configured credential must grant the declared `all-apis` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the Databricks record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-databricks-users-active-e450e291de03" title="Active" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.active`

            Active records whether the user account is currently active in the workspace. It is needed to distinguish Users rows by the exact Databricks-returned active value.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-7d497d1f60cb" title="Addresses" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses`

            Addresses records array of addresses associated with the user. It is needed to preserve the nested addresses relationship or details on the parent Databricks User record.

            * **Enables:** expand `addresses` to connect the containing Databricks User row to its returned addresses entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-addresses-country-59aa2c3fe9fb" title="Country" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.country`

            Country records country code or name. It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-formatted-fd7a9f5bf68e" title="Formatted" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.formatted`

            Formatted records full formatted address string. It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-locality-256b8474f859" title="Locality" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.locality`

            Locality records city or locality. It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-postalcode-36e61331d394" title="Postal Code" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.postalCode`

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

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

          <Accordion id="provider-permission-field-databricks-users-addresses-primary-c708a07777c9" title="Primary" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.primary`

            Primary records whether this is the primary address. It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-region-b805bab599f5" title="Region" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.region`

            Region records state or region. It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-streetaddress-d77781b84cc3" title="Street Address" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.streetAddress`

            Street Address records street address component. It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-addresses-type-c3c56ad97859" title="Type" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.addresses.type`

            Type records type of address (e.g., work, home). It is needed to preserve the Databricks-reported configured or derived address and place context for the same record.

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

          <Accordion id="provider-permission-field-databricks-users-displayname-b86e15f967d3" title="Display Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.displayName`

            Display Name records 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 `displayName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is interpreted at one Databricks User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-emails-e6eb751a5d0b" title="Emails" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `users.emails`

            Emails records array of email addresses associated with the user. It is needed to preserve the nested emails relationship or details on the parent Databricks User record.

            * **Enables:** expand `emails` to connect the containing Databricks User row to its returned emails entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-emails-ref-8b9a9725f369" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.emails.$ref`

            Resource Reference records SCIM reference URI for the email resource. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `$ref` while retaining the containing Users record as provenance.
            * **Interpretation:** Databricks reports this value on the User Email object returned for Users; it is link at one User Email 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-databricks-users-emails-display-a19d3f916668" title="Display" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.emails.display`

            Display records display label for the 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 `display` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the User Email object returned for Users; it is interpreted at one User Email record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-emails-primary-7c3c0b6e96e7" title="Primary" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.emails.primary`

            Primary records whether this is the primary email address. It is needed to distinguish Users rows by the exact Databricks-returned primary value.

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

          <Accordion id="provider-permission-field-databricks-users-emails-type-6525e9b36493" title="Type" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.emails.type`

            Type records type of email address (e.g., work, home). It is needed to distinguish Users rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-users-emails-value-9a86bf00bc4e" title="Value" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.emails.value`

            Value records the email address value. 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 `value` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the User Email object returned for Users; it is interpreted at one User Email record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-entitlements-c7266c336a3a" title="Entitlements" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `users.entitlements`

            Entitlements records array of entitlements granted to the user (e.g., workspace-access, databricks-sql-access). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `entitlements` to examine the returned entitlements details for the containing Databricks User record.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-entitlements-ref-069c94a80594" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.entitlements.$ref`

            Resource Reference records SCIM reference URI for the entitlement resource. 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 `$ref` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** Databricks reports this value on the User Entitlement object returned for Users; it is link at one User Entitlement record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-entitlements-display-557392d53306" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.entitlements.display`

            Display records display name of the entitlement. 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 `display` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** Databricks reports this value on the User Entitlement object returned for Users; it is interpreted at one User Entitlement 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-databricks-users-entitlements-value-45a58bec7c35" title="Value" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.entitlements.value`

            Value records the entitlement identifier. 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 `value` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** Databricks reports this value on the User Entitlement 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-databricks-users-externalid-53ec7a702c0b" title="External ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.externalId`

            External ID records external ID from the identity provider (e.g., Azure AD, Okta). It is needed to refer to the same external across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-users-groups-f71bed65632d" title="Groups" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups`

            Groups records array of groups the user belongs to. It is needed to preserve the nested groups relationship or details on the parent Databricks User record.

            * **Enables:** expand `groups` to connect the containing Databricks User row to its returned groups entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-groups-ref-6c4fa63969f4" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.$ref`

            Resource Reference records SCIM reference URI for the group resource. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `$ref` while retaining the containing Users record as provenance.
            * **Interpretation:** Databricks reports this value on the User Group Membership object returned for Users; it is link at one User Group Membership 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-databricks-users-groups-display-cb64ccda78e3" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.display`

            Display records display name of the group. It is needed to compare the returned display for individual Users rows and select rows with a specific `display` value.

            * **Enables:** locate Users rows whose returned display exactly matches `display` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the User Group Membership object returned for Users; it is interpreted at one User Group Membership record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-groups-type-65a4d1d1e9c8" title="Type" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.type`

            Type records type of group (direct or indirect). It is needed to distinguish Users rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-users-groups-value-d3eac4346401" title="Value" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.value`

            Value records unique identifier of the group. It is needed to refer to the same value across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-users-id-a7ba6db9a89e" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.id`

            ID records unique SCIM identifier for the user within the Databricks workspace. It is needed to distinguish repeated deliveries of the same Users row using the declared ingestion key.

            * **Enables:** use `id` as the declared ingestion deduplication key for Users and match repeated rows carrying the same Databricks identifier.
            * **Interpretation:** Databricks reports this value on the Databricks 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-databricks-users-locale-491e1059d874" title="Locale" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.locale`

            Locale records locale of the user. It is needed to preserve the Databricks-reported language or locale preference for this identity.

            * **Enables:** select identities by the exact `locale` language or locale tag without inferring physical location.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is interpreted at one Databricks User record per row; this Databricks-reported setting or qualifier does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-meta-7727202ba873" title="Meta" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `users.meta`

            Meta records SCIM resource metadata including resource type and creation/modification timestamps. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `meta` and associate them with the containing Users record.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one nested object per containing Databricks User object when present; keys and availability follow this Databricks response and may vary by object type or Databricks configuration.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-meta-created-60bc62f26a7c" title="Created" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `users.meta.created`

            Created records ISO 8601 timestamp when the resource was created. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-databricks-users-meta-lastmodified-f0609e2b9cef" title="Last Modified" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `users.meta.lastModified`

            Last Modified records ISO 8601 timestamp when the resource was last modified. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-databricks-users-meta-location-d3795081d432" title="Location" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.meta.location`

            Location records URI location of the resource. It is needed to preserve the Databricks-reported resource location link for the same record.

            * **Enables:** correlate the Databricks resource link in `location` with its containing Scim Meta row without treating the resource path as a statement of data residency.
            * **Interpretation:** Databricks reports this value on the Scim Meta object returned for Users; it is interpreted at one Scim Meta record per row; the schema uses the `Network.Url` scalar; the value is resource location link; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-meta-resourcetype-f74bd1c4aa47" title="Resource Type" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.meta.resourceType`

            Resource Type records the SCIM resource type (e.g., User, Group). It is needed to distinguish Users rows by the exact Databricks-returned resource type value.

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

          <Accordion id="provider-permission-field-databricks-users-meta-version-12d8a3110fa2" title="Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `users.meta.version`

            Version records version identifier (ETag) of the resource. It is needed to refer to the same version across records without relying on display text.

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

          <Accordion id="provider-permission-field-databricks-users-name-31ac3dadb8b6" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.name`

            Name records structured name object containing given name and family name. It is needed to preserve the nested name relationship or details on the parent Databricks User record.

            * **Enables:** expand `name` to connect the containing Databricks User row to its returned name entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one nested object per containing Databricks User object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-name-familyname-077fc831e81c" title="Family Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.name.familyName`

            Family Name records family (last) 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 `familyName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the User Name object returned for Users; it is interpreted at one User Name record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-name-formatted-7b347a88161d" title="Formatted" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.name.formatted`

            Formatted records full formatted name string. It is needed to preserve the exact Databricks-reported business, directory, or identity attribute represented by this field.

            * **Enables:** match or segment Users records by `formatted` only within the same Databricks attribute contract.
            * **Interpretation:** Databricks reports this value on the User Name object returned for Users; it is interpreted at one User Name record per row; the value is a Databricks-returned or configured label and is not a universal identity or business taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-name-givenname-086f2ca05fc6" title="Given Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.name.givenName`

            Given Name records given (first) 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 `givenName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the User Name object returned for Users; it is interpreted at one User Name record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-name-honorificprefix-f5b285617890" title="Honorific Prefix" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `users.name.honorificPrefix`

            Honorific Prefix records honorific prefix (e.g., Mr., Dr.). It is needed to preserve the exact Databricks-reported business, directory, or identity attribute represented by this field.

            * **Enables:** match or segment Users records by `honorificPrefix` only within the same Databricks attribute contract.
            * **Interpretation:** Databricks reports this value on the User Name object returned for Users; it is interpreted at one User Name record per row; the value is a Databricks-returned or configured label and is not a universal identity or business taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-name-honorificsuffix-7c7b871c7ef0" title="Honorific Suffix" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `users.name.honorificSuffix`

            Honorific Suffix records honorific suffix (e.g., Jr., III). It is needed to preserve the exact Databricks-reported business, directory, or identity attribute represented by this field.

            * **Enables:** match or segment Users records by `honorificSuffix` only within the same Databricks attribute contract.
            * **Interpretation:** Databricks reports this value on the User Name object returned for Users; it is interpreted at one User Name record per row; the value is a Databricks-returned or configured label and is not a universal identity or business taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-name-middlename-89f0e8df1e44" title="Middle Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.name.middleName`

            Middle Name records middle 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 `middleName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the User Name object returned for Users; it is interpreted at one User Name record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-nickname-1e9561bc17db" title="Nick Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.nickName`

            Nick Name records nickname or casual 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 `nickName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is interpreted at one Databricks User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-phonenumbers-d6157b650ce3" title="Phone Numbers" icon="phone" iconType="sharp-duotone-solid">
            Developer identifier: `users.phoneNumbers`

            Phone Numbers records array of phone numbers associated with the user. It is needed to preserve the nested phone numbers relationship or details on the parent Databricks User record.

            * **Enables:** expand `phoneNumbers` to connect the containing Databricks User row to its returned phone numbers entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-phonenumbers-display-33a2f7d38a2f" title="Display" icon="phone" iconType="sharp-duotone-solid">
            Developer identifier: `users.phoneNumbers.display`

            Display records display label for the phone number. It is needed to compare the returned display for individual Users rows and select rows with a specific `display` value.

            * **Enables:** locate Users rows whose returned display exactly matches `display` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the User Phone Number object returned for Users; it is interpreted at one User Phone Number record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-phonenumbers-primary-68816be0037e" title="Primary" icon="phone" iconType="sharp-duotone-solid">
            Developer identifier: `users.phoneNumbers.primary`

            Primary records whether this is the primary phone number. It is needed to distinguish Users rows by the exact Databricks-returned primary value.

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

          <Accordion id="provider-permission-field-databricks-users-phonenumbers-type-8063fb30e7ec" title="Type" icon="phone" iconType="sharp-duotone-solid">
            Developer identifier: `users.phoneNumbers.type`

            Type records type of phone number (e.g., work, mobile, home). It is needed to distinguish Users rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-users-phonenumbers-value-75e7a38a691f" title="Value" icon="phone" iconType="sharp-duotone-solid">
            Developer identifier: `users.phoneNumbers.value`

            Value records the phone number value. It is needed to preserve the exact contact number or extension reported for the person represented by this row.

            * **Enables:** associate `value` with the same User Phone Number identity and match the contact value only where it recurs exactly.
            * **Interpretation:** Databricks reports this value on the User Phone Number object returned for Users; it is interpreted at one User Phone Number record per row; the value is Databricks-reported contact data, not an account identifier or proof of current ownership.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-photos-1f6895cff214" title="Photos" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.photos`

            Photos records array of photo URLs associated with the user. It is needed to preserve the nested photos relationship or details on the parent Databricks User record.

            * **Enables:** expand `photos` to connect the containing Databricks User row to its returned photos entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-photos-display-cc747e87ddc7" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.photos.display`

            Display records display label for the photo. It is needed to compare the returned display for individual Users rows and select rows with a specific `display` value.

            * **Enables:** locate Users rows whose returned display exactly matches `display` and retain the Databricks identifier for any cross-record match.
            * **Interpretation:** Databricks reports this value on the User Photo object returned for Users; it is interpreted at one User Photo record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-photos-primary-c2b9db0a3a33" title="Primary" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.photos.primary`

            Primary records whether this is the primary photo. It is needed to distinguish Users rows by the exact Databricks-returned primary value.

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

          <Accordion id="provider-permission-field-databricks-users-photos-type-34da4cd8fdb3" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `users.photos.type`

            Type records type of photo (e.g., photo, thumbnail). It is needed to distinguish Users rows by the exact Databricks-returned type value.

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

          <Accordion id="provider-permission-field-databricks-users-photos-value-a00ab0bbdde1" title="Value" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.photos.value`

            Value records URL of the photo. It is needed to retain the exact Databricks resource or external link reported for this Users record.

            * **Enables:** open or correlate the resource named by `value` while retaining the containing User Photo row as provenance.
            * **Interpretation:** Databricks reports this value on the User Photo object returned for Users; it is interpreted at one User Photo record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-preferredlanguage-54e3a5dc57e3" title="Preferred Language" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.preferredLanguage`

            Preferred Language records preferred language of the user (BCP 47 language tag). It is needed to preserve the Databricks-reported language or locale preference for this identity.

            * **Enables:** select identities by the exact `preferredLanguage` language or locale tag without inferring physical location.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is interpreted at one Databricks User record per row; this Databricks-reported setting or qualifier does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-roles-af24d8fb16b9" title="Roles" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.roles`

            Roles records array of roles assigned to the user. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `roles` to examine the returned roles details for the containing Databricks User record.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-roles-ref-8d6920f826a9" title="Resource Reference" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.roles.$ref`

            Resource Reference records SCIM reference URI for the role resource. 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 `$ref` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** Databricks reports this value on the User Role object returned for Users; it is link at one User Role record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-roles-display-0bfd170ea951" title="Display" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.roles.display`

            Display records display name of the role. 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 `display` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** Databricks reports this value on the User Role object returned for Users; it is interpreted at one User Role 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-databricks-users-roles-type-889e3e4b055c" title="Type" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.roles.type`

            Type records type of the role. 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 `type` access-related value being investigated.
            * **Interpretation:** Databricks reports this value on the User Role object returned for Users; it is interpreted at one User Role record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are Databricks-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-roles-value-89328da5a687" title="Value" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.roles.value`

            Value records the role identifier or name. 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 `value` access value with the resource, account, or membership represented by the same Users row.
            * **Interpretation:** Databricks reports this value on the User Role 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-databricks-users-schemas-a88f3d9ed109" title="Schemas" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `users.schemas`

            Schemas records SCIM schema URNs that apply to this user resource. It is needed to preserve the nested schemas relationship or details on the parent Databricks User record.

            * **Enables:** expand `schemas` to connect the containing Databricks User row to its returned schemas entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one returned collection per containing Databricks User object.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-timezone-6f5c96d8dfb8" title="Timezone" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.timezone`

            Timezone records timezone of the user (IANA timezone identifier). It is needed to preserve the Databricks-reported timezone or locale setting for the same record.

            * **Enables:** compare the Databricks-reported timezone or locale setting in `timezone` for individual Users rows without treating it as a verified physical location.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is an identifier, not a measured quantity; the value is timezone or locale setting; this Databricks-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-title-38318698d9d6" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.title`

            Title records title of the user (e.g., 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:** Databricks reports this value on the Databricks User object returned for Users; it is interpreted at one Databricks User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-b2cbd7663180" title="Urn Ietf Params SCIM Schemas Extension Enterprise 2 0 User" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User`

            Urn Ietf Params SCIM Schemas Extension Enterprise 2 0 User records SCIM enterprise user extension attributes. It is needed to preserve the nested urn ietf params scim schemas extension enterprise 2 0 user relationship or details on the parent Databricks User record.

            * **Enables:** expand `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User` to connect the containing Databricks User row to its returned urn ietf params scim schemas extension enterprise 2 0 user entries.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is one nested object per containing Databricks User object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-fd608cfc1fc9" title="Cost Center" icon="sack-dollar" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.costCenter`

            Cost Center records cost center the user belongs to. It is needed to preserve the exact Databricks-reported business, directory, or identity attribute represented by this field.

            * **Enables:** match or segment Users records by `costCenter` only within the same Databricks attribute contract.
            * **Interpretation:** Databricks reports this value on the Scim Enterprise User Extension object returned for Users; it is interpreted at one Scim Enterprise User Extension record per row; the value is a Databricks-returned or configured label and is not a universal identity or business taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-75bbcdd52020" title="Department" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.department`

            Department records department the user belongs to. It is needed to compare the returned department for individual Users rows and select rows with a specific `department` value.

            * **Enables:** trace the department relationship returned in `department` from the Scim Enterprise User Extension row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Scim Enterprise User Extension object returned for Users; it is interpreted at one Scim Enterprise User Extension record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-bf1c8cd73c11" title="Division" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.division`

            Division records division the user belongs to. It is needed to preserve the exact Databricks-reported business, directory, or identity attribute represented by this field.

            * **Enables:** match or segment Users records by `division` only within the same Databricks attribute contract.
            * **Interpretation:** Databricks reports this value on the Scim Enterprise User Extension object returned for Users; it is interpreted at one Scim Enterprise User Extension record per row; the value is a Databricks-returned or configured label and is not a universal identity or business taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-f9b3f4e1c288" title="Employee Number" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.employeeNumber`

            Employee Number records employee number. It is needed to refer to the same employee number across records without relying on display text.

            * **Enables:** match `employeeNumber` to employee number references carrying the same Databricks-issued value in related Databricks records.
            * **Interpretation:** Databricks reports this value on the Scim Enterprise User Extension object returned for Users; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-44ad37863cd2" title="Manager" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.manager`

            Manager records manager reference for the user. It is needed to preserve the nested manager relationship or details on the parent Scim Enterprise User Extension record.

            * **Enables:** expand `manager` to connect the containing Scim Enterprise User Extension row to its returned manager entries.
            * **Interpretation:** Databricks reports this value on the Scim Enterprise User Extension object returned for Users; it is one nested object per containing Scim Enterprise User Extension object when present.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-b2e84b1f9227" title="Resource Reference" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.manager.$ref`

            Resource Reference records SCIM reference URI for the manager resource. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact Databricks resource referenced by `$ref` while retaining the containing Users record as provenance.
            * **Interpretation:** Databricks reports this value on the Scim Manager object returned for Users; it is link at one Scim Manager 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-databricks-users-urn-ietf-params-scim-schemas-ex-880160d8bb41" title="Display Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.manager.displayName`

            Display Name records display name of the manager. 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 `displayName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Scim Manager object returned for Users; it is interpreted at one Scim Manager record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-b01acda92532" title="Value" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.manager.value`

            Value records SCIM ID of the manager. 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 `value` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Scim Manager object returned for Users; it is interpreted at one Scim Manager record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-urn-ietf-params-scim-schemas-ex-5676b70ce210" title="Organization" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.organization`

            Organization records organization the user belongs to. It is needed to compare the returned organization for individual Users rows and select rows with a specific `organization` value.

            * **Enables:** trace the organization relationship returned in `organization` from the Scim Enterprise User Extension row to its named Databricks context.
            * **Interpretation:** Databricks reports this value on the Scim Enterprise User Extension object returned for Users; it is interpreted at one Scim Enterprise User Extension record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-username-58ed8aa45e84" title="User Name" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `users.userName`

            User Name records username of the user (often an email, but not guaranteed to be one). 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 `userName` value where it recurs in Databricks.
            * **Interpretation:** Databricks reports this value on the Databricks User object returned for Users; it is interpreted at one Databricks User record per row.
          </Accordion>

          <Accordion id="provider-permission-field-databricks-users-usertype-69e53f307983" title="User Type" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.userType`

            User Type records type of user (e.g., Employee, Contractor). It is needed to distinguish Users rows by the exact Databricks-returned user type value.

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

  <Tab title="Troubleshooting">
    If validation fails, confirm that the credential is active, the configured account can read the required resources, and every connection field matches the Provider environment.
    Parable never returns stored secret values; replace a secret in the connection form when it has expired or been revoked.
  </Tab>
</Tabs>