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

# Anaplan API

> Anaplan is a cloud-based enterprise planning platform that provides REST APIs for bulk data import/export, transactional data operations, model lifecycle management, audit logging, user identity management (SCIM), and financial consolidation across workspaces and models.

Anaplan is a cloud-based enterprise planning platform that provides REST APIs for bulk data import/export, transactional data operations, model lifecycle management, audit logging, user identity management (SCIM), and financial consolidation across workspaces and models.

<Tabs>
  <Tab title="Overview">
    Connect Parable to Anaplan for workspace, SCIM, and audit data using email and password with HTTP Basic authentication against the Anaplan token endpoint.

    #### Planning data

    Models, lists, workspaces you can access with the integration account

    #### Identity & audit

    SCIM users and groups (with Tenant Admin), audit events (with Tenant Auditor)

    ## Data streams

    This Provider Plugin defines 20 data streams.

    | Stream                    | Description                                                                                                                                                                                                                                                              | Sync        |
    | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- |
    | `workspaces`              | Lists all workspaces accessible to the authenticated user. Core organizational container in Anaplan.                                                                                                                                                                     | full        |
    | `models`                  | Lists all models across all workspaces accessible to the authenticated user, with optional detailed memory usage information.                                                                                                                                            | full        |
    | `workspace_models`        | Lists all models within a specific workspace. Useful for workspace-scoped model enumeration.                                                                                                                                                                             | full        |
    | `model_exports`           | Lists all export action definitions within a specific model. Export actions define data extractions from Anaplan modules/views.                                                                                                                                          | full        |
    | `model_imports`           | Lists all import action definitions within a specific model. Import actions define data loading configurations into Anaplan.                                                                                                                                             | full        |
    | `model_actions`           | Lists all actions (delete actions, other named actions) defined within a specific model.                                                                                                                                                                                 | full        |
    | `model_files`             | Lists all files (data sources and export outputs) within a specific model.                                                                                                                                                                                               | full        |
    | `model_lists`             | Lists all lists (dimensions/hierarchies) defined within a specific model. Lists are core structural elements in Anaplan.                                                                                                                                                 | full        |
    | `list_items`              | Retrieves all items within a specific list (dimension members). These are the actual data records within Anaplan lists/hierarchies.                                                                                                                                      | full        |
    | `model_modules`           | Lists all modules defined within a specific model. Modules are the primary data containers in Anaplan holding line items and views.                                                                                                                                      | full        |
    | `module_views`            | Lists all saved views within a specific module. Views represent different perspectives/layouts of module data.                                                                                                                                                           | full        |
    | `model_line_items`        | Lists all line items defined within a specific model. Line items are the individual data elements (metrics/measures) in Anaplan modules.                                                                                                                                 | full        |
    | `cloudworks_connections`  | Lists all CloudWorks connections configured for the tenant. Connections define external data source/destination endpoints (S3, Azure Blob, BigQuery, etc.).                                                                                                              | full        |
    | `cloudworks_integrations` | Lists all CloudWorks integrations configured for the tenant. Integrations define automated data flows between Anaplan models and external cloud services.                                                                                                                | full        |
    | `cloudworks_run_history`  | Lists CloudWorks integration run history records. Provides execution logs showing when integrations ran, their status, and duration.                                                                                                                                     | full        |
    | `users`                   | Lists all users in the Anaplan tenant via the Integration API v2. Returns user identity, email, active status, and admin role. Does not require SCIM provisioning or Enterprise tier.                                                                                    | full        |
    | `scim_users`              | Lists all users provisioned in the Anaplan tenant via SCIM 2.0. Returns user identity, email, active status, and workspace assignments.                                                                                                                                  | full        |
    | `audit_events`            | Retrieves audit events from the Anaplan tenant. Captures who-did-what-when across the platform including model changes, user actions, data imports/exports, and administrative operations. Anaplan retains up to 30 days of audit history. Requires Tenant Auditor role. | incremental |
    | `model_calendar`          | Retrieves the calendar/time configuration for an Anaplan model, including fiscal year settings, time ranges, and period definitions. This is a model-level metadata object but returns structured time taxonomy data.                                                    | full        |
    | `model_versions`          | Retrieves version information (revision tags) for Anaplan models via the ALM API. Tracks model versioning history including who created each version and when, supporting change management and activity tracking.                                                       | full        |
  </Tab>

  <Tab title="Setup Guide">
    ### Basic authentication

    #### What You'll Need

    | Credential   | What it is                     |
    | ------------ | ------------------------------ |
    | **Email**    | Anaplan integration user email |
    | **Password** | Anaplan account password       |

    > **Info:** **Setup access in Anaplan.** These steps require **Tenant Admin / Workspace Admin as required for the data you sync**, or a colleague with equivalent permissions who can create credentials for you.
    >
    > If that is not you, ask your Anaplan administrator.

    * **Workspace Admin** on all workspaces you want to sync
    * **Tenant Admin** (required for SCIM user and group access)
    * **Tenant Auditor** (required for audit event access)

    > **Info:** Designate the integration account as an **Exception User** under **Administration → Security Policies** so optional password rotation does not break the connection.

    #### Step 1: Confirm integration account

    Use (or create) a dedicated Anaplan user for Parable. Grant the roles above for the workspaces and APIs you need.

    #### Step 2: How authentication works

    Parable sends **email** and **password** to `https://auth.anaplan.com/token/authenticate` using HTTP Basic auth. Anaplan returns a short-lived `AnaplanAuthToken` for API calls; Parable refreshes it automatically.

    #### Step 3: Enter values in the form

    1. **Email** and **Password**: Enter the integration user credentials in the Provider form.
    2. Click **Save & test connection**.

    ```bash Token endpoint theme={null}
    curl -u "your-email@company.com" \
      -X POST -H "Content-Type: application/json" -d '' \
      https://auth.anaplan.com/token/authenticate
    ```

    > **Info:** Omitting the password after the colon makes curl prompt for it interactively so it is not stored in shell history.

    > **Success:** **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:** A successful response includes `tokenInfo.tokenValue`.

    > **Tip:** **Rate Limits:** Anaplan enforces rate limits of **varies by API; implement backoff for throttling**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
  </Tab>

  <Tab title="Permissions">
    <AccordionGroup>
      <Accordion id="provider-permission-tap-anaplan-audit-events-39bcbe14d169" title="Audit Events" icon="shield-check" iconType="sharp-duotone-solid">
        Developer identifier: `audit_events`

        Audit Events contain audit events from the Anaplan tenant. Captures who-did-what-when across the platform including model changes, user actions, data imports/exports, and administrative operations. Anaplan retains up to 30 days of audit history. Requires Tenant Auditor role.

        * **Enables:** trace recorded Anaplan changes and administrative actions to their actor and event time.
        * **Scope:** Reads provider changes through `POST https://audit.anaplan.com/audit/api/1/events/search?limit=10000` using the declared incremental request boundary. The operation requires the Tenant Auditor role and is limited to Anaplan's retained audit window, described here as up to 30 days.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-c0e5b1556129" title="Action Details" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails`

            Action Details records detailed information about the specific action performed. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret action details according to the provider and Workspace configuration that produced each audit event record.
            * **Interpretation:** Keys and value shapes within `actionDetails` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-actionid-44ddab73fcb1" title="Action ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.actionId`

            Action ID captures the identifier of the action definition (e.g., import ID, export ID, process ID). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same action ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `actionId` as a record-level identifier on `ActionDetails`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-actionname-8a71abd79725" title="Action Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.actionName`

            Action Name captures the name of the action definition. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact action name value attached to each action detail record.
            * **Interpretation:** The provider supplies `actionName` at action detail granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-actiontype-18851d328b8f" title="Action Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.actionType`

            Action Type captures the type of action (e.g., import, export, process, delete). It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported action type value when describing their recorded state.
            * **Interpretation:** The provider supplies `actionType` per action detail record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-changedproper-682dabd00448" title="Changed Properties" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.changedProperties`

            Changed Properties records list of properties that were changed during the event. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested changed properties object into its declared child fields for each action detail record.
            * **Interpretation:** The provider returns `changedProperties` as a list on `ActionDetails`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-changedproper-d8705b9c9036" title="New Value" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.changedProperties.newValue`

            New Value captures the new value of the property after the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded new value with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `newValue` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-changedproper-2ed9ebac187e" title="Old Value" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.changedProperties.oldValue`

            Old Value captures the previous value of the property before the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded old value with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `oldValue` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-changedproper-813b9e46033a" title="Property Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.changedProperties.propertyName`

            Property Name captures the name of the property that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact property name value attached to each changed property record.
            * **Interpretation:** The provider supplies `propertyName` at changed property granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-durationms-20d3f25a6eb8" title="Duration Ms" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.durationMs`

            Duration Ms captures the duration of the action in milliseconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by duration ms across audit event records.
            * **Interpretation:** The provider supplies `durationMs` per action detail record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-failurecount-6a05d9606b5e" title="Failure Count" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.failureCount`

            Failure Count captures the number of records that failed during the action. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported failure count for each action detail record.
            * **Interpretation:** The provider supplies `failureCount` at action detail granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-recordcount-684fc45018d2" title="Record Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.recordCount`

            Record Count captures the number of records processed by the action, if applicable. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported record count for each action detail record.
            * **Interpretation:** The provider supplies `recordCount` at action detail granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-sourcefileid-19dce8c88719" title="Source File ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.sourceFileId`

            Source File ID captures the file ID used as the source for an import action. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same source file ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sourceFileId` as a record-level identifier on `ActionDetails`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-sourcefilenam-c7fd8ae0bea2" title="Source File Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.sourceFileName`

            Source File Name captures the file name used as the source for an import action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact source file name value attached to each action detail record.
            * **Interpretation:** The provider supplies `sourceFileName` at action detail granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-targetlistid-8214a5d63ca1" title="Target List ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.targetListId`

            Target List ID captures the target list ID for an import action. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same target list ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetListId` as a record-level identifier on `ActionDetails`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-targetmodulei-5148a10e107f" title="Target Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.targetModuleId`

            Target Module ID captures the target module ID for an import action. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same target module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetModuleId` as a record-level identifier on `ActionDetails`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-taskid-b948c4fc79dd" title="Task ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.taskId`

            Task ID captures the task ID if the action was executed as an asynchronous task. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same task ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `taskId` as a record-level identifier on `ActionDetails`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-actiondetails-taskstate-d6988f538334" title="Task State" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.actionDetails.taskState`

            Task State captures the final state of the task (e.g., COMPLETE, FAILED, CANCELLED). It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported task state value when describing their recorded state.
            * **Interpretation:** The provider supplies `taskState` per action detail record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-activityid-86d5ce2f01ad" title="Activity ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.activityId`

            Activity ID is the identifier linking related audit events within a single activity or transaction. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same activity ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `activityId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-additionalattributes-95ca37a83c1e" title="Additional Attributes" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.additionalAttributes`

            Additional Attributes records event-specific attributes that vary by event type, returned as a key-value map by the Anaplan audit API. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact additional attributes when validating the configuration or technical definition of a audit event record.
            * **Interpretation:** The provider supplies `additionalAttributes` as configuration or technical metadata on `AuditEvent`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-checksum-1b0c23edd7dc" title="Checksum" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.checksum`

            Checksum records integrity checksum returned by the Anaplan audit API for the event record. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact checksum when validating the configuration or technical definition of a audit event record.
            * **Interpretation:** The provider supplies `checksum` as configuration or technical metadata on `AuditEvent`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-createddate-0c4239fc7c37" title="Created Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.createdDate`

            Created Date records epoch timestamp (milliseconds) when the audit record was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place audit event records on a timeline by created date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdDate` per audit event record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-createdtimezone-cfece0b7a121" title="Created Time Zone" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.createdTimeZone`

            Created Time Zone records time zone associated with `createdDate` when returned by the audit API. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for audit events using the recorded created time zone.
            * **Interpretation:** The provider supplies `createdTimeZone` as location or localization context per audit event record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-errormessage-9abde5dbd34d" title="Error Message" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.errorMessage`

            Error Message records error message if the action was unsuccessful. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact error message value attached to each audit event record.
            * **Interpretation:** The provider supplies `errorMessage` at audit event granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-eventcategory-1f5d8fa031e7" title="Event Category" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.eventCategory`

            Event Category states high-level category grouping for the audit event. It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported event category value when describing their recorded state.
            * **Interpretation:** The provider supplies `eventCategory` per audit event record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-eventdate-c67b27c1fc20" title="Event Date" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.eventDate`

            Event Date captures the epoch timestamp (in milliseconds) when the event occurred. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place audit event records on a timeline by event date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `eventDate` per audit event record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-eventdateiso-9f2441b077ac" title="Event Date Iso" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.eventDateIso`

            Event Date Iso records ISO 8601 formatted timestamp of when the event occurred. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place audit event records on a timeline by event date iso and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `eventDateIso` per audit event record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-eventtimezone-b24f7b89a3b8" title="Event Time Zone" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.eventTimeZone`

            Event Time Zone records time zone associated with `eventDate` when returned by the audit API. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for audit events using the recorded event time zone.
            * **Interpretation:** The provider supplies `eventTimeZone` as location or localization context per audit event record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-eventtype-6b0ccd27d410" title="Event Type" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.eventType`

            Event Type states optional category label for the audit event when the audit API returns it. Live search results typically use `eventTypeId` instead. It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported event type value when describing their recorded state.
            * **Interpretation:** The provider supplies `eventType` per audit event record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-eventtypeid-9631a0bcff87" title="Event Type ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.eventTypeId`

            Event Type ID identifies event type code returned by the Anaplan audit API (for example USR-8). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same event type ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `eventTypeId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-hostname-63557265d43e" title="Host Name" icon="network-wired" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.hostName`

            Host Name captures the hostname or server from which the action was performed. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact host name when validating the configuration or technical definition of a audit event record.
            * **Interpretation:** The provider supplies `hostName` as configuration or technical metadata on `AuditEvent`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-id-b131734bfa79" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.id`

            ID is the unique identifier for the audit event. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same audit event source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per audit event record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-ipaddress-e283d7cf282f" title="IP Address" icon="ip" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.ipAddress`

            IP Address captures the IP address from which the action was performed. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** segment audit event records by the recorded IP address without inferring a person's physical presence.
            * **Interpretation:** The provider supplies `ipAddress` as location or localization context per audit event record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-message-557a76538c2b" title="Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.message`

            Message records human-readable description of the audit event. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact message value attached to each audit event record.
            * **Interpretation:** The provider supplies `message` at audit event granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-modelid-ef2af9a9b08e" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.modelId`

            Model ID captures the model ID in which the event occurred, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-modelname-787a60d6195d" title="Model Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.modelName`

            Model Name captures the name of the model in which the event occurred. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact model name value attached to each audit event record.
            * **Interpretation:** The provider supplies `modelName` at audit event granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-objectid-03551527e575" title="Object ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.objectId`

            Object ID captures the unique identifier of the primary object affected by the event. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same object ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `objectId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-objectname-05f7017391df" title="Object Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.objectName`

            Object Name captures the name of the primary object affected by the event. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact object name value attached to each audit event record.
            * **Interpretation:** The provider supplies `objectName` at audit event granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-objecttype-493b10700843" title="Object Type" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.objectType`

            Object Type captures the type of the primary object affected (e.g., model, workspace, list, module). It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported object type value when describing their recorded state.
            * **Interpretation:** The provider supplies `objectType` per audit event record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-parameters-d0edbc16fa2f" title="Parameters" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.parameters`

            Parameters records additional parameters or context details associated with the audit event. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret parameters according to the provider and Workspace configuration that produced each audit event record.
            * **Interpretation:** Keys and value shapes within `parameters` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-parameters-name-76b117bbf11d" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.parameters.name`

            Name captures the parameter name or key. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same audit event parameter source row before constructing its represented state.
            * **Interpretation:** The provider supplies `name` at one value per audit event parameter record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-parameters-type-32ee737c690b" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.parameters.type`

            Type captures the data type or classification of the parameter value. It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per audit event parameter record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-parameters-value-ead5b266809c" title="Value" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.parameters.value`

            Value captures the parameter value. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded value with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `value` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-roleid-9e0551327e8f" title="Role ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.roleId`

            Role ID captures the role ID involved in the event, if applicable (e.g., role grant/revoke). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same role ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `roleId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-rolename-22b89326baa6" title="Role Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.roleName`

            Role Name captures the name of the role involved in the event. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported role name attached to each audit event record.
            * **Interpretation:** The provider supplies `roleName` at audit event granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-sessionid-80387bed6428" title="Session ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.sessionId`

            Session ID captures the session identifier associated with the user's session at the time of the event. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same session ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sessionId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-sourcetype-3632698eb1c1" title="Source Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.sourceType`

            Source Type captures the source or channel through which the action was initiated. It preserves the provider's current classification of this record.

            * **Enables:** separate audit event records by the exact provider-reported source type value when describing their recorded state.
            * **Interpretation:** The provider supplies `sourceType` per audit event record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-success-56868e47993d" title="Success" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.success`

            Success indicates whether the audited action completed successfully. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select audit event records for which the provider reports success as true or false.
            * **Interpretation:** The provider supplies `success` as a boolean per audit event record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-targetuseremail-33537a18c020" title="Target User Email" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.targetUserEmail`

            Target User Email captures the email of the target user, if the event involves an action on another user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the audit event record to the provider-reported actor represented by target user email.
            * **Interpretation:** The provider supplies `targetUserEmail` as identity or attribution context on each audit event record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-targetuserid-026dafe2ae8c" title="Target User ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.targetUserId`

            Target User ID captures the user ID of the target user, if the event involves an action on another user (e.g., role assignment). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same target user ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetUserId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-tenantid-40d63ecb468f" title="Tenant ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.tenantId`

            Tenant ID captures the Anaplan tenant ID associated with this audit event. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same tenant ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `tenantId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-useragent-a8c34f2fadc5" title="User Agent" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.userAgent`

            User Agent records user-Agent string for the client that performed the action, when present. It preserves the client environment reported with the event.

            * **Enables:** count Mixpanel events by the reported user agent client environment.
            * **Interpretation:** Mixpanel supplies `userAgent` per tracked event from client metadata; missing values do not identify an operating system or browser.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-useremail-14e4a9ec7ac5" title="User Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.userEmail`

            User Email captures the email address of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the audit event record to the provider-reported actor represented by user email.
            * **Interpretation:** The provider supplies `userEmail` as identity or attribution context on each audit event record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-userid-57baa50ead52" title="User ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.userId`

            User ID captures the unique identifier of the user who performed the action. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same user ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `userId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-username-419e6dec8cff" title="User Name" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.userName`

            User Name captures the display name or email of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the audit event record to the provider-reported actor represented by user name.
            * **Interpretation:** The provider supplies `userName` as identity or attribution context on each audit event record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-workspaceid-f0bb5c8dd514" title="Workspace ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.workspaceId`

            Workspace ID captures the workspace ID in which the event occurred, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match audit event records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `AuditEvent`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-audit-events-workspacename-c60081126f92" title="Workspace Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `audit_events.workspaceName`

            Workspace Name captures the name of the workspace in which the event occurred. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact workspace name value attached to each audit event record.
            * **Interpretation:** The provider supplies `workspaceName` at audit event granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-cloudworks-connections-aa8e3c17d2ea" title="Cloudworks Connections" icon="route" iconType="sharp-duotone-solid">
        Developer identifier: `cloudworks_connections`

        Cloudworks Connections contain all CloudWorks connections configured for the tenant. Connections define external data source/destination endpoints (S3, Azure Blob, BigQuery, etc.).

        * **Enables:** review the external connection definitions available to CloudWorks integrations.
        * **Scope:** Reads the declared collection through `GET /cloudworks/2/0/integrations/connections` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-5a35bb7ac168" title="Body" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body`

            Body records connection-specific configuration details such as bucket name, container, project, etc. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret body according to the provider and Workspace configuration that produced each cloudworks connection record.
            * **Interpretation:** Keys and value shapes within `body` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-accesskeyid-68c39bd0d975" title="Access Key ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.accessKeyId`

            Access Key ID identifies AWS access key ID for S3 connections (may be masked or omitted in responses). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks connection records to provider records that carry the same access key ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `accessKeyId` as a record-level identifier on `ConnectionBody`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-account-6c8f5f0124e4" title="Account" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.account`

            Account records snowflake account identifier. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested account object into its declared child fields for each connection body record.
            * **Interpretation:** The provider returns `account` as a nested object or reference on `ConnectionBody`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-authtype-a3e87a566de8" title="Auth Type" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.authType`

            Auth Type states authentication type used by the connection (e.g., password, key, token, oauth). It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported auth type attached to each connection body record.
            * **Interpretation:** The provider supplies `authType` at connection body granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-bucket-6298a9b80389" title="Bucket" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.bucket`

            Bucket records s3 bucket name or GCS bucket name (applicable to AmazonS3, GoogleCloudStorage). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact bucket when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `bucket` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-catalog-145d0b03c58f" title="Catalog" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.catalog`

            Catalog records catalog name for Databricks Unity Catalog or similar. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact catalog when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `catalog` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-containernam-f55f2723c64d" title="Container Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.containerName`

            Container Name records Azure Blob Storage container name. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact container name when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `containerName` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-database-05f3f5927386" title="Database" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.database`

            Database records database name for Snowflake, Redshift, JDBC, AzureSql, or AzureSynapse connections. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact database when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `database` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-datasetid-fe1df1194e57" title="Dataset ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.datasetId`

            Dataset ID identifies bigQuery dataset ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks connection records to provider records that carry the same dataset ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `datasetId` as a record-level identifier on `ConnectionBody`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-externalid-f8a6ab6ee501" title="External ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.externalId`

            External ID identifies external ID used with the IAM role for S3 cross-account access. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks connection records to provider records that carry the same external ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `externalId` as a record-level identifier on `ConnectionBody`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-host-4b8f50166674" title="Host" icon="ip" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.host`

            Host records hostname or IP address for SFTP, JDBC, Snowflake, Databricks, or database connections. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact host when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `host` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-httppath-6705a0b52b21" title="HTTP Path" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.httpPath`

            HTTP Path records databricks HTTP path for SQL endpoint. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact HTTP path when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `httpPath` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-port-cfbca28657e0" title="Port" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.port`

            Port records the network port configured for an SFTP, JDBC, or database connection. It preserves the connection endpoint setting used with the host and protocol.

            * **Enables:** construct and audit the destination endpoint for each CloudWorks connection.
            * **Interpretation:** The provider supplies `port` as an integer connection setting, not a quantity or duration; a missing value may leave protocol-default behavior to other configuration.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-projectid-64a865cd7d39" title="Project ID" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.projectId`

            Project ID identifies Google Cloud project ID for BigQuery or GCS connections. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks connection records to provider records that carry the same project ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `projectId` as a record-level identifier on `ConnectionBody`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-region-5380014cea57" title="Region" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.region`

            Region records AWS region for S3 connections (e.g., us-east-1). It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** segment cloudworks connection records by the recorded region without inferring a person's physical presence.
            * **Interpretation:** The provider supplies `region` as location or localization context per connection body record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-rolearn-1cf0bcc14393" title="Role Arn" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.roleArn`

            Role Arn states AWS IAM role ARN used for cross-account access to S3. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported role arn attached to each connection body record.
            * **Interpretation:** The provider supplies `roleArn` at connection body granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-sastoken-48a8d03eab6d" title="SAS Token" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.sasToken`

            SAS Token states Azure SAS token for authentication (may be masked in responses). It documents the access-related value reported for this object or membership.

            * **Enables:** confirm which CloudWorks connection authentication mode is configured during narrowly authorized troubleshooting without revealing the token value.
            * **Interpretation:** Anaplan may mask `sasToken` in responses; treat any returned value as sensitive configuration metadata, never expose it, and never assume it is a reusable credential.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-schema-252356348431" title="Schema" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.schema`

            Schema records schema name within the database (Snowflake, Redshift, etc.). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact schema when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `schema` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-serviceaccou-6f3f8e2dad56" title="Service Account Email" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.serviceAccountEmail`

            Service Account Email records Google service account email used for authentication. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the connection body record to the provider-reported person or account represented by service account email.
            * **Interpretation:** The provider supplies `serviceAccountEmail` as identity or attribution context on each connection body record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-storageaccou-35d0b5e8e4ef" title="Storage Account Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.storageAccountName`

            Storage Account Name records Azure Storage account name. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact storage account name when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `storageAccountName` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-url-90dfac7d019b" title="URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.url`

            URL records connection URL for Databricks, JDBC, or other URL-based connections. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by URL on a connection body record.
            * **Interpretation:** The provider supplies `url` as a URL or resource locator on each connection body record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-username-23b4401b1289" title="User Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.username`

            User Name records username for SFTP, database, or other credential-based connections. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the connection body record to the provider-reported actor represented by user name.
            * **Interpretation:** The provider supplies `username` as identity or attribution context on each connection body record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-body-warehouse-5605249f11c9" title="Warehouse" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.body.warehouse`

            Warehouse records snowflake warehouse name. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact warehouse when validating the configuration or technical definition of a connection body record.
            * **Interpretation:** The provider supplies `warehouse` as configuration or technical metadata on `ConnectionBody`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-connectionid-35ee3a5138c2" title="Connection ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.connectionId`

            Connection ID is the unique identifier for the CloudWorks connection. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same cloud works connection source row before constructing its represented state.
            * **Interpretation:** The provider supplies `connectionId` at one value per cloud works connection record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-createdat-d1980673d4ae" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.createdAt`

            Created At records ISO 8601 timestamp when the connection was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks connection records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdAt` per cloud works connection record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-createdby-b9a4073d089e" title="Created By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.createdBy`

            Created By records identifier or email of the user who created the connection. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the cloud works connection record to the provider-reported person or account represented by created by.
            * **Interpretation:** The provider supplies `createdBy` as identity or attribution context on each cloud works connection record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-modifiedat-be52dd656ece" title="Modified At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.modifiedAt`

            Modified At records ISO 8601 timestamp when the connection was last modified. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks connection records on a timeline by modified at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `modifiedAt` per cloud works connection record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-modifiedby-c2cb82432e38" title="Modified By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.modifiedBy`

            Modified By records identifier or email of the user who last modified the connection. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the cloud works connection record to the provider-reported person or account represented by modified by.
            * **Interpretation:** The provider supplies `modifiedBy` as identity or attribution context on each cloud works connection record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-name-bb5d9906b209" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.name`

            Name records human-readable name of the connection. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each cloud works connection record.
            * **Interpretation:** The provider supplies `name` at cloud works connection granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-connections-type-796b2bb98950" title="Type" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_connections.type`

            Type captures the type of external service this connection targets (e.g., AmazonS3, AzureBlob, GoogleBigQuery). It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks connection records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per cloud works connection record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-cloudworks-integrations-dbc09aacf0a2" title="Cloudworks Integrations" icon="route" iconType="sharp-duotone-solid">
        Developer identifier: `cloudworks_integrations`

        Cloudworks Integrations contain all CloudWorks integrations configured for the tenant. Integrations define automated data flows between Anaplan models and external cloud services.

        * **Enables:** map automated CloudWorks data flows to their model and connection configuration.
        * **Scope:** Reads the declared collection through `GET /cloudworks/2/0/integrations` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-actionid-709ef7711314" title="Action ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.actionId`

            Action ID is the identifier of the Anaplan import or export action linked to this integration. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same action ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `actionId` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-connectionid-4e7072009563" title="Connection ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.connectionId`

            Connection ID is the identifier of the CloudWorks connection (external cloud service) used by this integration. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same connection ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `connectionId` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-connectiontype-874e9684898b" title="Connection Type" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.connectionType`

            Connection Type captures the type of external cloud service connection (e.g., S3, Azure Blob, BigQuery). It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported connection type value when describing their recorded state.
            * **Interpretation:** The provider supplies `connectionType` per cloud works integration record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-createdat-11562a018635" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.createdAt`

            Created At records ISO 8601 timestamp when the integration was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks integration records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdAt` per cloud works integration record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-createdby-31745857d8dd" title="Created By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.createdBy`

            Created By records identifier or email of the user who created the integration. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the cloud works integration record to the provider-reported person or account represented by created by.
            * **Interpretation:** The provider supplies `createdBy` as identity or attribution context on each cloud works integration record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-fileid-c6e09c5a6aff" title="File ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.fileId`

            File ID is the identifier of the Anaplan file used in the integration data transfer. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same file ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `fileId` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-integrationid-0ba1a24fa38a" title="Integration ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.integrationId`

            Integration ID is the unique identifier for the CloudWorks integration. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same cloud works integration source row before constructing its represented state.
            * **Interpretation:** The provider supplies `integrationId` at one value per cloud works integration record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-lastrunstatus-365b3da03544" title="Last Run Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.lastRunStatus`

            Last Run Status states status of the most recent run of this integration. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported last run status value when describing their recorded state.
            * **Interpretation:** The provider supplies `lastRunStatus` per cloud works integration record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-lastruntime-f58af5d0397b" title="Last Run Time" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.lastRunTime`

            Last Run Time records ISO 8601 timestamp of the most recent run. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks integration records on a timeline by last run time and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastRunTime` per cloud works integration record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-lastsuccessfulru-89812681ec77" title="Last Successful Run Time" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.lastSuccessfulRunTime`

            Last Successful Run Time records ISO 8601 timestamp of the most recent successful run. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks integration records on a timeline by last successful run time and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastSuccessfulRunTime` per cloud works integration record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-modelid-627f7b4cc17c" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.modelId`

            Model ID is the identifier of the Anaplan model associated with this integration. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-name-ae358e450fe8" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.name`

            Name records human-readable name of the integration. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each cloud works integration record.
            * **Interpretation:** The provider supplies `name` at cloud works integration granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-notification-b28f721826e2" title="Notification" icon="megaphone" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.notification`

            Notification records notification settings for integration run results. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested notification records contained by each cloud works integration record.
            * **Interpretation:** The provider returns `notification` as a nested object or reference on `CloudWorksIntegration`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-notification-ena-a2ba69bc7cc8" title="Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.notification.enabled`

            Enabled indicates whether notifications are enabled for this integration. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select cloudworks integration records for which the provider reports enabled as true or false.
            * **Interpretation:** The provider supplies `enabled` as a boolean per integration notification record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-notification-not-06cc6607c0bd" title="Notify On Failure" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.notification.notifyOnFailure`

            Notify On Failure indicates whether to send notifications on failed runs. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select cloudworks integration records for which the provider reports notify on failure as true or false.
            * **Interpretation:** The provider supplies `notifyOnFailure` as a boolean per integration notification record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-notification-not-4fd4a9fff8dd" title="Notify On Success" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.notification.notifyOnSuccess`

            Notify On Success indicates whether to send notifications on successful runs. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select cloudworks integration records for which the provider reports notify on success as true or false.
            * **Interpretation:** The provider supplies `notifyOnSuccess` as a boolean per integration notification record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-notification-rec-1b4b21410f4f" title="Recipients" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.notification.recipients`

            Recipients records list of email addresses to receive notifications. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the integration notification record to the provider-reported person or account represented by recipients.
            * **Interpretation:** The provider supplies `recipients` as identity or attribution context on each integration notification record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-nuxvisible-8fc98871b852" title="Nux Visible" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.nuxVisible`

            Nux Visible indicates whether the integration is visible in the new user experience UI. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select cloudworks integration records for which the provider reports nux visible as true or false.
            * **Interpretation:** The provider supplies `nuxVisible` as a boolean per cloud works integration record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-runcount-40bdddfa71ec" title="Run Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.runCount`

            Run Count reports the total number of times this integration has been executed. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported run count for each cloud works integration record.
            * **Interpretation:** The provider supplies `runCount` at cloud works integration granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-bee20f9f6579" title="Schedule" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule`

            Schedule records schedule configuration for automated runs of this integration, if any. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact schedule when validating the configuration or technical definition of a cloud works integration record.
            * **Interpretation:** The provider supplies `schedule` as configuration or technical metadata on `CloudWorksIntegration`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-cronexp-5309ddab40e5" title="Cron Expression" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.cronExpression`

            Cron Expression records cron expression defining the schedule, if applicable. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact cron expression when validating the configuration or technical definition of a integration schedule record.
            * **Interpretation:** The provider supplies `cronExpression` as configuration or technical metadata on `IntegrationSchedule`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-daysofm-5ea14e09a951" title="Days Of Month" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.daysOfMonth`

            Days Of Month records days of the month on which the schedule runs (for monthly schedules). It preserves the provider-defined period or schedule cadence for this record.

            * **Enables:** group cloudworks integration records by the provider-defined days of month period or schedule.
            * **Interpretation:** The provider supplies `daysOfMonth` per integration schedule record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-daysofw-420a50b68a6c" title="Days Of Week" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.daysOfWeek`

            Days Of Week records days of the week on which the schedule runs (for weekly schedules). It preserves the provider-defined period or schedule cadence for this record.

            * **Enables:** group cloudworks integration records by the provider-defined days of week period or schedule.
            * **Interpretation:** The provider supplies `daysOfWeek` per integration schedule record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-enabled-e40ade1801b8" title="Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.enabled`

            Enabled indicates whether the schedule is currently active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select cloudworks integration records for which the provider reports enabled as true or false.
            * **Interpretation:** The provider supplies `enabled` as a boolean per integration schedule record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-enddate-2b4ac6ca7515" title="End Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.endDate`

            End Date records ISO 8601 date or datetime when the schedule ends, if applicable. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks integration records on a timeline by end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `endDate` per integration schedule record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-interva-575686db3938" title="Interval Minutes" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.intervalMinutes`

            Interval Minutes reports interval in minutes between runs for interval-based schedules. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by interval minutes across cloudworks integration records.
            * **Interpretation:** The provider supplies `intervalMinutes` per integration schedule record in the unit stated by the provider description; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-schedul-beca92a64175" title="Schedule ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.scheduleId`

            Schedule ID is the unique identifier for the schedule. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same schedule ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `scheduleId` as a record-level identifier on `IntegrationSchedule`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-startda-4f4a0bb8f30b" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.startDate`

            Start Date records ISO 8601 date or datetime when the schedule begins. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks integration records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per integration schedule record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-time-e7577e26e400" title="Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.time`

            Time records time of day for scheduled execution (HH:mm format). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact time when validating the configuration or technical definition of a integration schedule record.
            * **Interpretation:** The provider supplies `time` as configuration or technical metadata on `IntegrationSchedule`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-timezon-fd40a539d592" title="Timezone" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.timezone`

            Timezone identifies IANA timezone identifier for the schedule (e.g., America/`New_York`). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same timezone, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `timezone` as a record-level identifier on `IntegrationSchedule`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-schedule-type-f9a38ea64409" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.schedule.type`

            Type captures the recurrence type of the schedule. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per integration schedule record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-81831c9720aa" title="Sources" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources`

            Sources lists the configured origin endpoints that feed the integration. It preserves the input-side relationships of the CloudWorks data flow.

            * **Enables:** reconstruct which source connections and processes supply data to each integration.
            * **Interpretation:** The provider returns `sources` as a list of endpoint definitions on `CloudWorksIntegration`; an empty list and an omitted list are distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-actionid-fd9143336bfe" title="Action ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.actionId`

            Action ID identifies Anaplan action identifier (import/export) for Anaplan-type endpoints. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same action ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `actionId` as a record-level identifier on `IntegrationEndpoint`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-bucket-68a5b6a3f7c0" title="Bucket" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.bucket`

            Bucket records bucket or container name in the external cloud storage. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact bucket when validating the configuration or technical definition of a integration endpoint record.
            * **Interpretation:** The provider supplies `bucket` as configuration or technical metadata on `IntegrationEndpoint`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-connecti-fbccd69905f0" title="Connection ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.connectionId`

            Connection ID is the identifier of the CloudWorks connection for external endpoints. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same integration endpoint source row before constructing its represented state.
            * **Interpretation:** The provider supplies `connectionId` at one value per integration endpoint record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-dataset-f099c4ab1952" title="Dataset" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.dataset`

            Dataset records dataset name for BigQuery or similar database endpoints. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact dataset when validating the configuration or technical definition of a integration endpoint record.
            * **Interpretation:** The provider supplies `dataset` as configuration or technical metadata on `IntegrationEndpoint`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-fileid-ebc2bfbe107d" title="File ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.fileId`

            File ID identifies Anaplan file identifier for Anaplan-type endpoints. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same file ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `fileId` as a record-level identifier on `IntegrationEndpoint`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-modelid-88e152960ea1" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.modelId`

            Model ID identifies Anaplan model identifier for Anaplan-type endpoints. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `IntegrationEndpoint`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-path-aab9751b9e45" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.path`

            Path records file path or object key in the external cloud storage. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact path when validating the configuration or technical definition of a integration endpoint record.
            * **Interpretation:** The provider supplies `path` as configuration or technical metadata on `IntegrationEndpoint`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-table-6eb865baa3b8" title="Table" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.table`

            Table states table name for database-type endpoints. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported table value when describing their recorded state.
            * **Interpretation:** The provider supplies `table` per integration endpoint record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-sources-type-c8cacf3dddb3" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.sources.type`

            Type captures the endpoint type (e.g., 'anaplan', 's3', 'azureblob', 'bigquery', 'googlecloud', 'snowflake'). It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per integration endpoint record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-status-46dd903e6f78" title="Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.status`

            Status states current status of the integration. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per cloud works integration record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-targets-33fda56b08f1" title="Targets" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.targets`

            Targets lists the configured destination endpoints that receive integration output. It preserves the output-side relationships of the CloudWorks data flow.

            * **Enables:** reconstruct which target connections and processes receive data from each integration.
            * **Interpretation:** The provider returns `targets` as a list of endpoint definitions on `CloudWorksIntegration`; an empty list and an omitted list are distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-tenantid-f15e2c6d67c1" title="Tenant ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.tenantId`

            Tenant ID is the identifier of the Anaplan tenant that owns this integration. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same tenant ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `tenantId` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-type-1b95842da8ca" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.type`

            Type captures the type/direction of the integration (e.g., import or export). It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks integration records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per cloud works integration record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-updatedat-8ee2e75ffce2" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.updatedAt`

            Updated At records ISO 8601 timestamp when the integration was last updated. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks integration records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updatedAt` per cloud works integration record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-updatedby-02477d32e08b" title="Updated By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.updatedBy`

            Updated By records identifier or email of the user who last updated the integration. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the cloud works integration record to the provider-reported person or account represented by updated by.
            * **Interpretation:** The provider supplies `updatedBy` as identity or attribution context on each cloud works integration record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-version-139206b285e1" title="Version" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.version`

            Version identifies version identifier for the integration configuration. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same version, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `version` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-integrations-workspaceid-b3985b6f259b" title="Workspace ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_integrations.workspaceId`

            Workspace ID is the identifier of the Anaplan workspace associated with this integration. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks integration records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `CloudWorksIntegration`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-cloudworks-run-history-b802fdc905ed" title="Cloudworks Run History" icon="timeline" iconType="sharp-duotone-solid">
        Developer identifier: `cloudworks_run_history`

        Cloudworks Run History contains CloudWorks integration run history records. Provides execution logs showing when integrations ran, their status, and duration.

        * **Enables:** compare integration executions by recorded status, start time, and duration.
        * **Scope:** Reads the declared collection through `GET /cloudworks/2/0/integrations/{id}/runs` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-cancelledby-c35a4cffa67d" title="Cancelled By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.cancelledBy`

            Cancelled By records identifier or email of the user who cancelled the run, if applicable. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the cloud works run history record to the provider-reported person or account represented by cancelled by.
            * **Interpretation:** The provider supplies `cancelledBy` as identity or attribution context on each cloud works run history record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-completedat-69efaa806f60" title="Completed At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.completedAt`

            Completed At states ISO 8601 timestamp indicating when the integration run completed. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported completed at value when describing their recorded state.
            * **Interpretation:** The provider supplies `completedAt` per cloud works run history record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-createdat-ecb96717d4f2" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.createdAt`

            Created At records ISO 8601 timestamp indicating when the run record was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks run history records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdAt` per cloud works run history record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-duration-33989acf403a" title="Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.duration`

            Duration reports duration of the integration run in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by duration across cloudworks run history records.
            * **Interpretation:** The provider supplies `duration` per cloud works run history record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-failedcount-40e1d5a68890" title="Failed Count" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.failedCount`

            Failed Count reports the number of records or items that failed during the run. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported failed count for each cloud works run history record.
            * **Interpretation:** The provider supplies `failedCount` at cloud works run history granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-failuredumpavaila-c912fdefffc7" title="Failure Dump Available" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.failureDumpAvailable`

            Failure Dump Available indicates whether a failure dump file is available for download. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select cloudworks run history records for which the provider reports failure dump available as true or false.
            * **Interpretation:** The provider supplies `failureDumpAvailable` as a boolean per cloud works run history record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-failurereason-c2bc55fda80e" title="Failure Reason" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.failureReason`

            Failure Reason records description of the failure reason if the run did not succeed. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact failure reason value attached to each cloud works run history record.
            * **Interpretation:** The provider supplies `failureReason` at cloud works run history granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-id-81b4ac340beb" title="ID" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.id`

            ID identifies parent key injected by the ingestor from the `cloudworks_integrations` to `cloudworks_run_history` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `CloudWorksRunHistory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-ignoredcount-451891833a3d" title="Ignored Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.ignoredCount`

            Ignored Count reports the number of records or items ignored during the run. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported ignored count for each cloud works run history record.
            * **Interpretation:** The provider supplies `ignoredCount` at cloud works run history granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-integrationid-cb4ccd57b77a" title="Integration ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.integrationId`

            Integration ID is the identifier of the CloudWorks integration that was executed. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same integration ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `integrationId` as a record-level identifier on `CloudWorksRunHistory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-integrationname-02040eea6a3a" title="Integration Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.integrationName`

            Integration Name records human-readable name of the CloudWorks integration. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact integration name value attached to each cloud works run history record.
            * **Interpretation:** The provider supplies `integrationName` at cloud works run history granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-progress-53dc24483c98" title="Progress" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.progress`

            Progress reports the integration run's completion percentage from 0 to 100. It records how far execution advanced at the captured state.

            * **Enables:** distinguish completed, partial, and potentially stalled runs when reviewing run history.
            * **Interpretation:** The provider supplies `progress` as a numeric percentage per CloudWorks run; zero, a partial value, and missing are distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-retrycount-7f793372dcfe" title="Retry Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.retryCount`

            Retry Count reports the number of retry attempts made for this run. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported retry count for each cloud works run history record.
            * **Interpretation:** The provider supplies `retryCount` at cloud works run history granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-runid-03536b883948" title="Run ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.runId`

            Run ID is the unique identifier for this specific integration run. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same cloud works run history source row before constructing its represented state.
            * **Interpretation:** The provider supplies `runId` at one value per cloud works run history record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-scheduleid-43aa77789793" title="Schedule ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.scheduleId`

            Schedule ID is the identifier of the schedule that triggered this run, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same schedule ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `scheduleId` as a record-level identifier on `CloudWorksRunHistory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-2eeb870c4f21" title="Source Info" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo`

            Source Info identifies the source endpoint used by this integration run. It keeps execution history tied to the input-side connection and process details.

            * **Enables:** correlate a run's outcome with the exact source configuration involved in that execution.
            * **Interpretation:** The provider returns `sourceInfo` as a nested `RunEndpointInfo` object; absence means no source detail was reported for the run.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-connec-a5e2a9b3b007" title="Connection ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.connectionId`

            Connection ID is the identifier of the CloudWorks connection used. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same connection ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `connectionId` as a record-level identifier on `RunEndpointInfo`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-connec-48ffa69524c3" title="Connection Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.connectionName`

            Connection Name records name of the CloudWorks connection. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact connection name value attached to each run endpoint info record.
            * **Interpretation:** The provider supplies `connectionName` at run endpoint info granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-fileid-47854af0b613" title="File ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.fileId`

            File ID is the identifier of the file involved in the integration, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same file ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `fileId` as a record-level identifier on `RunEndpointInfo`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-filena-d34e2fe970d3" title="File Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.fileName`

            File Name records name of the file involved in the integration, if applicable. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact file name value attached to each run endpoint info record.
            * **Interpretation:** The provider supplies `fileName` at run endpoint info granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-modeli-fddfa1354950" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.modelId`

            Model ID identifies Anaplan model identifier, if the endpoint is an Anaplan model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `RunEndpointInfo`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-path-4dd19b22881e" title="Path" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.path`

            Path records path or bucket location for cloud storage endpoints. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact path when validating the configuration or technical definition of a run endpoint info record.
            * **Interpretation:** The provider supplies `path` as configuration or technical metadata on `RunEndpointInfo`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-type-4ef0505d2e6b" title="Type" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.type`

            Type states type of the endpoint, such as Anaplan, S3, Azure Blob, or Google BigQuery. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per run endpoint info record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-sourceinfo-worksp-05d33d2ce7a0" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.sourceInfo.workspaceId`

            Workspace ID identifies Anaplan workspace identifier, if the endpoint is an Anaplan model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `RunEndpointInfo`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-startedat-937382f5edc2" title="Started At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.startedAt`

            Started At records ISO 8601 timestamp indicating when the integration run started. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks run history records on a timeline by started at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startedAt` per cloud works run history record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-startedby-c6bd5f6227a1" title="Started By" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.startedBy`

            Started By records identifier or email of the user or system that initiated the run. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the cloud works run history record to the provider-reported person or account represented by started by.
            * **Interpretation:** The provider supplies `startedBy` as identity or attribution context on each cloud works run history record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-status-a156f4641208" title="Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.status`

            Status states current status of the integration run. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per cloud works run history record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-successfulcount-f633a8de83d2" title="Successful Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.successfulCount`

            Successful Count reports the number of records or items successfully processed during the run. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported successful count for each cloud works run history record.
            * **Interpretation:** The provider supplies `successfulCount` at cloud works run history granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-targetinfo-9d5c72741e15" title="Target Info" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.targetInfo`

            Target Info identifies the destination endpoint used by this integration run. It keeps execution history tied to the output-side connection and process details.

            * **Enables:** correlate a run's outcome with the exact target configuration involved in that execution.
            * **Interpretation:** The provider returns `targetInfo` as a nested `RunEndpointInfo` object; absence means no target detail was reported for the run.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-2a29aa7762e9" title="Task Details" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails`

            Task Details records list of individual task details within this integration run. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested task details records contained by each cloud works run history record.
            * **Interpretation:** The provider returns `taskDetails` as a list on `CloudWorksRunHistory`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-actio-700f5e0c87e7" title="Action ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.actionId`

            Action ID is the identifier of the Anaplan action (import/export/process) executed by this task. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same action ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `actionId` as a record-level identifier on `RunTaskDetail`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-compl-213d81fcc1e4" title="Completed At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.completedAt`

            Completed At states ISO 8601 timestamp indicating when the task completed. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported completed at value when describing their recorded state.
            * **Interpretation:** The provider supplies `completedAt` per run task detail record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-faile-35cd31f6c632" title="Failed Count" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.failedCount`

            Failed Count reports the number of records that failed in this task. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported failed count for each run task detail record.
            * **Interpretation:** The provider supplies `failedCount` at run task detail granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-failu-859c1feebd4a" title="Failure Reason" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.failureReason`

            Failure Reason records description of the failure reason for this task, if applicable. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact failure reason value attached to each run task detail record.
            * **Interpretation:** The provider supplies `failureReason` at run task detail granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-ignor-67078afae2e7" title="Ignored Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.ignoredCount`

            Ignored Count reports the number of records ignored by this task. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported ignored count for each run task detail record.
            * **Interpretation:** The provider supplies `ignoredCount` at run task detail granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-model-5115346449c1" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.modelId`

            Model ID is the identifier of the Anaplan model associated with this task. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `RunTaskDetail`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-start-7140bb7bb274" title="Started At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.startedAt`

            Started At records ISO 8601 timestamp indicating when the task started. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks run history records on a timeline by started at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startedAt` per run task detail record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-succe-3eda59dbae58" title="Successful Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.successfulCount`

            Successful Count reports the number of records successfully processed by this task. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported successful count for each run task detail record.
            * **Interpretation:** The provider supplies `successfulCount` at run task detail granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-taski-63c7b3f407d6" title="Task ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.taskId`

            Task ID is the unique identifier for the task. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same run task detail source row before constructing its represented state.
            * **Interpretation:** The provider supplies `taskId` at one value per run task detail record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-taskn-5833e06f9f98" title="Task Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.taskName`

            Task Name records name of the task. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact task name value attached to each run task detail record.
            * **Interpretation:** The provider supplies `taskName` at run task detail granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-tasks-d908e22490dc" title="Task Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.taskStatus`

            Task Status states status of this individual task. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported task status value when describing their recorded state.
            * **Interpretation:** The provider supplies `taskStatus` per run task detail record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-taskt-07d17f000361" title="Task Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.taskType`

            Task Type states type of the task, such as import or export. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported task type value when describing their recorded state.
            * **Interpretation:** The provider supplies `taskType` per run task detail record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-taskdetails-works-79ecc97f06ac" title="Workspace ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.taskDetails.workspaceId`

            Workspace ID is the identifier of the Anaplan workspace associated with this task. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match cloudworks run history records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `RunTaskDetail`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-totalcount-1ab4e272ee4c" title="Total Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.totalCount`

            Total Count reports the total number of records or items processed during the run. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total count for each cloud works run history record.
            * **Interpretation:** The provider supplies `totalCount` at cloud works run history granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-trigger-6ea1119cb2a2" title="Trigger" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.trigger`

            Trigger states how the integration run was triggered. It preserves the provider's current classification of this record.

            * **Enables:** separate cloudworks run history records by the exact provider-reported trigger value when describing their recorded state.
            * **Interpretation:** The provider supplies `trigger` per cloud works run history record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-cloudworks-run-history-updatedat-495fbfde7fc3" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `cloudworks_run_history.updatedAt`

            Updated At records ISO 8601 timestamp indicating when the run record was last updated. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place cloudworks run history records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updatedAt` per cloud works run history record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-list-items-9daa307115c2" title="List Items" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `list_items`

        List Items contain all items within a specific list (dimension members). These are the actual data records within Anaplan lists/hierarchies.

        * **Enables:** enumerate the dimension members contained by each Anaplan list.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{modelId}/lists/{id}/items` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-list-items-code-c8d2cc99aeee" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.code`

            Code contains an optional external code assigned to the list item, often used for integration mapping with external systems. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact code when validating the configuration or technical definition of a anaplan list item record.
            * **Interpretation:** The provider supplies `code` as configuration or technical metadata on `AnaplanListItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-id-39f14363cfda" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.id`

            ID captures the unique numeric identifier of the list item within the Anaplan model. This is the internal Anaplan item ID. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same anaplan list item source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per anaplan list item record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-modelid-2472d9ba35b8" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.modelId`

            Model ID identifies parent `modelId` injected by the ingestor from the `model_lists` to `list_items` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match list item records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `AnaplanListItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-name-a1fdc111d901" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.name`

            Name captures the display name of the list item. This is the human-readable label shown in Anaplan. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each anaplan list item record.
            * **Interpretation:** The provider supplies `name` at anaplan list item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-parent-e6b6bdd44695" title="Parent" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.parent`

            Parent captures the ID of the parent list item in a hierarchical list. Null or absent if the item is a top-level member. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the anaplan list item record to the provider-reported person or account represented by parent.
            * **Interpretation:** The provider supplies `parent` as identity or attribution context on each anaplan list item record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-parentname-9bcbfc7d53e0" title="Parent Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.parentName`

            Parent Name captures the display name of the parent list item, if the list is hierarchical. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact parent name value attached to each anaplan list item record.
            * **Interpretation:** The provider supplies `parentName` at anaplan list item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-properties-bf2a631fab95" title="Properties" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.properties`

            Properties contains a map of custom properties (list-level attributes) defined on the list, keyed by property name or ID. Contains values specific to this list item. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret properties according to the provider and Workspace configuration that produced each list item record.
            * **Interpretation:** Keys and value shapes within `properties` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-properties-additionalproperti-cb86fa6fe19e" title="Additional Properties" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.properties.additionalProperties`

            Additional Properties records each key represents a property name or ID defined on the list. The value contains the property's current value for this list item. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact additional properties value attached to each list item property record.
            * **Interpretation:** The provider supplies `additionalProperties` at list item property granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-properties-additionalproperti-e426569fb39c" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.properties.additionalProperties.id`

            ID identifies for properties that reference another list, the ID of the referenced list item. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match list item records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `ListItemPropertyValue`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-properties-additionalproperti-28d465f590f0" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.properties.additionalProperties.name`

            Name records for properties that reference another list, the name of the referenced list item. For text properties, the text value. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each list item property value record.
            * **Interpretation:** The provider supplies `name` at list item property value granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-properties-additionalproperti-a657ef86a8b3" title="Type" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.properties.additionalProperties.type`

            Type captures the data type of the property value, such as TEXT, NUMBER, BOOLEAN, DATE, or LIST. It preserves the provider's current classification of this record.

            * **Enables:** separate list item records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per list item property value record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-properties-additionalproperti-5bfa3134dae3" title="Value" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.properties.additionalProperties.value`

            Value captures the raw value of the property, represented as a string. Numeric, boolean, and date values are serialized as strings. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place list item records on a timeline by value and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `value` per list item property value record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-subsets-e3384c4693db" title="Subsets" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.subsets`

            Subsets contains a map of subset memberships for this list item, keyed by subset name or ID. Values indicate whether the item belongs to each subset. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact subsets value attached to each anaplan list item record.
            * **Interpretation:** The provider supplies `subsets` at anaplan list item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-subsets-additionalproperties-e4a4f188f147" title="Additional Properties" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.subsets.additionalProperties`

            Additional Properties records true if the list item belongs to the subset identified by the key, false otherwise. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select list item records for which the provider reports additional properties as true or false.
            * **Interpretation:** The provider supplies `additionalProperties` as a boolean per list item subset record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-list-items-workspaceid-28b55557355e" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `list_items.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `model_lists` to `list_items` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match list item records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `AnaplanListItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-actions-c8e4c234115e" title="Model Actions" icon="list-check" iconType="sharp-duotone-solid">
        Developer identifier: `model_actions`

        Model Actions contain all actions (delete actions, other named actions) defined within a specific model.

        * **Enables:** catalog named actions available within each model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/actions` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-actions-actiontype-967443a552c5" title="Action Type" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.actionType`

            Action Type states action type code returned by the Anaplan actions API (for example `DELETE_BY_SELECTION`, `ORDER_HIERARCHY`). It preserves the provider's current classification of this record.

            * **Enables:** separate model action records by the exact provider-reported action type value when describing their recorded state.
            * **Interpretation:** The provider supplies `actionType` per model action record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-id-cae9361e564b" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.id`

            ID is the unique identifier of the action within the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model action source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per model action record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-modelid-79adf09621e6" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.modelId`

            Model ID identifies parent id injected by the ingestor from the `workspace_models` to `model_actions` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model action records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModelAction`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-moduleid-374d767dba5b" title="Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.moduleId`

            Module ID is the identifier of the module associated with this action, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model action records to provider records that carry the same module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `moduleId` as a record-level identifier on `ModelAction`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-modulename-52c401103361" title="Module Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.moduleName`

            Module Name records name of the module associated with this action, if applicable. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact module name value attached to each model action record.
            * **Interpretation:** The provider supplies `moduleName` at model action granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-name-e7df7ce6b9d5" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.name`

            Name records display name of the action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each model action record.
            * **Interpretation:** The provider supplies `name` at model action granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-type-5aeae915caaa" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.type`

            Type states legacy/alternate type field when present. Live Integration API responses use `actionType`. It preserves the provider's current classification of this record.

            * **Enables:** separate model action records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per model action record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-actions-workspaceid-b6e4d6839838" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_actions.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `workspace_models` to `model_actions` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model action records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelAction`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-calendar-8aedce4c71b0" title="Model Calendar" icon="calendar-clock" iconType="sharp-duotone-solid">
        Developer identifier: `model_calendar`

        Model Calendar contains the calendar/time configuration for an Anaplan model, including fiscal year settings, time ranges, and period definitions. This is a model-level metadata object but returns structured time taxonomy data.

        * **Enables:** interpret model periods against the configured fiscal calendar and time ranges.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/modelCalendar` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-calendar-calendartype-82dfba257663" title="Calendar Type" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.calendarType`

            Calendar Type captures the type of calendar used by the model. It preserves the provider's current classification of this record.

            * **Enables:** separate model calendar records by the exact provider-reported calendar type value when describing their recorded state.
            * **Interpretation:** The provider supplies `calendarType` per model calendar record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentfiscalyear-b9220c1f3598" title="Current Fiscal Year" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentFiscalYear`

            Current Fiscal Year records details about the current fiscal year. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested current fiscal year object into its declared child fields for each model calendar record.
            * **Interpretation:** The provider returns `currentFiscalYear` as a nested object or reference on `ModelCalendar`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentfiscalyear-enddate-6f41177bccf5" title="End Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentFiscalYear.endDate`

            End Date captures the end date of the fiscal year in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `endDate` per fiscal year detail record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentfiscalyear-name-35fc02af5233" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentFiscalYear.name`

            Name captures the display name of the fiscal year (e.g., 'FY24'). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each fiscal year detail record.
            * **Interpretation:** The provider supplies `name` at fiscal year detail granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentfiscalyear-startda-37c6281e566c" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentFiscalYear.startDate`

            Start Date captures the start date of the fiscal year in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per fiscal year detail record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentfiscalyear-year-d449da389750" title="Year" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentFiscalYear.year`

            Year identifies the calendar year mapped to the fiscal-year definition. It anchors the provider's fiscal label to a calendar grouping.

            * **Enables:** align fiscal periods with calendar-year reporting and resolve labels such as `FY24`.
            * **Interpretation:** The provider supplies `year` as a calendar-year value, not a quantity or elapsed duration; missing means no calendar mapping was reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentperiod-135c8bf88fba" title="Current Period" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentPeriod`

            Current Period captures the current active time period in the model calendar. It preserves the provider's current classification of this record.

            * **Enables:** separate model calendar records by the exact provider-reported current period value when describing their recorded state.
            * **Interpretation:** The provider supplies `currentPeriod` per model calendar record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentperiod-enddate-35acdd196d20" title="End Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentPeriod.endDate`

            End Date records end date of the current period in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `endDate` per current period record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentperiod-id-8dbb93bb24a9" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentPeriod.id`

            ID is the unique identifier of the current period. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model calendar records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `CurrentPeriod`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentperiod-level-78472f957ee4" title="Level" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentPeriod.level`

            Level captures the time level of the current period (e.g., 'Month', 'Quarter'). It preserves the provider's current classification of this record.

            * **Enables:** separate model calendar records by the exact provider-reported level value when describing their recorded state.
            * **Interpretation:** The provider supplies `level` per current period record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentperiod-name-cc11849742d0" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentPeriod.name`

            Name records display name of the current period (e.g., 'Jan 24', 'Q1 FY24'). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each current period record.
            * **Interpretation:** The provider supplies `name` at current period granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-currentperiod-startdate-9c0e4909bb90" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.currentPeriod.startDate`

            Start Date records start date of the current period in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per current period record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-enabled-861164c5eb50" title="Enabled" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.enabled`

            Enabled indicates whether the calendar/time dimension is enabled for the model. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model calendar records for which the provider reports enabled as true or false.
            * **Interpretation:** The provider supplies `enabled` as a boolean per model calendar record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-fiscalyear-7b45472c8e33" title="Fiscal Year" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.fiscalYear`

            Fiscal Year records fiscal year configuration including start month and year offset settings. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact fiscal year when validating the configuration or technical definition of a model calendar record.
            * **Interpretation:** The provider supplies `fiscalYear` as configuration or technical metadata on `ModelCalendar`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-fiscalyear-fiscalyearname-4b7b7865cd09" title="Fiscal Year Name Based On End Year" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.fiscalYear.fiscalYearNameBasedOnEndYear`

            Fiscal Year Name Based On End Year records if true, the fiscal year is named based on the calendar year in which it ends; if false, based on the year in which it starts. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model calendar records for which the provider reports fiscal year name based on end year as true or false.
            * **Interpretation:** The provider supplies `fiscalYearNameBasedOnEndYear` as a boolean per fiscal year config record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-fiscalyear-startmonth-c130b166e31c" title="Start Month" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.fiscalYear.startMonth`

            Start Month captures the month in which the fiscal year begins. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested start month object into its declared child fields for each fiscal year config record.
            * **Interpretation:** The provider returns `startMonth` as a nested object or reference on `FiscalYearConfig`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-fiscalyear-yearlabel-b0ff1c3a2fea" title="Year Label" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.fiscalYear.yearLabel`

            Year Label captures the label format used for fiscal years (e.g., 'FY' prefix). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact year label value attached to each fiscal year config record.
            * **Interpretation:** The provider supplies `yearLabel` at fiscal year config granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-modelid-3a40fcad5679" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.modelId`

            Model ID identifies parent id injected by the ingestor from the `workspace_models` to `model_calendar` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model calendar source row before constructing its represented state.
            * **Interpretation:** The provider supplies `modelId` at one value per model calendar record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-ce16ce5317e6" title="Periods" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods`

            Periods records list of period definitions configured in the model calendar (e.g., months, quarters, years). It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested periods object into its declared child fields for each model calendar record.
            * **Interpretation:** The provider returns `periods` as a list on `ModelCalendar`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-enddate-e30d66fc83a2" title="End Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.endDate`

            End Date records end date of the period in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `endDate` per period definition record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-id-952b28a2c876" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.id`

            ID is the unique identifier of the period. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same period definition source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per period definition record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-iscurrent-48e6f8850ba8" title="Is Current" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.isCurrent`

            Is Current indicates whether this period is the current active period. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model calendar records for which the provider reports is current as true or false.
            * **Interpretation:** The provider supplies `isCurrent` as a boolean per period definition record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-level-baec2a89c581" title="Level" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.level`

            Level captures the time level this period belongs to (e.g., 'Month', 'Quarter', 'Year'). It preserves the provider's current classification of this record.

            * **Enables:** separate model calendar records by the exact provider-reported level value when describing their recorded state.
            * **Interpretation:** The provider supplies `level` per period definition record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-name-232742ecce92" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.name`

            Name records display name of the period (e.g., 'Jan 23', 'Q2 FY24', 'FY24'). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each period definition record.
            * **Interpretation:** The provider supplies `name` at period definition granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-order-63d17fb7115c" title="Order" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.order`

            Order reports sort order of the period within its level. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify model calendar records using the provider-defined order value.
            * **Interpretation:** The provider supplies `order` at period definition granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-parentid-b4e812461c54" title="Parent ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.parentId`

            Parent ID is the identifier of the parent period in the time hierarchy (e.g., a month's parent quarter). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model calendar records to provider records that carry the same parent ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `parentId` as a record-level identifier on `PeriodDefinition`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-periods-startdate-6c51d23ff3db" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.periods.startDate`

            Start Date records start date of the period in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per period definition record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timedimension-77adb20c2ad0" title="Time Dimension" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeDimension`

            Time Dimension captures the time dimension definition for the model. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared time dimension layout or dimensional scope of each model calendar record.
            * **Interpretation:** The provider returns `timeDimension` as a nested object or reference on `ModelCalendar`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timedimension-id-8b34a5c67173" title="ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeDimension.id`

            ID is the unique identifier of the time dimension. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model calendar records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TimeDimension`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timedimension-name-407f16c1b3b6" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeDimension.name`

            Name records name of the time dimension. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each time dimension record.
            * **Interpretation:** The provider supplies `name` at time dimension granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timelevels-3fdd6f3f47a5" title="Time Levels" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeLevels`

            Time Levels records hierarchy of time levels available in the model (e.g., Day, Week, Month, Quarter, Half Year, Year). It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by time levels on each model calendar record.
            * **Interpretation:** The provider returns `timeLevels` as a list on `ModelCalendar`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timelevels-enabled-dcc6ca6398d7" title="Enabled" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeLevels.enabled`

            Enabled indicates whether this time level is enabled in the model. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model calendar records for which the provider reports enabled as true or false.
            * **Interpretation:** The provider supplies `enabled` as a boolean per time level record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timelevels-id-2b1631a5d6a7" title="ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeLevels.id`

            ID is the unique identifier of the time level. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same time level source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per time level record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timelevels-name-a7fe698949a9" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeLevels.name`

            Name records name of the time level (e.g., 'Month', 'Quarter', 'Year'). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each time level record.
            * **Interpretation:** The provider supplies `name` at time level granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timelevels-order-93e6ba215ce0" title="Order" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeLevels.order`

            Order reports hierarchical order of the time level, with lower values being more granular. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify model calendar records using the provider-defined order value.
            * **Interpretation:** The provider supplies `order` at time level granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timelevels-periodsperyear-49bdacf0a3dd" title="Periods Per Year" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeLevels.periodsPerYear`

            Periods Per Year reports the number of periods of this level per year (e.g., 12 for months, 4 for quarters). It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported periods per year for each time level record.
            * **Interpretation:** The provider supplies `periodsPerYear` at time level granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-e2ad23f1bec5" title="Time Range" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange`

            Time Range captures the overall time range configured for the model. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested time range object into its declared child fields for each model calendar record.
            * **Interpretation:** The provider returns `timeRange` as a nested object or reference on `ModelCalendar`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-enddate-a8802fa7f23f" title="End Date" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.endDate`

            End Date captures the end date of the model's time range in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `endDate` per time range record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-endperiod-1d6c4d3039e0" title="End Period" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.endPeriod`

            End Period captures the name or identifier of the last period in the time range. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model calendar records to provider records that carry the same end period, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `endPeriod` as a record-level identifier on `TimeRange`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-futureyears-72c86b9b0cd2" title="Future Years" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.futureYears`

            Future Years reports the number of future years included in the time range relative to the current year. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported future years for each time range record.
            * **Interpretation:** The provider supplies `futureYears` at time range granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-numberofyears-7b74ebd3b58f" title="Number Of Years" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.numberOfYears`

            Number Of Years reports the total number of years spanned by the time range. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported number of years for each time range record.
            * **Interpretation:** The provider supplies `numberOfYears` at time range granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-pastyears-f1290c2c2b2a" title="Past Years" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.pastYears`

            Past Years reports the number of past years included in the time range relative to the current year. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported past years for each time range record.
            * **Interpretation:** The provider supplies `pastYears` at time range granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-startdate-a0ce09697cfe" title="Start Date" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.startDate`

            Start Date captures the start date of the model's time range in ISO 8601 format. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model calendar records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per time range record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-timerange-startperiod-e751611cab20" title="Start Period" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.timeRange.startPeriod`

            Start Period captures the name or identifier of the first period in the time range. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model calendar records to provider records that carry the same start period, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `startPeriod` as a record-level identifier on `TimeRange`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-workspaceid-5062638d728d" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `workspace_models` to `model_calendar` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model calendar records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelCalendar`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-yearrange-a67ced796ad9" title="Year Range" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.yearRange`

            Year Range captures the range of years covered by the model calendar. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested year range object into its declared child fields for each model calendar record.
            * **Interpretation:** The provider returns `yearRange` as a nested object or reference on `ModelCalendar`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-yearrange-endyear-0ef24161753e" title="End Year" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.yearRange.endYear`

            End Year identifies the last calendar year included in the model's time range. It marks the closing boundary of the configured planning horizon.

            * **Enables:** determine whether forecast periods required for analysis fall within the model calendar.
            * **Interpretation:** The provider supplies `endYear` as a calendar-year boundary, not a count or duration; missing means the upper boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-calendar-yearrange-startyear-963707942811" title="Start Year" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_calendar.yearRange.startYear`

            Start Year identifies the first calendar year included in the model's time range. It marks the opening boundary of the configured planning horizon.

            * **Enables:** determine whether historical periods required for analysis fall within the model calendar.
            * **Interpretation:** The provider supplies `startYear` as a calendar-year boundary, not a count or duration; missing means the lower boundary was not reported.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-exports-3c6c3d438c84" title="Model Exports" icon="list-check" iconType="sharp-duotone-solid">
        Developer identifier: `model_exports`

        Model Exports contain all export action definitions within a specific model. Export actions define data extractions from Anaplan modules/views.

        * **Enables:** review the export actions configured to extract data from a model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/exports` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-exports-columncount-5bed19cc9f60" title="Column Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columnCount`

            Column Count reports the number of columns in the export output, if available. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported column count for each model export record.
            * **Interpretation:** The provider supplies `columnCount` at model export granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-31838ece4654" title="Columns" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns`

            Columns records definitions of the columns included in the export output. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared columns layout or dimensional scope of each model export record.
            * **Interpretation:** The provider returns `columns` as a list on `ModelExport`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-columnindex-b07425dd463f" title="Column Index" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.columnIndex`

            Column Index reports zero-based index position of the column in the export output. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify model export records using the provider-defined column index value.
            * **Interpretation:** The provider supplies `columnIndex` at export column granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-customheadername-6380f8134047" title="Custom Header Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.customHeaderName`

            Custom Header Name records custom header name assigned to this column, if any. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret custom header name according to the provider and Workspace configuration that produced each model export record.
            * **Interpretation:** Keys and value shapes within `customHeaderName` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-datatype-c6e75f89471c" title="Data Type" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.dataType`

            Data Type states data type of the column values, e.g., TEXT, NUMBER, BOOLEAN, DATE, LIST. It preserves the provider's current classification of this record.

            * **Enables:** separate model export records by the exact provider-reported data type value when describing their recorded state.
            * **Interpretation:** The provider supplies `dataType` per export column record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-dimensionid-009a36aa96f3" title="Dimension ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.dimensionId`

            Dimension ID is the identifier of the dimension this column represents, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same dimension ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `dimensionId` as a record-level identifier on `ExportColumn`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-dimensionname-8a6ecb280dac" title="Dimension Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.dimensionName`

            Dimension Name records name of the dimension this column represents. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact dimension name value attached to each export column record.
            * **Interpretation:** The provider supplies `dimensionName` at export column granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-lineitemid-4104e24a0bf0" title="Line Item ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.lineItemId`

            Line Item ID is the identifier of the line item this column represents, if applicable. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same export column source row before constructing its represented state.
            * **Interpretation:** The provider supplies `lineItemId` at one value per export column record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-columns-lineitemname-618a37a7001d" title="Line Item Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.columns.lineItemName`

            Line Item Name records name of the line item this column represents, if applicable. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact line item name value attached to each export column record.
            * **Interpretation:** The provider supplies `lineItemName` at export column granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-createdat-a420891440bf" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.createdAt`

            Created At records ISO 8601 timestamp when the export action was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model export records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdAt` per model export record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-createdby-c3a805f77125" title="Created By" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.createdBy`

            Created By records identifier or name of the user who created the export action. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the model export record to the provider-reported person or account represented by created by.
            * **Interpretation:** The provider supplies `createdBy` as identity or attribution context on each model export record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-datarow-597c5a207a13" title="Data Row" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.dataRow`

            Data Row identifies the row position where exported data begins. It separates header material from the records intended for parsing.

            * **Enables:** start export ingestion at the provider-declared data boundary without treating preceding rows as data.
            * **Interpretation:** The provider supplies `dataRow` as a row position, not a count or business measure; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-delimiter-f74630288b8d" title="Delimiter" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.delimiter`

            Delimiter records text qualifier/delimiter used to wrap field values, e.g., '"'. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact delimiter when validating the configuration or technical definition of a model export record.
            * **Interpretation:** The provider supplies `delimiter` as configuration or technical metadata on `ModelExport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-encoding-0e404244cd07" title="Encoding" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.encoding`

            Encoding records character encoding used for the export output, e.g., 'UTF-8'. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact encoding when validating the configuration or technical definition of a model export record.
            * **Interpretation:** The provider supplies `encoding` as configuration or technical metadata on `ModelExport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-exportformat-03816c0113c6" title="Export Format" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.exportFormat`

            Export Format captures the output format of the exported data. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact export format when validating the configuration or technical definition of a model export record.
            * **Interpretation:** The provider supplies `exportFormat` as configuration or technical metadata on `ModelExport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-exporttype-0c8f1f73c22e" title="Export Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.exportType`

            Export Type captures the type of export, indicating what kind of data source is being exported. It preserves the provider's current classification of this record.

            * **Enables:** separate model export records by the exact provider-reported export type value when describing their recorded state.
            * **Interpretation:** The provider supplies `exportType` per model export record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-headerrow-c2bbb0b012aa" title="Header Row" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.headerRow`

            Header Row records row number that contains column headers in the export output. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact header row when validating the configuration or technical definition of a model export record.
            * **Interpretation:** The provider supplies `headerRow` as configuration or technical metadata on `ModelExport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-id-9f61f5eceefe" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.id`

            ID is the unique identifier for the export action definition. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model export source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per model export record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-lastmodifiedat-74b4cde32921" title="Last Modified At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.lastModifiedAt`

            Last Modified At records ISO 8601 timestamp when the export action was last modified. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model export records on a timeline by last modified at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastModifiedAt` per model export record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-lastmodifiedby-5383522d01c8" title="Last Modified By" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.lastModifiedBy`

            Last Modified By records identifier or name of the user who last modified the export action. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the model export record to the provider-reported person or account represented by last modified by.
            * **Interpretation:** The provider supplies `lastModifiedBy` as identity or attribution context on each model export record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-layout-2eb3561c20dc" title="Layout" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.layout`

            Layout captures the layout type of the export, such as grid or tabular. It preserves the provider's current classification of this record.

            * **Enables:** separate model export records by the exact provider-reported layout value when describing their recorded state.
            * **Interpretation:** The provider supplies `layout` per model export record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-lineitems-fa83d2d59b2f" title="Line Items" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.lineItems`

            Line Items records line item identifiers included in the export, if applicable. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared line items layout or dimensional scope of each model export record.
            * **Interpretation:** The provider returns `lineItems` as a list on `ModelExport`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-listid-031743948bec" title="List ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.listId`

            List ID is the identifier of the list being exported, if the export type is a list export. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same list ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `listId` as a record-level identifier on `ModelExport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-listname-106fee7fd44d" title="List Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.listName`

            List Name states name of the list being exported, if the export type is a list export. It preserves the provider's current classification of this record.

            * **Enables:** separate model export records by the exact provider-reported list name value when describing their recorded state.
            * **Interpretation:** The provider supplies `listName` per model export record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-modelid-0a0646127988" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.modelId`

            Model ID identifies parent id injected by the ingestor from the `workspace_models` to `model_exports` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModelExport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-moduleid-aab88babaf62" title="Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.moduleId`

            Module ID is the identifier of the source module from which data is exported. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `moduleId` as a record-level identifier on `ModelExport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-modulename-985defe19f94" title="Module Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.moduleName`

            Module Name records name of the source module from which data is exported. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact module name value attached to each model export record.
            * **Interpretation:** The provider supplies `moduleName` at model export granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-name-0d940ba76e97" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.name`

            Name records display name of the export action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each model export record.
            * **Interpretation:** The provider supplies `name` at model export granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-pages-e6e3ed688a6f" title="Pages" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.pages`

            Pages records page dimension filters applied to the export, if any. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared pages layout or dimensional scope of each model export record.
            * **Interpretation:** The provider returns `pages` as a list on `ModelExport`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-pages-dimensionid-ab58b7351cac" title="Dimension ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.pages.dimensionId`

            Dimension ID is the identifier of the dimension used as a page filter. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same dimension ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `dimensionId` as a record-level identifier on `ExportPage`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-pages-dimensionname-4e5c26cf1703" title="Dimension Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.pages.dimensionName`

            Dimension Name records name of the dimension used as a page filter. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact dimension name value attached to each export page record.
            * **Interpretation:** The provider supplies `dimensionName` at export page granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-pages-itemid-cd9ea8aecf81" title="Item ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.pages.itemId`

            Item ID is the identifier of the selected item within the page dimension. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same export page source row before constructing its represented state.
            * **Interpretation:** The provider supplies `itemId` at one value per export page record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-pages-itemname-66d37ae0f24f" title="Item Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.pages.itemName`

            Item Name records name of the selected item within the page dimension. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact item name value attached to each export page record.
            * **Interpretation:** The provider supplies `itemName` at export page granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-rowcount-49c7bbb55165" title="Row Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.rowCount`

            Row Count reports the number of rows in the export output, if available. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported row count for each model export record.
            * **Interpretation:** The provider supplies `rowCount` at model export granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-separator-8b75d11cf0c5" title="Separator" icon="table" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.separator`

            Separator records column separator/delimiter used in the export output, e.g., ',' or '\t'. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact separator when validating the configuration or technical definition of a model export record.
            * **Interpretation:** The provider supplies `separator` as configuration or technical metadata on `ModelExport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-viewid-67cc0148f521" title="View ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.viewId`

            View ID is the identifier of the saved view used for the export, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same view ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `viewId` as a record-level identifier on `ModelExport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-viewname-25919a7de123" title="View Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.viewName`

            View Name records name of the saved view used for the export, if applicable. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact view name value attached to each model export record.
            * **Interpretation:** The provider supplies `viewName` at model export granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-exports-workspaceid-c911a98af632" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_exports.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `workspace_models` to `model_exports` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model export records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelExport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-files-199e74a1a0a7" title="Model Files" icon="folder-open" iconType="sharp-duotone-solid">
        Developer identifier: `model_files`

        Model Files contain all files (data sources and export outputs) within a specific model.

        * **Enables:** trace model data-source and export-output files to their parent model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/files` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-files-chunkcount-3a96b00aa6ca" title="Chunk Count" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.chunkCount`

            Chunk Count captures the number of chunks the file is divided into for upload/download. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported chunk count for each model file record.
            * **Interpretation:** The provider supplies `chunkCount` at model file granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-code-39228f050714" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.code`

            Code contains an optional code or identifier associated with the file. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact code when validating the configuration or technical definition of a model file record.
            * **Interpretation:** The provider supplies `code` as configuration or technical metadata on `ModelFile`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-delimiter-8195b2698076" title="Delimiter" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.delimiter`

            Delimiter captures the column delimiter used in the file (e.g., comma, tab). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact delimiter when validating the configuration or technical definition of a model file record.
            * **Interpretation:** The provider supplies `delimiter` as configuration or technical metadata on `ModelFile`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-description-491417583fa1" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.description`

            Description contains a human-readable description of the file. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each model file record.
            * **Interpretation:** The provider supplies `description` at model file granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-encoding-73be4ade07ae" title="Encoding" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.encoding`

            Encoding captures the character encoding of the file (e.g., UTF-8). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact encoding when validating the configuration or technical definition of a model file record.
            * **Interpretation:** The provider supplies `encoding` as configuration or technical metadata on `ModelFile`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-firstdatarow-1065615f80cc" title="First Data Row" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.firstDataRow`

            First Data Row identifies the zero-based row where file data begins after any headers. It preserves the parsing boundary recorded for the model file.

            * **Enables:** skip header rows and begin processing at the same row position Anaplan uses.
            * **Interpretation:** The provider supplies `firstDataRow` as a zero-based row index, not a row count; zero means the first row and missing means no boundary was reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-format-d94fbb4223f4" title="Format" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.format`

            Format captures the format of the file content (e.g., txt, csv). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact format when validating the configuration or technical definition of a model file record.
            * **Interpretation:** The provider supplies `format` as configuration or technical metadata on `ModelFile`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-headerrow-1eca36c96d3a" title="Header Row" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.headerRow`

            Header Row captures the row number that contains column headers (0-indexed). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact header row when validating the configuration or technical definition of a model file record.
            * **Interpretation:** The provider supplies `headerRow` as configuration or technical metadata on `ModelFile`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-id-151b7dc52266" title="ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.id`

            ID captures the unique identifier of the file within the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model file source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per model file record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-modelid-34ff15a93abd" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.modelId`

            Model ID identifies parent model id injected by the ingestor when iterating per-model. Not part of the upstream Anaplan API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model file records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModelFile`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-name-ca18abdcfe2b" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.name`

            Name captures the display name of the file. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each model file record.
            * **Interpretation:** The provider supplies `name` at model file granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-origin-0d1d50e831da" title="Origin" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.origin`

            Origin carries the provider-reported origin for each model file record. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested origin object into its declared child fields for each model file record.
            * **Interpretation:** The provider returns `origin` as a nested object or reference on `ModelFile`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-origin-actionname-18854ee9d125" title="Action Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.origin.actionName`

            Action Name captures the name of the action (import or export) that produced or consumes this file. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact action name value attached to each file origin record.
            * **Interpretation:** The provider supplies `actionName` at file origin granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-origin-exportid-cc40e1dcc44b" title="Export ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.origin.exportId`

            Export ID captures the identifier of the export action associated with this file, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model file records to provider records that carry the same export ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `exportId` as a record-level identifier on `FileOrigin`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-origin-importid-2e035d3dd5c9" title="Import ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.origin.importId`

            Import ID captures the identifier of the import action associated with this file, if applicable. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model file records to provider records that carry the same import ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `importId` as a record-level identifier on `FileOrigin`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-origin-type-8a256ee3b892" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.origin.type`

            Type carries the source state or classification named Type for each file origin row. It preserves the provider's current classification of this record.

            * **Enables:** separate model file records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per file origin record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-separator-3af0890f26de" title="Separator" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.separator`

            Separator captures the separator character used in the file, such as a line separator or record delimiter. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact separator when validating the configuration or technical definition of a model file record.
            * **Interpretation:** The provider supplies `separator` as configuration or technical metadata on `ModelFile`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-files-workspaceid-f7b264967cf9" title="Workspace ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_files.workspaceId`

            Workspace ID identifies parent workspace id injected by the ingestor when iterating per-workspace. Not part of the upstream Anaplan API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model file records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelFile`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-imports-ef9a04e43e65" title="Model Imports" icon="list-check" iconType="sharp-duotone-solid">
        Developer identifier: `model_imports`

        Model Imports contain all import action definitions within a specific model. Import actions define data loading configurations into Anaplan.

        * **Enables:** review the import actions configured to load data into a model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/imports` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-imports-code-8814fca46742" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.code`

            Code records optional user-defined code for the import action. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret code according to the provider and Workspace configuration that produced each model import record.
            * **Interpretation:** Keys and value shapes within `code` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-4d855867f20d" title="Column Mappings" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings`

            Column Mappings lists the relationships from source columns to target dimensions or line items. It preserves the import mapping needed to explain where each input value lands.

            * **Enables:** reconstruct and audit source-to-target assignments for each model import.
            * **Interpretation:** The provider supplies `columnMappings` as a list of mapping objects; an empty list and a missing mapping declaration are distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-columnindex-52c7d7998bda" title="Column Index" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.columnIndex`

            Column Index reports zero-based index of the source column. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify model import records using the provider-defined column index value.
            * **Interpretation:** The provider supplies `columnIndex` at column mapping granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-columnname-d9d757f6a470" title="Column Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.columnName`

            Column Name identifies name of the source column being mapped. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same column mapping source row before constructing its represented state.
            * **Interpretation:** The provider supplies `columnName` at one value per column mapping record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-dateformat-5cfae4b2681d" title="Date Format" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.dateFormat`

            Date Format records the date format pattern applied when the column contains date values. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact date format when validating the configuration or technical definition of a column mapping record.
            * **Interpretation:** The provider supplies `dateFormat` as configuration or technical metadata on `ColumnMapping`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-ignored-629a8ef405cd" title="Ignored" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.ignored`

            Ignored indicates whether this source column is ignored and not mapped to any target. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model import records for which the provider reports ignored as true or false.
            * **Interpretation:** The provider supplies `ignored` as a boolean per column mapping record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-mappingtype-618070894bc6" title="Mapping Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.mappingType`

            Mapping Type captures the type of mapping applied to this column. It preserves the provider's current classification of this record.

            * **Enables:** separate model import records by the exact provider-reported mapping type value when describing their recorded state.
            * **Interpretation:** The provider supplies `mappingType` per column mapping record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-targetdimen-2dca1f27b80d" title="Target Dimension ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.targetDimensionId`

            Target Dimension ID is the identifier of the target dimension this column maps to. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same target dimension ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetDimensionId` as a record-level identifier on `ColumnMapping`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-targetdimen-d8c9d15c61ab" title="Target Dimension Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.targetDimensionName`

            Target Dimension Name records name of the target dimension this column maps to. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact target dimension name value attached to each column mapping record.
            * **Interpretation:** The provider supplies `targetDimensionName` at column mapping granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-targetlinei-9db9d5ef42f4" title="Target Line Item ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.targetLineItemId`

            Target Line Item ID is the identifier of the target line item this column maps to. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same target line item ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetLineItemId` as a record-level identifier on `ColumnMapping`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-targetlinei-be5f2e7e5475" title="Target Line Item Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.targetLineItemName`

            Target Line Item Name records name of the target line item this column maps to. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact target line item name value attached to each column mapping record.
            * **Interpretation:** The provider supplies `targetLineItemName` at column mapping granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-columnmappings-targetprope-4ce2c5395ae5" title="Target Property Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.columnMappings.targetPropertyName`

            Target Property Name records name of the target property (for list imports) this column maps to. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact target property name value attached to each column mapping record.
            * **Interpretation:** The provider supplies `targetPropertyName` at column mapping granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-delimiter-dff5d1ec70d4" title="Delimiter" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.delimiter`

            Delimiter captures the delimiter character used in the source file (e.g., comma, tab). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact delimiter when validating the configuration or technical definition of a model import record.
            * **Interpretation:** The provider supplies `delimiter` as configuration or technical metadata on `ModelImport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-encoding-9aaf62d13bd8" title="Encoding" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.encoding`

            Encoding records character encoding of the source file (e.g., UTF-8). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact encoding when validating the configuration or technical definition of a model import record.
            * **Interpretation:** The provider supplies `encoding` as configuration or technical metadata on `ModelImport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-firstdatarow-a08eeaca3dfc" title="First Data Row" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.firstDataRow`

            First Data Row identifies the source-file row where import data begins. It separates headers and preamble rows from the imported records.

            * **Enables:** reproduce the import boundary and diagnose row-alignment errors in source files.
            * **Interpretation:** The provider supplies `firstDataRow` as a row position, not a row count or business measure; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-headerrow-a6d197dd175d" title="Header Row" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.headerRow`

            Header Row captures the row number in the source file that contains column headers. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact header row when validating the configuration or technical definition of a model import record.
            * **Interpretation:** The provider supplies `headerRow` as configuration or technical metadata on `ModelImport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-id-a1d58d627fa5" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.id`

            ID is the unique identifier of the import action. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model import source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per model import record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-importdatasourceid-b6dabf3d02f5" title="Import Data Source ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.importDataSourceId`

            Import Data Source ID is the identifier of the data source (file or list) used by this import action. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same import data source ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `importDataSourceId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-importdatasourcename-45614356f61b" title="Import Data Source Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.importDataSourceName`

            Import Data Source Name records name of the data source used by this import action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact import data source name value attached to each model import record.
            * **Interpretation:** The provider supplies `importDataSourceName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-importdatasourcetype-3b221b08e437" title="Import Data Source Type" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.importDataSourceType`

            Import Data Source Type captures the type of data source feeding this import (e.g., file, list, module). It preserves the provider's current classification of this record.

            * **Enables:** separate model import records by the exact provider-reported import data source type value when describing their recorded state.
            * **Interpretation:** The provider supplies `importDataSourceType` per model import record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-importtype-4ee69865fec7" title="Import Type" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.importType`

            Import Type captures the type of import, indicating the target structure (e.g., module data, list items, or users). It preserves the provider's current classification of this record.

            * **Enables:** separate model import records by the exact provider-reported import type value when describing their recorded state.
            * **Interpretation:** The provider supplies `importType` per model import record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-modelid-e504dcde97eb" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.modelId`

            Model ID identifies parent model id injected by the ingestor when iterating per-model. Not part of the upstream Anaplan API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-name-e5d871de9228" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.name`

            Name records display name of the import action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each model import record.
            * **Interpretation:** The provider supplies `name` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-separator-fc923a3d31c3" title="Separator" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.separator`

            Separator captures the text qualifier or separator used in the source file. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact separator when validating the configuration or technical definition of a model import record.
            * **Interpretation:** The provider supplies `separator` as configuration or technical metadata on `ModelImport`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcefileid-dc5b9fbc201b" title="Source File ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceFileId`

            Source File ID is the identifier of the source file used by this import action. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same source file ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sourceFileId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcefilename-384ae0a0d01a" title="Source File Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceFileName`

            Source File Name records name of the source file used by this import action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact source file name value attached to each model import record.
            * **Interpretation:** The provider supplies `sourceFileName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcelistid-2d2be974cbff" title="Source List ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceListId`

            Source List ID is the identifier of the source list when importing from a list. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same source list ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sourceListId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcelistname-c9419214c2f4" title="Source List Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceListName`

            Source List Name records name of the source list when importing from a list. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact source list name value attached to each model import record.
            * **Interpretation:** The provider supplies `sourceListName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcemodelid-5588e0088a92" title="Source Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceModelId`

            Source Model ID is the identifier of the source model if the import pulls data from another Anaplan model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same source model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sourceModelId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcemodelname-4ce691232e56" title="Source Model Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceModelName`

            Source Model Name records name of the source model if the import pulls data from another Anaplan model. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact source model name value attached to each model import record.
            * **Interpretation:** The provider supplies `sourceModelName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcemoduleid-89b7628e93c9" title="Source Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceModuleId`

            Source Module ID is the identifier of the source module when importing from a module view. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same source module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sourceModuleId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourcemodulename-be14960ae449" title="Source Module Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceModuleName`

            Source Module Name records name of the source module when importing from a module view. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact source module name value attached to each model import record.
            * **Interpretation:** The provider supplies `sourceModuleName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourceviewid-819e2b38d23b" title="Source View ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceViewId`

            Source View ID is the identifier of the source view when importing from a module view. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same source view ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `sourceViewId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-sourceviewname-bbcbfc2ab37d" title="Source View Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.sourceViewName`

            Source View Name records name of the source view when importing from a module view. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact source view name value attached to each model import record.
            * **Interpretation:** The provider supplies `sourceViewName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-targetlistid-1d6d75858689" title="Target List ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.targetListId`

            Target List ID is the identifier of the target list when the import loads list items. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same target list ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetListId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-targetlistname-068cdc555c62" title="Target List Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.targetListName`

            Target List Name records name of the target list when the import loads list items. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact target list name value attached to each model import record.
            * **Interpretation:** The provider supplies `targetListName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-targetmoduleid-34c16f84531e" title="Target Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.targetModuleId`

            Target Module ID is the identifier of the target module when the import loads module data. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same target module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `targetModuleId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-targetmodulename-a23d28e9cf8e" title="Target Module Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.targetModuleName`

            Target Module Name records name of the target module when the import loads module data. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact target module name value attached to each model import record.
            * **Interpretation:** The provider supplies `targetModuleName` at model import granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-imports-workspaceid-e5f221908e62" title="Workspace ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_imports.workspaceId`

            Workspace ID identifies parent workspace id injected by the ingestor when iterating per-workspace. Not part of the upstream Anaplan API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model import records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelImport`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-line-items-2a7f6a129cff" title="Model Line Items" icon="chart-line" iconType="sharp-duotone-solid">
        Developer identifier: `model_line_items`

        Model Line Items contain all line items defined within a specific model. Line items are the individual data elements (metrics/measures) in Anaplan modules.

        * **Enables:** inventory the measures defined by line items within each planning model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/lineItems` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-line-items-appliesto-d2678a94f899" title="Applies To" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.appliesTo`

            Applies To lists the dimensions and entities related to the line item. It preserves the relationships that determine where the line item's values exist.

            * **Enables:** reconstruct line-item dimensionality and join each line item to its applicable lists or entities.
            * **Interpretation:** The provider supplies `appliesTo` as a list of dimension references; an empty list and a missing relationship list are distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-appliesto-id-0bd79a215bfb" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.appliesTo.id`

            ID is the unique identifier of the dimension. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same dimension reference source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per dimension reference record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-appliesto-name-696703a680d5" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.appliesTo.name`

            Name records name of the dimension. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each dimension reference record.
            * **Interpretation:** The provider supplies `name` at dimension reference granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-breakback-18662cb173e7" title="Breakback" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.breakback`

            Breakback indicates whether breakback (spread) is enabled for this line item. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model line item records for which the provider reports breakback as true or false.
            * **Interpretation:** The provider supplies `breakback` as a boolean per model line item record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-broughtforward-ab2e1a77b12e" title="Brought Forward" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.broughtForward`

            Brought Forward indicates whether the line item uses brought-forward (opening balance) time functionality. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model line item records for which the provider reports brought forward as true or false.
            * **Interpretation:** The provider supplies `broughtForward` as a boolean per model line item record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-cellcount-d2a275173350" title="Cell Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.cellCount`

            Cell Count captures the total number of cells occupied by this line item across all dimensions. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported cell count for each model line item record.
            * **Interpretation:** The provider supplies `cellCount` at model line item granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-code-81d9bad030ea" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.code`

            Code records optional code assigned to the line item for external reference or integration purposes. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact code when validating the configuration or technical definition of a model line item record.
            * **Interpretation:** The provider supplies `code` as configuration or technical metadata on `ModelLineItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-datatags-e52055ec5c18" title="Data Tags" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.dataTags`

            Data Tags records data tags associated with this line item for classification or governance. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** apply the provider-defined data tags classifications to each model line item record.
            * **Interpretation:** The provider returns `dataTags` as a list on `ModelLineItem`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-format-2deb563919cc" title="Format" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.format`

            Format captures the data format/type of the line item (e.g., NUMBER, TEXT, BOOLEAN, DATE, `TIME_ENTITY`, LIST). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact format when validating the configuration or technical definition of a model line item record.
            * **Interpretation:** The provider supplies `format` as configuration or technical metadata on `ModelLineItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-da3c853b5880" title="Format Metadata" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata`

            Format Metadata records additional metadata about the line item's format, such as associated list or entity details. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact format metadata when validating the configuration or technical definition of a model line item record.
            * **Interpretation:** The provider supplies `formatMetadata` as configuration or technical metadata on `ModelLineItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-dateform-e24a8eafa667" title="Date Format" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.dateFormat`

            Date Format records the date format pattern for DATE-format line items. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact date format when validating the configuration or technical definition of a format metadata record.
            * **Interpretation:** The provider supplies `dateFormat` as configuration or technical metadata on `FormatMetadata`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-decimalp-5501080071de" title="Decimal Places" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.decimalPlaces`

            Decimal Places defines how many digits appear after the decimal point for a NUMBER-format line item. It preserves the provider's numeric display precision.

            * **Enables:** reproduce line-item formatting and interpret stored values with the intended decimal precision.
            * **Interpretation:** The provider supplies `decimalPlaces` as a formatting count, not an observed business value; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-decimals-bb651b6b5308" title="Decimal Separator" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.decimalSeparator`

            Decimal Separator records decimal separator character. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact decimal separator when validating the configuration or technical definition of a format metadata record.
            * **Interpretation:** The provider supplies `decimalSeparator` as configuration or technical metadata on `FormatMetadata`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-grouping-e1fd34df5641" title="Grouping Separator" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.groupingSeparator`

            Grouping Separator records thousands grouping separator character. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact grouping separator when validating the configuration or technical definition of a format metadata record.
            * **Interpretation:** The provider supplies `groupingSeparator` as configuration or technical metadata on `FormatMetadata`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-listid-4d09f6dc2755" title="List ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.listId`

            List ID is the identifier of the associated list, if the line item format is LIST. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model line item records to provider records that carry the same list ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `listId` as a record-level identifier on `FormatMetadata`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-listname-1d5065db22dd" title="List Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.listName`

            List Name records name of the associated list, if the line item format is LIST. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact list name value attached to each format metadata record.
            * **Interpretation:** The provider supplies `listName` at format metadata granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-minimums-05866cc42d8c" title="Minimum Significant Digits" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.minimumSignificantDigits`

            Minimum Significant Digits defines the minimum displayed precision for NUMBER-format line items. It preserves the formatting rule used with decimal places.

            * **Enables:** reproduce numeric presentation and distinguish formatting precision from the line item's value.
            * **Interpretation:** The provider supplies `minimumSignificantDigits` as a digit-count setting, not an observed business measure; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-negative-77d6e8d49277" title="Negative Number Notation" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.negativeNumberNotation`

            Negative Number Notation records notation style for negative numbers (e.g., minus sign, parentheses). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact negative number notation when validating the configuration or technical definition of a format metadata record.
            * **Interpretation:** The provider supplies `negativeNumberNotation` as configuration or technical metadata on `FormatMetadata`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formatmetadata-zeroform-e088d13d2176" title="Zero Format" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formatMetadata.zeroFormat`

            Zero Format records how zero values are displayed. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact zero format when validating the configuration or technical definition of a format metadata record.
            * **Interpretation:** The provider supplies `zeroFormat` as configuration or technical metadata on `FormatMetadata`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formula-6db752c4d279" title="Formula" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formula`

            Formula captures the formula expression defined for this line item, if any. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact formula when validating the configuration or technical definition of a model line item record.
            * **Interpretation:** The provider supplies `formula` as configuration or technical metadata on `ModelLineItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-formulascope-25bce19e93bd" title="Formula Scope" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.formulaScope`

            Formula Scope captures the scope of the formula, indicating where the formula applies. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact formula scope when validating the configuration or technical definition of a model line item record.
            * **Interpretation:** The provider supplies `formulaScope` as configuration or technical metadata on `ModelLineItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-id-7cc115217de6" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.id`

            ID is the unique identifier of the line item within the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model line item source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per model line item record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-issummary-4199762d0eed" title="Is Summary" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.isSummary`

            Is Summary indicates whether this line item is a summary line item. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model line item records for which the provider reports is summary as true or false.
            * **Interpretation:** The provider supplies `isSummary` as a boolean per model line item record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-modelid-9bf8090e3c23" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.modelId`

            Model ID identifies parent id injected by the ingestor from the `workspace_models` to `model_line_items` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model line item records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModelLineItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-moduleid-432fdba8a0ba" title="Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.moduleId`

            Module ID is the identifier of the module that contains this line item. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model line item records to provider records that carry the same module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `moduleId` as a record-level identifier on `ModelLineItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-modulename-c861aa81ccdd" title="Module Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.moduleName`

            Module Name records name of the module that contains this line item. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact module name value attached to each model line item record.
            * **Interpretation:** The provider supplies `moduleName` at model line item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-name-87d002012583" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.name`

            Name records display name of the line item. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each model line item record.
            * **Interpretation:** The provider supplies `name` at model line item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-notes-d06c5003d8a9" title="Notes" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.notes`

            Notes records user-defined notes or description for the line item. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret notes according to the provider and Workspace configuration that produced each model line item record.
            * **Interpretation:** Keys and value shapes within `notes` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-parent-d1281d46383b" title="Parent" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.parent`

            Parent records parent line item reference when nested. Live API returns `{id, name}`; absent or null when the line item has no parent. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact parent value attached to each model line item record.
            * **Interpretation:** The provider supplies `parent` at model line item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-parent-id-72ed10e0672e" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.parent.id`

            ID is the identifier of the parent line item. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same line item parent source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per line item parent record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-parent-name-b9008d31e42d" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.parent.name`

            Name records display name of the parent line item. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each line item parent record.
            * **Interpretation:** The provider supplies `name` at line item parent granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-parentname-32b46d7a5bc7" title="Parent Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.parentName`

            Parent Name records name of the parent line item, if this line item is nested. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact parent name value attached to each model line item record.
            * **Interpretation:** The provider supplies `parentName` at model line item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-readaccessdriver-377a93ea1e64" title="Read Access Driver" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.readAccessDriver`

            Read Access Driver captures the access driver controlling read permissions for this line item. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported read access driver attached to each model line item record.
            * **Interpretation:** The provider supplies `readAccessDriver` at model line item granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-referencedby-6dcb4298f907" title="Referenced By" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.referencedBy`

            Referenced By records list of line items or formulas that reference this line item. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared referenced by layout or dimensional scope of each model line item record.
            * **Interpretation:** The provider returns `referencedBy` as a list on `ModelLineItem`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-startofsection-d4fc027a6f37" title="Start Of Section" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.startOfSection`

            Start Of Section indicates whether this line item marks the start of a section in the module. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model line item records for which the provider reports start of section as true or false.
            * **Interpretation:** The provider supplies `startOfSection` as a boolean per model line item record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-style-0cf7ea45a973" title="Style" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.style`

            Style records display style or formatting hint for the line item. It preserves the provider's visual treatment for the represented object.

            * **Enables:** reproduce or compare the provider-supplied style for the represented design or board object.
            * **Interpretation:** The provider supplies `style` in its own color, opacity, stroke, emoji, or style vocabulary for the represented object.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-summary-538c60135129" title="Summary" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.summary`

            Summary captures the summary (aggregation) method applied to the line item. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact summary value attached to each model line item record.
            * **Interpretation:** The provider supplies `summary` at model line item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-timerange-43a2659bbc4a" title="Time Range" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.timeRange`

            Time Range records time range label for the line item as returned by the API (for example Model Calendar, 2016 - 2026). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact time range value attached to each model line item record.
            * **Interpretation:** The provider supplies `timeRange` at model line item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-timescale-299b73d66ffa" title="Time Scale" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.timeScale`

            Time Scale captures the time scale granularity for the line item (e.g., Month, Quarter, Year). It preserves the provider-defined period or schedule cadence for this record.

            * **Enables:** group model line item records by the provider-defined time scale period or schedule.
            * **Interpretation:** The provider supplies `timeScale` per model line item record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-useswitchover-bdd3a2867cfd" title="Use Switchover" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.useSwitchover`

            Use Switchover indicates whether the line item uses switchover for actual vs. forecast data. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model line item records for which the provider reports use switchover as true or false.
            * **Interpretation:** The provider supplies `useSwitchover` as a boolean per model line item record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-version-2ddd09cad524" title="Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.version`

            Version records version settings for the line item, if applicable. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact version when validating the configuration or technical definition of a model line item record.
            * **Interpretation:** The provider supplies `version` as configuration or technical metadata on `ModelLineItem`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-version-id-9e7c28900a9b" title="ID" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.version.id`

            ID is the identifier of the version. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model line item records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `VersionReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-version-name-93d920d14f66" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.version.name`

            Name records name of the version. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each version reference record.
            * **Interpretation:** The provider supplies `name` at version reference granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-workspaceid-a8d500e82c06" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `workspace_models` to `model_line_items` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model line item records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelLineItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-line-items-writeaccessdriver-92d18995e1f9" title="Write Access Driver" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_line_items.writeAccessDriver`

            Write Access Driver captures the access driver controlling write permissions for this line item. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported write access driver attached to each model line item record.
            * **Interpretation:** The provider supplies `writeAccessDriver` at model line item granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-lists-62d1c6ac97c3" title="Model Lists" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `model_lists`

        Model Lists contain all lists (dimensions/hierarchies) defined within a specific model. Lists are core structural elements in Anaplan.

        * **Enables:** map the lists that define dimensions and hierarchies in each planning model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/lists` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-lists-category-4fc4defde8cf" title="Category" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.category`

            Category captures the category classification of the list. It preserves the provider's current classification of this record.

            * **Enables:** separate model list records by the exact provider-reported category value when describing their recorded state.
            * **Interpretation:** The provider supplies `category` per anaplan model list record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-hasselectiveaccess-4c158abaeb45" title="Has Selective Access" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.hasSelectiveAccess`

            Has Selective Access indicates whether selective access is enabled for this list, restricting which items users can see. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported has selective access attached to each anaplan model list record.
            * **Interpretation:** The provider supplies `hasSelectiveAccess` at anaplan model list granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-id-a6f94d0b2ae6" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.id`

            ID captures the unique identifier of the list within the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same anaplan model list source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per anaplan model list record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-itemcount-105c6b161058" title="Item Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.itemCount`

            Item Count captures the total number of items currently in the list. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported item count for each anaplan model list record.
            * **Interpretation:** The provider supplies `itemCount` at anaplan model list granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-managedby-ec01ea288833" title="Managed By" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.managedBy`

            Managed By states indicates how the list is managed, e.g., by the system or a specific process. It preserves the provider's current classification of this record.

            * **Enables:** separate model list records by the exact provider-reported managed by value when describing their recorded state.
            * **Interpretation:** The provider supplies `managedBy` per anaplan model list record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-modelid-f9428d591878" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.modelId`

            Model ID identifies parent id injected by the ingestor from the `workspace_models` to `model_lists` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model list records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `AnaplanModelList`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-name-fd3b03548919" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.name`

            Name captures the display name of the list. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each anaplan model list record.
            * **Interpretation:** The provider supplies `name` at anaplan model list granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-nextitemindex-d3abc08b5cc5" title="Next Item Index" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.nextItemIndex`

            Next Item Index captures the next available item index for numbered lists. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify model list records using the provider-defined next item index value.
            * **Interpretation:** The provider supplies `nextItemIndex` at anaplan model list granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-numberedlist-bae51fe0f031" title="Numbered List" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.numberedList`

            Numbered List indicates whether this list is a numbered list, where items are auto-numbered by Anaplan. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model list records for which the provider reports numbered list as true or false.
            * **Interpretation:** The provider supplies `numberedList` as a boolean per anaplan model list record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-parent-a2edf55b78d8" title="Parent" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.parent`

            Parent records reference to the parent list if this list is part of a hierarchy. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by parent on each anaplan model list record.
            * **Interpretation:** The provider returns `parent` as a nested object or reference on `AnaplanModelList`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-parent-id-dd9e3f42ad5e" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.parent.id`

            ID captures the unique identifier of the referenced list. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model list records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `ListReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-parent-name-f39375cbe831" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.parent.name`

            Name captures the display name of the referenced list. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each list reference record.
            * **Interpretation:** The provider supplies `name` at list reference granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-permitteditems-fe947ced201d" title="Permitted Items" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.permittedItems`

            Permitted Items captures the maximum number of items permitted in the list. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported permitted items for each anaplan model list record.
            * **Interpretation:** The provider supplies `permittedItems` at anaplan model list granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-productiondata-cf778ef8b0ce" title="Production Data" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.productionData`

            Production Data indicates whether this list contains production data (relevant for ALM/revision management). It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model list records for which the provider reports production data as true or false.
            * **Interpretation:** The provider supplies `productionData` as a boolean per anaplan model list record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-propertiescount-89dcd682f36b" title="Properties Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.propertiesCount`

            Properties Count captures the number of properties (custom columns) defined on this list. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret properties count according to the provider and Workspace configuration that produced each model list record.
            * **Interpretation:** Keys and value shapes within `propertiesCount` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-selectiveaccessbydefault-6ed2bf51139e" title="Selective Access By Default" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.selectiveAccessByDefault`

            Selective Access By Default indicates whether selective access is applied by default for new users. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported selective access by default attached to each anaplan model list record.
            * **Interpretation:** The provider supplies `selectiveAccessByDefault` at anaplan model list granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-subsetcount-261fd88e574a" title="Subset Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.subsetCount`

            Subset Count captures the number of subsets defined for this list. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported subset count for each anaplan model list record.
            * **Interpretation:** The provider supplies `subsetCount` at anaplan model list granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-toplevelitem-aeb519df3dc0" title="Top Level Item" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.topLevelItem`

            Top Level Item states reference to the top-level item in the list hierarchy. It preserves the provider's current classification of this record.

            * **Enables:** separate model list records by the exact provider-reported top level item value when describing their recorded state.
            * **Interpretation:** The provider supplies `topLevelItem` per anaplan model list record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-toplevelitem-id-2e81404b94ee" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.topLevelItem.id`

            ID captures the unique identifier of the list item. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model list records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `ListItemReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-toplevelitem-name-d70638c5d4f2" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.topLevelItem.name`

            Name captures the display name of the list item. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each list item reference record.
            * **Interpretation:** The provider supplies `name` at list item reference granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-usedinappliesto-2bdfda0f00c7" title="Used In Applies To" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.usedInAppliesTo`

            Used In Applies To indicates whether this list is used in an applies-to context for line items or modules. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model list records for which the provider reports used in applies to as true or false.
            * **Interpretation:** The provider supplies `usedInAppliesTo` as a boolean per anaplan model list record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-usetoplevelaspagedefault-dd7811b09bdd" title="Use Top Level As Page Default" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.useTopLevelAsPageDefault`

            Use Top Level As Page Default indicates whether the top-level item of the list is used as the default page selection. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model list records for which the provider reports use top level as page default as true or false.
            * **Interpretation:** The provider supplies `useTopLevelAsPageDefault` as a boolean per anaplan model list record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-workflowenabled-10bb60d84a07" title="Workflow Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.workflowEnabled`

            Workflow Enabled indicates whether workflow is enabled for this list. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model list records for which the provider reports workflow enabled as true or false.
            * **Interpretation:** The provider supplies `workflowEnabled` as a boolean per anaplan model list record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-lists-workspaceid-dfa9612d8c69" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_lists.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `workspace_models` to `model_lists` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model list records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `AnaplanModelList`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-modules-8b2fdf88b357" title="Model Modules" icon="brackets-curly" iconType="sharp-duotone-solid">
        Developer identifier: `model_modules`

        Model Modules contain all modules defined within a specific model. Modules are the primary data containers in Anaplan holding line items and views.

        * **Enables:** map the modules that hold line items and views within a model.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{id}/modules` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-modules-allversions-4d4f0f4fc069" title="All Versions" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.allVersions`

            All Versions indicates whether the module applies across all versions. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports all versions as true or false.
            * **Interpretation:** The provider supplies `allVersions` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-cellcount-919be805509c" title="Cell Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.cellCount`

            Cell Count reports the number of data cells in the module. It expresses structural scale independently of the module's byte footprint.

            * **Enables:** compare module complexity and relate cell volume to memory usage.
            * **Interpretation:** The provider supplies `cellCount` as an integer count per module; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-code-4c377de9d80b" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.code`

            Code contains an optional user-defined code for the module, used for external integrations and programmatic references. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret code according to the provider and Workspace configuration that produced each model module record.
            * **Interpretation:** Keys and value shapes within `code` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-currentversion-17ecf61e8e2d" title="Current Version" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.currentVersion`

            Current Version indicates whether the module applies to the current version of the model. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports current version as true or false.
            * **Interpretation:** The provider supplies `currentVersion` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-dimensions-611fc73f3172" title="Dimensions" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.dimensions`

            Dimensions lists the list and time relationships that define the module's structure. It preserves the axes needed to interpret the module's cells.

            * **Enables:** reconstruct module dimensionality and identify which lists or time groupings shape its data.
            * **Interpretation:** The provider supplies `dimensions` as a list of dimension references; an empty list and a missing relationship list are distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-dimensions-id-878a7f014fd6" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.dimensions.id`

            ID captures the unique identifier of the dimension. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same module dimension source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per module dimension record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-dimensions-itemcount-43574c8cc917" title="Item Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.dimensions.itemCount`

            Item Count captures the number of items in this dimension. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported item count for each module dimension record.
            * **Interpretation:** The provider supplies `itemCount` at module dimension granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-dimensions-name-48d2fc1fd780" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.dimensions.name`

            Name captures the display name of the dimension. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each module dimension record.
            * **Interpretation:** The provider supplies `name` at module dimension granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-dimensions-type-1cdf8041c0ec" title="Type" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.dimensions.type`

            Type captures the type of the dimension, such as list, time, or version. It preserves the provider's current classification of this record.

            * **Enables:** separate model module records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per module dimension record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-editable-fa8b0f675e44" title="Editable" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.editable`

            Editable indicates whether the module data is editable by users. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports editable as true or false.
            * **Interpretation:** The provider supplies `editable` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-id-a019792184de" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.id`

            ID captures the unique identifier of the module within the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same anaplan module source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per anaplan module record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-isnumberedlist-283b698c3759" title="Is Numbered List" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.isNumberedList`

            Is Numbered List indicates whether the module is backed by a numbered list. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports is numbered list as true or false.
            * **Interpretation:** The provider supplies `isNumberedList` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-isswitchover-e1b8d8e52d46" title="Is Switchover" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.isSwitchover`

            Is Switchover indicates whether the module uses switchover versioning. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports is switchover as true or false.
            * **Interpretation:** The provider supplies `isSwitchover` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-lineitemcount-772870d41551" title="Line Item Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.lineItemCount`

            Line Item Count captures the number of line items defined within this module. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported line item count for each anaplan module record.
            * **Interpretation:** The provider supplies `lineItemCount` at anaplan module granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-memoryusage-145b96e2bd70" title="Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.memoryUsage`

            Memory Usage reports the bytes consumed by the module. It provides the module-level footprint within its model.

            * **Enables:** identify memory-heavy modules and compare their contribution to model capacity.
            * **Interpretation:** The provider supplies `memoryUsage` as an integer byte value per module; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-modelid-dcca73cadfa5" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.modelId`

            Model ID identifies parent id injected by the ingestor from the `workspace_models` to `model_modules` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model module records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `AnaplanModule`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-modulecategory-5121b7f9d050" title="Module Category" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.moduleCategory`

            Module Category captures the category grouping this module belongs to, if any. It preserves the provider's current classification of this record.

            * **Enables:** separate model module records by the exact provider-reported module category value when describing their recorded state.
            * **Interpretation:** The provider supplies `moduleCategory` per anaplan module record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-modulecategory-id-ad7a9a7e373a" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.moduleCategory.id`

            ID captures the unique identifier of the module category. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model module records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `ModuleCategory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-modulecategory-name-54bfa23074d5" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.moduleCategory.name`

            Name captures the display name of the module category. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each module category record.
            * **Interpretation:** The provider supplies `name` at module category granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-name-80ab07e912b8" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.name`

            Name captures the display name of the module. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each anaplan module record.
            * **Interpretation:** The provider supplies `name` at anaplan module granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-startofsection-2fadc2dcbaae" title="Start Of Section" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.startOfSection`

            Start Of Section indicates whether this module marks the start of a new section in the model contents. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports start of section as true or false.
            * **Interpretation:** The provider supplies `startOfSection` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-useslineitems-bed3de2e0812" title="Uses Line Items" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.usesLineItems`

            Uses Line Items indicates whether the module contains line items. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports uses line items as true or false.
            * **Interpretation:** The provider supplies `usesLineItems` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-viewcount-3e21eaaf904a" title="View Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.viewCount`

            View Count captures the number of saved views defined within this module. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported view count for each anaplan module record.
            * **Interpretation:** The provider supplies `viewCount` at anaplan module granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-visible-a3730c6fb0ec" title="Visible" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.visible`

            Visible indicates whether the module is visible to end users in the Anaplan UI. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model module records for which the provider reports visible as true or false.
            * **Interpretation:** The provider supplies `visible` as a boolean per anaplan module record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-modules-workspaceid-54c97440aed6" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_modules.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `workspace_models` to `model_modules` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model module records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `AnaplanModule`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-model-versions-bed549072c4a" title="Model Versions" icon="timeline" iconType="sharp-duotone-solid">
        Developer identifier: `model_versions`

        Model Versions contain version information (revision tags) for Anaplan models via the ALM API. Tracks model versioning history including who created each version and when, supporting change management and activity tracking.

        * **Enables:** trace ALM revision tags to the creator and creation time recorded by Anaplan.
        * **Scope:** Reads the declared collection through `GET /2/0/models/{id}/alm/revisions` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-model-versions-appliedat-35da17067242" title="Applied At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.appliedAt`

            Applied At records ISO 8601 timestamp indicating when the revision tag was last applied. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model version records on a timeline by applied at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `appliedAt` per model version record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-appliedby-8b13e7891578" title="Applied By" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.appliedBy`

            Applied By captures the user who last applied or deployed this revision tag. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the model version record to the provider-reported person or account represented by applied by.
            * **Interpretation:** The provider supplies `appliedBy` as identity or attribution context on each model version record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-appliedby-email-309adb181283" title="Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.appliedBy.email`

            Email records email address of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user summary record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each user summary record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-appliedby-id-77c8d10f8cbe" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.appliedBy.id`

            ID is the unique identifier of the user. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model version records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `UserSummary`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-appliedby-name-2699fbf560eb" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.appliedBy.name`

            Name records display name of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user summary record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each user summary record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-createdat-bf3789c923bd" title="Created At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.createdAt`

            Created At records ISO 8601 timestamp indicating when the revision tag was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model version records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdAt` per model version record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-createdby-c816b7dc6a30" title="Created By" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.createdBy`

            Created By captures the user who created this revision tag. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the model version record to the provider-reported person or account represented by created by.
            * **Interpretation:** The provider supplies `createdBy` as identity or attribution context on each model version record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-deleted-1540134788b7" title="Deleted" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.deleted`

            Deleted indicates whether the revision tag has been soft-deleted. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select model version records for which the provider reports deleted as true or false.
            * **Interpretation:** The provider supplies `deleted` as a boolean per model version record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-description-deb62b829e18" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.description`

            Description records optional description or notes for the revision tag. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each model version record.
            * **Interpretation:** The provider supplies `description` at model version granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-id-622bd65aa223" title="ID" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.id`

            ID is the unique identifier of the revision tag. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same model version source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per model version record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-modelid-e59e9e66df3c" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.modelId`

            Model ID identifies parent model id injected by the ingestor when iterating per-model. Not part of the upstream Anaplan API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model version records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModelVersion`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-name-85f40fffd439" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.name`

            Name records name or label assigned to the revision tag. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each model version record.
            * **Interpretation:** The provider supplies `name` at model version granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-revisionid-5144ae44cd6b" title="Revision ID" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.revisionId`

            Revision ID captures the internal revision identifier associated with this tag. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model version records to provider records that carry the same revision ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `revisionId` as a record-level identifier on `ModelVersion`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-revisionnumber-cb661765272e" title="Revision Number" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.revisionNumber`

            Revision Number identifies the provider-assigned sequence position of a model revision. It keeps version history snapshots correlated to the revision that produced them.

            * **Enables:** order revisions within one model and detect changed or skipped versions between captured snapshots.
            * **Interpretation:** The provider supplies `revisionNumber` as a model-scoped revision sequence, not a comparable business measure; equal numbers are meaningful only within the same model history.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-syncstate-da188a5cd7f5" title="Sync State" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.syncState`

            Sync State captures the synchronization state of the revision relative to the source model. It preserves the provider's current classification of this record.

            * **Enables:** separate model version records by the exact provider-reported sync state value when describing their recorded state.
            * **Interpretation:** The provider supplies `syncState` per model version record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-tags-748771fb0ef4" title="Tags" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.tags`

            Tags records optional list of tags or labels associated with this revision. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** apply the provider-defined tags classifications to each model version record.
            * **Interpretation:** The provider returns `tags` as a list on `ModelVersion`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-model-versions-workspaceid-7a8a90a9a0d7" title="Workspace ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `model_versions.workspaceId`

            Workspace ID identifies parent workspace id injected by the ingestor when iterating per-workspace. Not part of the upstream Anaplan API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model version records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModelVersion`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-models-e041501ec368" title="Models" icon="brackets-curly" iconType="sharp-duotone-solid">
        Developer identifier: `models`

        Models contain all models across all workspaces accessible to the authenticated user, with optional detailed memory usage information.

        * **Enables:** compare the planning models visible across workspaces and account for their reported memory footprint.
        * **Scope:** Reads the declared collection through `GET /2/0/models` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-models-activestate-f4b89e3d0dca" title="Active State" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.activeState`

            Active State states current active state of the model (e.g., ACTIVE, ARCHIVED). It preserves the provider's current classification of this record.

            * **Enables:** separate model records by the exact provider-reported active state value when describing their recorded state.
            * **Interpretation:** The provider supplies `activeState` per anaplan model record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-categoryvalues-9f7d1d5535c3" title="Category Values" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.categoryValues`

            Category Values states category/tag values associated with the model. Each entry is a category-value object returned by the Anaplan model API. It preserves the provider's current classification of this record.

            * **Enables:** separate model records by the exact provider-reported category values value when describing their recorded state.
            * **Interpretation:** The provider supplies `categoryValues` per anaplan model record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-currentworkspaceid-ff44ceb0f89e" title="Current Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.currentWorkspaceId`

            Current Workspace ID is the identifier of the workspace that currently contains this model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model records to provider records that carry the same current workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `currentWorkspaceId` as a record-level identifier on `AnaplanModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-currentworkspacename-50c8bcb653c0" title="Current Workspace Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `models.currentWorkspaceName`

            Current Workspace Name records display name of the workspace that currently contains this model. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact current workspace name value attached to each anaplan model record.
            * **Interpretation:** The provider supplies `currentWorkspaceName` at anaplan model granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-id-06f75fbd5a53" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.id`

            ID is the unique identifier (GUID) of the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same anaplan model source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per anaplan model record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-isocreationdate-ad30e83391c9" title="Iso Creation Date" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.isoCreationDate`

            Iso Creation Date records ISO 8601 timestamp of when the model was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model records on a timeline by iso creation date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `isoCreationDate` per anaplan model record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-lastmodified-6bf8f52322b7" title="Last Modified" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.lastModified`

            Last Modified records ISO 8601 timestamp of the last modification to the model. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place model records on a timeline by last modified and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastModified` per anaplan model record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-lastmodifiedbyuserguid-f3f82ecccec8" title="Last Modified By User GUID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.lastModifiedByUserGuid`

            Last Modified By User GUID is the GUID of the user who last modified the model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model records to provider records that carry the same last modified by user GUID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `lastModifiedByUserGuid` as a record-level identifier on `AnaplanModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-lastsavedserialnumber-080ba4735853" title="Last Saved Serial Number" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.lastSavedSerialNumber`

            Last Saved Serial Number identifies serial number of the last save operation on the model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model records to provider records that carry the same last saved serial number, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `lastSavedSerialNumber` as a record-level identifier on `AnaplanModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-memoryusage-8771c489d96c" title="Memory Usage" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.memoryUsage`

            Memory Usage reports the total memory usage of the model in bytes. Available when `modelDetails`=true. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported memory usage for each anaplan model record.
            * **Interpretation:** The provider supplies `memoryUsage` at anaplan model granularity as the storage or memory unit named by the provider; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-8e1d0e2e19d6" title="Model Size" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize`

            Model Size groups the cell and memory breakdown returned when `modelDetails`=true. It preserves the component detail needed to explain the model's footprint.

            * **Enables:** attribute total model memory to modules, lists, versions, time, users, and overhead.
            * **Interpretation:** The provider supplies `modelSize` as a nested `ModelSize` object, not a scalar byte value; absence can mean detailed model data was not requested or returned.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-generalmemoryusage-9448f07fcd69" title="General Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.generalMemoryUsage`

            General Memory Usage reports the bytes consumed by general and overhead model data. It isolates the overhead contribution to the model footprint.

            * **Enables:** compare overhead memory between models and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `generalMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-listmemoryusage-956c783d63ae" title="List Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.listMemoryUsage`

            List Memory Usage reports the bytes consumed by list data within the model. It isolates the list contribution to the model footprint.

            * **Enables:** rank models by list memory and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `listMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-modulememoryusage-77b0bd324803" title="Module Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.moduleMemoryUsage`

            Module Memory Usage reports the bytes consumed by module data within the model. It isolates the module contribution to the model footprint.

            * **Enables:** rank models by module memory and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `moduleMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-othermemoryusage-5241555a5569" title="Other Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.otherMemoryUsage`

            Other Memory Usage reports the bytes consumed by model data outside the named memory categories. It preserves the residual contribution to the model footprint.

            * **Enables:** reconcile categorized memory with total usage and identify models with unusually large uncategorized consumption.
            * **Interpretation:** The provider supplies `otherMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-timememoryusage-b1816d856d64" title="Time Memory Usage" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.timeMemoryUsage`

            Time Memory Usage reports the bytes consumed by time-related model data. It isolates the time-data contribution to the model footprint.

            * **Enables:** compare time-related memory between models and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `timeMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-totalmemoryusage-896e60809b2f" title="Total Memory Usage" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.totalMemoryUsage`

            Total Memory Usage reports the total memory usage of the model in bytes. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total memory usage for each model size record.
            * **Interpretation:** The provider supplies `totalMemoryUsage` at model size granularity as the storage or memory unit named by the provider; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-usermemoryusage-53be9880c86f" title="User Memory Usage" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.userMemoryUsage`

            User Memory Usage reports the bytes consumed by user-related model data. It isolates the user-data contribution to the model footprint.

            * **Enables:** compare user-data memory between models and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `userMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelsize-versionmemoryusage-b58b766aae35" title="Version Memory Usage" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelSize.versionMemoryUsage`

            Version Memory Usage reports the bytes consumed by version data within the model. It isolates the version-data contribution to the model footprint.

            * **Enables:** compare version memory between models and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `versionMemoryUsage` as an integer byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modelurl-83c97c153c00" title="Model URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `models.modelUrl`

            Model URL records URL to access the model in the Anaplan web application. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by model URL on a anaplan model record.
            * **Interpretation:** The provider supplies `modelUrl` as a URL or resource locator on each anaplan model record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modules-6f6833eed7eb" title="Modules" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `models.modules`

            Modules records summary list of modules within the model, if returned. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested modules object into its declared child fields for each anaplan model record.
            * **Interpretation:** The provider returns `modules` as a list on `AnaplanModel`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modules-id-a929cf6bd477" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `models.modules.id`

            ID is the unique identifier of the module. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same module summary source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per module summary record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-modules-name-99327a1a0ae6" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `models.modules.name`

            Name records display name of the module. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each module summary record.
            * **Interpretation:** The provider supplies `name` at module summary granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-name-1bd47f305883" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `models.name`

            Name records display name of the model. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each anaplan model record.
            * **Interpretation:** The provider supplies `name` at anaplan model granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-ownerguid-3594d11b4520" title="Owner GUID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.ownerGuid`

            Owner GUID is the GUID of the model owner. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model records to provider records that carry the same owner GUID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `ownerGuid` as a record-level identifier on `AnaplanModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-ownername-e0ba98443232" title="Owner Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `models.ownerName`

            Owner Name records display name of the model owner. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the anaplan model record to the provider-reported actor represented by owner name.
            * **Interpretation:** The provider supplies `ownerName` as identity or attribution context on each anaplan model record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-status-0fd0627661fa" title="Status" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.status`

            Status states operational status of the model. It preserves the provider's current classification of this record.

            * **Enables:** separate model records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per anaplan model record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-urlshortid-411f05f006b0" title="URL Short ID" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `models.urlShortId`

            URL Short ID identifies short identifier used in model URLs. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model records to provider records that carry the same URL short ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `urlShortId` as a record-level identifier on `AnaplanModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-models-version-051d2ce5073a" title="Version" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `models.version`

            Version identifies version identifier of the model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match model records to provider records that carry the same version, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `version` as a record-level identifier on `AnaplanModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-module-views-f836c03a49b1" title="Module Views" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `module_views`

        Module Views contain all saved views within a specific module. Views represent different perspectives/layouts of module data.

        * **Enables:** catalog the saved layouts exposed for each model module.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{workspaceId}/models/{modelId}/modules/{id}/views` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-module-views-code-e4bc7e4aaae5" title="Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.code`

            Code records optional code assigned to the view for external reference. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact code when validating the configuration or technical definition of a module view record.
            * **Interpretation:** The provider supplies `code` as configuration or technical metadata on `ModuleView`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-columns-952cd8f7a403" title="Columns" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.columns`

            Columns records list of dimension descriptors placed on the columns axis of the view. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared columns layout or dimensional scope of each module view record.
            * **Interpretation:** The provider returns `columns` as a list on `ModuleView`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-columns-id-497897b556e2" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.columns.id`

            ID captures the unique identifier of the dimension. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same view dimension source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per view dimension record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-columns-name-7ad6a9facae3" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.columns.name`

            Name captures the display name of the dimension. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each view dimension record.
            * **Interpretation:** The provider supplies `name` at view dimension granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-id-1401be6970bd" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.id`

            ID captures the unique identifier of the view within the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same module view source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per module view record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-modelid-0be9d14021e3" title="Model ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.modelId`

            Model ID identifies parent `modelId` injected by the ingestor from the `model_modules` to `module_views` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match module view records to provider records that carry the same model ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `modelId` as a record-level identifier on `ModuleView`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-moduleid-05403f259dd9" title="Module ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.moduleId`

            Module ID captures the identifier of the module this view belongs to. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match module view records to provider records that carry the same module ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `moduleId` as a record-level identifier on `ModuleView`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-modulename-635c05b71350" title="Module Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.moduleName`

            Module Name captures the name of the module this view belongs to. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact module name value attached to each module view record.
            * **Interpretation:** The provider supplies `moduleName` at module view granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-name-19e6be621b34" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.name`

            Name captures the display name of the saved view. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each module view record.
            * **Interpretation:** The provider supplies `name` at module view granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-pages-c91a1be8a872" title="Pages" icon="filter" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.pages`

            Pages records list of dimension descriptors placed on the pages (filter) axis of the view. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared pages layout or dimensional scope of each module view record.
            * **Interpretation:** The provider returns `pages` as a list on `ModuleView`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-rows-f695bd4127bf" title="Rows" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.rows`

            Rows records list of dimension descriptors placed on the rows axis of the view. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared rows layout or dimensional scope of each module view record.
            * **Interpretation:** The provider returns `rows` as a list on `ModuleView`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-module-views-workspaceid-27f1f9a4d5bf" title="Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `module_views.workspaceId`

            Workspace ID identifies parent `workspaceId` injected by the ingestor from the `model_modules` to `module_views` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match module view records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `ModuleView`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-scim-users-9ef998ced7bb" title="SCIM Users" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `scim_users`

        SCIM Users contain all users provisioned in the Anaplan tenant via SCIM 2.0. Returns user identity, email, active status, and workspace assignments.

        * **Enables:** review provisioned identities and their reported workspace assignments.
        * **Scope:** Reads the declared collection through `GET /scim/1/0/v2/Users` as a full snapshot. Only SCIM-provisioned users visible to the configured account are included.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-scim-users-active-1e09a777afb1" title="Active" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.active`

            Active indicates whether the user account is active in the Anaplan tenant. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select scim user records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per scim user record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-displayname-f6a9af1f0f9c" title="Display Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.displayName`

            Display Name captures the user's full display name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each scim user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-emails-e20fe0cde911" title="Emails" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.emails`

            Emails records list of email addresses associated with the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user record to the provider-reported person or account represented by emails.
            * **Interpretation:** The provider supplies `emails` as identity or attribution context on each scim user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-emails-primary-470d023399ce" title="Primary" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.emails.primary`

            Primary indicates whether this is the user's primary email address. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select scim user records for which the provider reports primary as true or false.
            * **Interpretation:** The provider supplies `primary` as a boolean per scim email record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-emails-type-bff88d0c02fa" title="Type" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.emails.type`

            Type captures the type/label of the email address (e.g., work, home). It preserves the provider's current classification of this record.

            * **Enables:** separate scim user records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per scim email record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-emails-value-2f724ebcad50" title="Value" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.emails.value`

            Value captures the email address value. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same scim email source row before constructing its represented state.
            * **Interpretation:** The provider supplies `value` at one value per scim email record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-entitlements-5c942a0aab23" title="Entitlements" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.entitlements`

            Entitlements states entitlements granted to the user. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported entitlements attached to each scim user record.
            * **Interpretation:** The provider supplies `entitlements` at scim user granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-entitlements-display-2afab22c0e79" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.entitlements.display`

            Display records human-readable display name of the entitlement. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact display value attached to each scim entitlement record.
            * **Interpretation:** The provider supplies `display` at scim entitlement granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-entitlements-primary-a30c98027595" title="Primary" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.entitlements.primary`

            Primary indicates whether this is the user's primary entitlement. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select scim user records for which the provider reports primary as true or false.
            * **Interpretation:** The provider supplies `primary` as a boolean per scim entitlement record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-entitlements-value-e4df2a37ddc7" title="Value" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.entitlements.value`

            Value captures the entitlement identifier or name. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same scim entitlement source row before constructing its represented state.
            * **Interpretation:** The provider supplies `value` at one value per scim entitlement record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-externalid-5ed9ffc10cd6" title="External ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.externalId`

            External ID identifies external identifier for the user, typically set by the identity provider. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match scim user records to provider records that carry the same external ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `externalId` as a record-level identifier on `ScimUser`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-groups-2096c1f9cbc3" title="Groups" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.groups`

            Groups records groups the user belongs to within the Anaplan SCIM directory. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each scim user record with the specific provider container named by groups.
            * **Interpretation:** The provider returns `groups` as a list on `ScimUser`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-groups-ref-4eef82dd2cad" title="$ref" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.groups.$ref`

            \$ref captures the URI reference to the full group resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by \$ref on a scim group ref record.
            * **Interpretation:** The provider supplies `$ref` as a URL or resource locator on each scim group ref record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-groups-display-08dd18e79649" title="Display" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.groups.display`

            Display captures the display name of the group. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact display value attached to each scim group ref record.
            * **Interpretation:** The provider supplies `display` at scim group ref granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-groups-value-04241f05d769" title="Value" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.groups.value`

            Value captures the unique identifier of the group. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same scim group ref source row before constructing its represented state.
            * **Interpretation:** The provider supplies `value` at one value per scim group ref record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-id-5f70e08586f7" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.id`

            ID is the unique identifier for the user within the Anaplan SCIM directory. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same scim user source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per scim user record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-meta-760a7bdf8352" title="Meta" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.meta`

            Meta groups the SCIM resource type, location, and creation and modification timestamps for the user. It preserves lifecycle metadata supplied with the resource.

            * **Enables:** locate the SCIM resource and correlate user snapshots with their reported creation and last-modified boundaries.
            * **Interpretation:** The provider returns `meta` as a nested `ScimMeta` object; absence means the SCIM metadata was not reported with that user.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-meta-created-a7286fdf3e1a" title="Created" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.meta.created`

            Created records ISO 8601 timestamp when the resource was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place scim user records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per scim meta record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-meta-lastmodified-416b72de77c5" title="Last Modified" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.meta.lastModified`

            Last Modified records ISO 8601 timestamp when the resource was last modified. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place scim user records on a timeline by last modified and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastModified` per scim meta record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-meta-location-49b87b2ba000" title="Location" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.meta.location`

            Location captures the canonical URI of the SCIM resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by location on a scim meta record.
            * **Interpretation:** The provider supplies `location` as a URL or resource locator on each scim meta record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-meta-resourcetype-dbd1e0580c88" title="Resource Type" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.meta.resourceType`

            Resource Type captures the SCIM resource type (e.g., User). It preserves the provider's current classification of this record.

            * **Enables:** separate scim user records by the exact provider-reported resource type value when describing their recorded state.
            * **Interpretation:** The provider supplies `resourceType` per scim meta record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-meta-version-184cca57d2a1" title="Version" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.meta.version`

            Version captures the version (ETag) of the SCIM resource for optimistic concurrency. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact version when validating the configuration or technical definition of a scim meta record.
            * **Interpretation:** The provider supplies `version` as configuration or technical metadata on `ScimMeta`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-0d2c0f9599fa" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name`

            Name captures the user's name components (given name, family name, etc.). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each scim user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-familyname-99292235b9ae" title="Family Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name.familyName`

            Family Name captures the user's last name / family name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user name record to the provider-reported person or account represented by family name.
            * **Interpretation:** The provider supplies `familyName` as identity or attribution context on each scim user name record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-formatted-f62a27ac84b7" title="Formatted" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name.formatted`

            Formatted captures the full name formatted for display. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user name record to the provider-reported person or account represented by formatted.
            * **Interpretation:** The provider supplies `formatted` as identity or attribution context on each scim user name record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-givenname-514cb79750a8" title="Given Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name.givenName`

            Given Name captures the user's first name / given name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user name record to the provider-reported person or account represented by given name.
            * **Interpretation:** The provider supplies `givenName` as identity or attribution context on each scim user name record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-honorificprefix-90f244210c41" title="Honorific Prefix" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name.honorificPrefix`

            Honorific Prefix records honorific prefix (e.g., Mr., Dr.). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user name record to the provider-reported person or account represented by honorific prefix.
            * **Interpretation:** The provider supplies `honorificPrefix` as identity or attribution context on each scim user name record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-honorificsuffix-b73197398c7b" title="Honorific Suffix" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name.honorificSuffix`

            Honorific Suffix records honorific suffix (e.g., Jr., III). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user name record to the provider-reported person or account represented by honorific suffix.
            * **Interpretation:** The provider supplies `honorificSuffix` as identity or attribution context on each scim user name record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-name-middlename-52116d7bef3f" title="Middle Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.name.middleName`

            Middle Name captures the user's middle name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user name record to the provider-reported person or account represented by middle name.
            * **Interpretation:** The provider supplies `middleName` as identity or attribution context on each scim user name record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-roles-4dd6557bb19b" title="Roles" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.roles`

            Roles states roles assigned to the user in Anaplan. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported roles attached to each scim user record.
            * **Interpretation:** The provider supplies `roles` at scim user granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-roles-display-e750ab03983a" title="Display" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.roles.display`

            Display records human-readable display name of the role. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact display value attached to each scim role record.
            * **Interpretation:** The provider supplies `display` at scim role granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-roles-primary-d36c44fccf42" title="Primary" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.roles.primary`

            Primary indicates whether this is the user's primary role. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select scim user records for which the provider reports primary as true or false.
            * **Interpretation:** The provider supplies `primary` as a boolean per scim role record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-roles-value-a5aefe4ba009" title="Value" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.roles.value`

            Value captures the role identifier or name. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same scim role source row before constructing its represented state.
            * **Interpretation:** The provider supplies `value` at one value per scim role record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-schemas-f13b4f8a5296" title="Schemas" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.schemas`

            Schemas records SCIM schema URIs applicable to this user resource (e.g., urn:ietf:params:scim:schemas:core:2.0:User and Anaplan extension schemas). It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact schemas when validating the configuration or technical definition of a scim user record.
            * **Interpretation:** The provider supplies `schemas` as configuration or technical metadata on `ScimUser`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-65522418edad" title="Urn SCIM Schemas Extension Anaplan 2 0 User" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User`

            Urn SCIM Schemas Extension Anaplan 2 0 User records Anaplan-specific SCIM extension attributes for the user. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact urn SCIM schemas extension anaplan 2 0 user when validating the configuration or technical definition of a scim user record.
            * **Interpretation:** The provider supplies `urn:scim:schemas:extension:anaplan:2.0:User` as configuration or technical metadata on `ScimUser`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-b7c447db9730" title="Last Login Date" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.lastLoginDate`

            Last Login Date records ISO 8601 timestamp of the user's last login to Anaplan. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place scim user records on a timeline by last login date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastLoginDate` per anaplan user extension record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-d39adf4c4daa" title="Lockout Date" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.lockoutDate`

            Lockout Date records ISO 8601 timestamp when the user account was locked out, if applicable. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place scim user records on a timeline by lockout date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lockoutDate` per anaplan user extension record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-44b6cced2a43" title="Model Creator" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.modelCreator`

            Model Creator indicates whether the user has model creator privileges. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select scim user records for which the provider reports model creator as true or false.
            * **Interpretation:** The provider supplies `modelCreator` as a boolean per anaplan user extension record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-ad0fa3e8958a" title="Tenant Admin" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.tenantAdmin`

            Tenant Admin indicates whether the user has tenant administrator privileges. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported tenant admin attached to each anaplan user extension record.
            * **Interpretation:** The provider supplies `tenantAdmin` at anaplan user extension granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-57816ec4243c" title="Workspaces" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.workspaces`

            Workspaces records list of Anaplan workspaces the user is assigned to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each anaplan user extension record with the specific provider container named by workspaces.
            * **Interpretation:** The provider returns `workspaces` as a list on `AnaplanUserExtension`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-3b7680f0a63e" title="Active" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.workspaces.active`

            Active indicates whether the user's assignment to this workspace is currently active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select scim user records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per anaplan workspace assignment record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-58539baf0397" title="Role" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.workspaces.role`

            Role captures the user's role within the workspace. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported role attached to each anaplan workspace assignment record.
            * **Interpretation:** The provider supplies `role` at anaplan workspace assignment granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-d599139ed8ec" title="Workspace ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.workspaces.workspaceId`

            Workspace ID captures the unique identifier of the Anaplan workspace. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match scim user records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `AnaplanWorkspaceAssignment`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-urn-scim-schemas-extension-an-b484d4996f5a" title="Workspace Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.urn:scim:schemas:extension:anaplan:2.0:User.workspaces.workspaceName`

            Workspace Name captures the display name of the Anaplan workspace. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact workspace name value attached to each anaplan workspace assignment record.
            * **Interpretation:** The provider supplies `workspaceName` at anaplan workspace assignment granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-scim-users-username-9ce4a241a9c5" title="User Name" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `scim_users.userName`

            User Name captures the user's login name, typically their email address. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the scim user record to the provider-reported actor represented by user name.
            * **Interpretation:** The provider supplies `userName` as identity or attribution context on each scim user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-users-4e891cafa825" title="Users" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `users`

        Users contain all users in the Anaplan tenant via the Integration API v2. Returns user identity, email, active status, and admin role. Does not require SCIM provisioning or Enterprise tier.

        * **Enables:** resolve Anaplan account identities, active state, and administrator context without requiring SCIM.
        * **Scope:** Reads the declared collection through `GET /2/0/users` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-users-active-19de6c835304" title="Active" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.active`

            Active indicates whether the user account is currently enabled. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per anaplan user record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-customerid-35ff3a9ad9cc" title="Customer ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.customerId`

            Customer ID identifies Anaplan customer/tenant identifier associated with the user. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match user records to provider records that carry the same customer ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `customerId` as a record-level identifier on `AnaplanUser`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-email-4c96a92aefd1" title="Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.email`

            Email records user email address (login identifier). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the anaplan user record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each anaplan user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-emailoptin-df9f3ab7c655" title="Email Opt In" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `users.emailOptIn`

            Email Opt In indicates whether the user has opted in to Anaplan email communications. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports email opt in as true or false.
            * **Interpretation:** The provider supplies `emailOptIn` as a boolean per anaplan user record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-firstname-9ccae2c0b6fd" title="First Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.firstName`

            First Name records user first name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the anaplan user record to the provider-reported person or account represented by first name.
            * **Interpretation:** The provider supplies `firstName` as identity or attribution context on each anaplan user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-id-4e943707069a" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.id`

            ID is the unique Anaplan-assigned user identifier. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same anaplan user source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per anaplan user record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-lastlogindate-2360c8c05ff6" title="Last Login Date" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `users.lastLoginDate`

            Last Login Date records ISO 8601 timestamp of the user's last login, if available. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place user records on a timeline by last login date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastLoginDate` per anaplan user record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-lastname-c28503746d36" title="Last Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `users.lastName`

            Last Name records user last name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the anaplan user record to the provider-reported person or account represented by last name.
            * **Interpretation:** The provider supplies `lastName` as identity or attribution context on each anaplan user record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-users-tenantadmin-a3cc7d3e27ce" title="Tenant Admin" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `users.tenantAdmin`

            Tenant Admin indicates whether the user has tenant administrator privileges. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported tenant admin attached to each anaplan user record.
            * **Interpretation:** The provider supplies `tenantAdmin` at anaplan user granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-workspace-models-67a06e5b3dfb" title="Workspace Models" icon="brackets-curly" iconType="sharp-duotone-solid">
        Developer identifier: `workspace_models`

        Workspace Models contain all models within a specific workspace.

        * **Enables:** enumerate planning models within each parent workspace.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces/{id}/models` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-workspace-models-activestate-5d85fce3b01d" title="Active State" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.activeState`

            Active State states current active state of the model (e.g., ACTIVE, ARCHIVED). It preserves the provider's current classification of this record.

            * **Enables:** separate workspace model records by the exact provider-reported active state value when describing their recorded state.
            * **Interpretation:** The provider supplies `activeState` per workspace model record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-categoryvalues-0ceaea49b995" title="Category Values" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.categoryValues`

            Category Values states list of category/tag values associated with the model. It preserves the provider's current classification of this record.

            * **Enables:** separate workspace model records by the exact provider-reported category values value when describing their recorded state.
            * **Interpretation:** The provider supplies `categoryValues` per workspace model record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-categoryvalues-category-aa93d44f06af" title="Category ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.categoryValues.categoryId`

            Category ID is the identifier of the parent category. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match workspace model records to provider records that carry the same category ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `categoryId` as a record-level identifier on `CategoryValue`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-categoryvalues-category-d4ee54ae8f88" title="Category Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.categoryValues.categoryName`

            Category Name states display name of the parent category. It preserves the provider's current classification of this record.

            * **Enables:** separate workspace model records by the exact provider-reported category name value when describing their recorded state.
            * **Interpretation:** The provider supplies `categoryName` per category value record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-categoryvalues-id-d3894314068d" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.categoryValues.id`

            ID is the unique identifier of the category value. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same category value source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per category value record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-categoryvalues-name-65939e44054c" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.categoryValues.name`

            Name records display name of the category value. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each category value record.
            * **Interpretation:** The provider supplies `name` at category value granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-currentworkspaceid-0cad653629b5" title="Current Workspace ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.currentWorkspaceId`

            Current Workspace ID is the identifier of the workspace that currently contains this model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match workspace model records to provider records that carry the same current workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `currentWorkspaceId` as a record-level identifier on `WorkspaceModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-currentworkspacename-e2f44b2cbefc" title="Current Workspace Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.currentWorkspaceName`

            Current Workspace Name records name of the workspace that currently contains this model. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact current workspace name value attached to each workspace model record.
            * **Interpretation:** The provider supplies `currentWorkspaceName` at workspace model granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-id-bd1e1541de90" title="ID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.id`

            ID is the unique identifier (GUID) of the model. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same workspace model source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per workspace model record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-isocreationdate-f4659bea5d0e" title="Iso Creation Date" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.isoCreationDate`

            Iso Creation Date records ISO 8601 timestamp of when the model was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place workspace model records on a timeline by iso creation date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `isoCreationDate` per workspace model record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-lastmodified-807f3ab0137b" title="Last Modified" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.lastModified`

            Last Modified records last-modified timestamp returned by the workspace models API (same instant as `lastModifiedDate` when both are present). It anchors the named event or boundary on the record's timeline.

            * **Enables:** place workspace model records on a timeline by last modified and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastModified` per workspace model record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-lastmodifiedbyuserguid-cfda306a9417" title="Last Modified By User GUID" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.lastModifiedByUserGuid`

            Last Modified By User GUID is the GUID of the user who last modified the model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match workspace model records to provider records that carry the same last modified by user GUID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `lastModifiedByUserGuid` as a record-level identifier on `WorkspaceModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-lastmodifieddate-b80d0659ccf2" title="Last Modified Date" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.lastModifiedDate`

            Last Modified Date records ISO 8601 timestamp of when the model was last modified. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place workspace model records on a timeline by last modified date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastModifiedDate` per workspace model record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-lastsavedserialnumber-c269b6b57844" title="Last Saved Serial Number" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.lastSavedSerialNumber`

            Last Saved Serial Number identifies serial number of the last save operation on the model. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match workspace model records to provider records that carry the same last saved serial number, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `lastSavedSerialNumber` as a record-level identifier on `WorkspaceModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-memoryusage-f383bf69a2b6" title="Memory Usage" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.memoryUsage`

            Memory Usage reports the model's total memory consumption in bytes when `modelDetails`=true. It supplies the overall footprint for the workspace-model relationship.

            * **Enables:** rank models within a workspace by memory consumption and track capacity concentration.
            * **Interpretation:** The provider supplies `memoryUsage` as a numeric byte value per workspace-model record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelsize-bd4990d5309d" title="Model Size" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelSize`

            Model Size groups the model's cell total and component memory breakdown. It preserves the detail needed to explain the workspace model's footprint.

            * **Enables:** relate model scale in cells to the memory consumed by modules, lists, and other components.
            * **Interpretation:** The provider supplies `modelSize` as a nested `ModelSize` object, not a scalar byte value; absence means the breakdown was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelsize-listmemoryusa-340ece85b3d7" title="List Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelSize.listMemoryUsage`

            List Memory Usage reports the bytes consumed by list data within the workspace model. It isolates the list contribution to the model footprint.

            * **Enables:** rank workspace models by list memory and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `listMemoryUsage` as a numeric byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelsize-modulememoryu-f77647ed0a40" title="Module Memory Usage" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelSize.moduleMemoryUsage`

            Module Memory Usage reports the bytes consumed by module data within the workspace model. It isolates the module contribution to the model footprint.

            * **Enables:** rank workspace models by module memory and calculate its share of total memory usage.
            * **Interpretation:** The provider supplies `moduleMemoryUsage` as a numeric byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelsize-othermemoryus-47e5419c681d" title="Other Memory Usage" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelSize.otherMemoryUsage`

            Other Memory Usage reports the bytes consumed by workspace-model components outside the named categories. It preserves the residual contribution to the model footprint.

            * **Enables:** reconcile categorized memory with total usage and identify models with unusually large uncategorized consumption.
            * **Interpretation:** The provider supplies `otherMemoryUsage` as a numeric byte value per model-size record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelsize-totalcells-bb72621335fe" title="Total Cells" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelSize.totalCells`

            Total Cells reports the total number of cells across all modules in the model. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total cells for each model size record.
            * **Interpretation:** The provider supplies `totalCells` at model size granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelsize-totalmemoryus-08fe9f6865ee" title="Total Memory Usage" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelSize.totalMemoryUsage`

            Total Memory Usage reports the total memory usage of the model in bytes. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total memory usage for each model size record.
            * **Interpretation:** The provider supplies `totalMemoryUsage` at model size granularity as the storage or memory unit named by the provider; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modelurl-ad95eb08f758" title="Model URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modelUrl`

            Model URL records URL to access the model in the Anaplan web interface. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by model URL on a workspace model record.
            * **Interpretation:** The provider supplies `modelUrl` as a URL or resource locator on each workspace model record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modules-b605c70743c2" title="Modules" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modules`

            Modules records summary list of modules within the model, if returned. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested modules object into its declared child fields for each workspace model record.
            * **Interpretation:** The provider returns `modules` as a list on `WorkspaceModel`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modules-id-a51dcdfd13eb" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modules.id`

            ID is the unique identifier of the module. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same module summary source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per module summary record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-modules-name-0cb330bf9d2e" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.modules.name`

            Name records display name of the module. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each module summary record.
            * **Interpretation:** The provider supplies `name` at module summary granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-name-19e276f61cba" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.name`

            Name records display name of the model. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each workspace model record.
            * **Interpretation:** The provider supplies `name` at workspace model granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspace-models-workspaceid-84f288c1f478" title="Workspace ID" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `workspace_models.workspaceId`

            Workspace ID identifies parent id injected by the ingestor from the workspaces to `workspace_models` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match workspace model records to provider records that carry the same workspace ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `workspaceId` as a record-level identifier on `WorkspaceModel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-anaplan-workspaces-f847b262a20b" title="Workspaces" icon="table" iconType="sharp-duotone-solid">
        Developer identifier: `workspaces`

        Workspaces contain all workspaces accessible to the authenticated user. Core organizational container in Anaplan.

        * **Enables:** enumerate the Anaplan containers available to the configured account before resolving model-scoped records.
        * **Scope:** Reads the declared collection through `GET /2/0/workspaces` as a full snapshot. Results are limited to objects visible to the configured Anaplan exception user; inaccessible workspaces and models are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-anaplan-workspaces-active-0129ef0e8951" title="Active" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.active`

            Active indicates whether the workspace is currently active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select workspace records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per workspace record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspaces-currentsize-8a6e5fc9f3d4" title="Current Size" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.currentSize`

            Current Size reports the workspace storage currently used in bytes. It provides the usage value needed alongside the configured allowance.

            * **Enables:** calculate capacity utilization and identify the workspaces with the largest storage footprint.
            * **Interpretation:** The provider supplies `currentSize` as an integer byte value per workspace; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspaces-id-3e7736701aec" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.id`

            ID is the unique identifier for the workspace. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same workspace source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per workspace record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspaces-name-919b6f57cfc3" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.name`

            Name records display name of the workspace. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each workspace record.
            * **Interpretation:** The provider supplies `name` at workspace granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-anaplan-workspaces-sizeallowance-cef1cf9cb183" title="Size Allowance" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.sizeAllowance`

            Size Allowance reports the maximum workspace storage capacity in bytes. It establishes the capacity ceiling paired with current size.

            * **Enables:** compare allotted capacity with current use to identify workspaces approaching their storage limit.
            * **Interpretation:** The provider supplies `sizeAllowance` as an integer byte value per workspace; zero and missing are not interchangeable.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    | Error                                | Meaning               | Solution                                                 |
    | ------------------------------------ | --------------------- | -------------------------------------------------------- |
    | `401 Unauthorized` on token endpoint | Bad email or password | Verify credentials                                       |
    | `401 Caller is unauthorized` on SCIM | Missing Tenant Admin  | Grant Tenant Admin to the integration account            |
    | `401 No valid token header` on audit | Audit auth mismatch   | Confirm Tenant Auditor; audit may require different auth |
    | `403 Forbidden` on workspaces        | Insufficient access   | Grant Workspace Admin on target workspaces               |
    | Password stopped working             | Rotation policy       | Use Exception User or update the Provider password       |

    #### Common Issues

    #### Account locked after failed attempts

    Contact your Tenant Admin to unlock the account.

    #### SCIM returns empty user list

    Workspace Admin alone is not enough; the account needs **Tenant Admin** for SCIM.

    #### Audit events not available

    Confirm Tenant Auditor role and supported auth for the audit API with Anaplan support.

    **[Anaplan REST API](https://help.anaplan.com/anaplan-api-844c6d40-a21c-423d-8435-ebaaa0372b76)** — API documentation

    **[SCIM API](https://help.anaplan.com/anaplan-scim-api-f6a801cd-c253-4ab9-ba03-dac09fd71f7c)** — User provisioning API

    **[Audit API](https://auditservice.docs.apiary.io/)** — Audit event API reference
  </Tab>
</Tabs>