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

# monday.com

> Sync boards, items, users, teams, workspaces, updates, tags, docs, and activity logs from monday.com

Sync boards, items, users, teams, workspaces, updates, tags, docs, and activity logs from monday.com.

<Tabs>
  <Tab title="Overview">
    ### Personal API Token

    Connect Parable to Monday.com using a personal API token and the GraphQL API. The token is tied to your user and inherits your account permissions, so the data Parable can sync depends on what your user can see. For full-account coverage, use an administrator's token.

    > **Info:** The token inherits your user's permissions. A member token only reaches boards that user is subscribed to; an administrator token reaches the whole account.

    #### Boards & work items

    Boards, groups, columns, items, subitems, tags, activity logs

    #### People & workspaces

    Users, teams, workspaces

    #### Collaboration

    Updates, replies, WorkDocs

    ### Personal API Token

    Monday.com serves a single GraphQL endpoint. Parable sends the API version header shown below.

    ```
    POST https://api.monday.com/v2
    ```

    The token is sent in the `Authorization` header **without** a `Bearer` prefix. Parable also sends `API-Version: 2025-04` and `Content-Type: application/json`.

    ### Personal API Token

    All of the tables below are collected for a connection. The access level of your token determines how much data each returns.

    | Data                           | Access needed                                |
    | ------------------------------ | -------------------------------------------- |
    | Boards, groups, columns        | Admin, or member subscribed to the board     |
    | Items, subitems, column values | Admin, or member subscribed to the board     |
    | Users                          | Admin (member tokens return limited results) |
    | Teams                          | Admin                                        |
    | Workspaces                     | Admin                                        |
    | Updates & replies              | Admin, or access to the item's board         |
    | Tags                           | Admin                                        |
    | WorkDocs                       | Access to the doc or its workspace           |
    | Activity logs                  | Admin **and** an Enterprise plan             |

    ### Personal API Token

    #### Query boards with items

    ```graphql theme={null}
    query {
      boards(limit: 10) {
        id
        name
        state
        items_page {
          items {
            id
            name
            column_values {
              id
              value
            }
          }
        }
      }
    }
    ```

    #### Query users

    ```graphql theme={null}
    query {
      users {
        id
        name
        email
        is_admin
        created_at
      }
    }
    ```

    ### OAuth 2.0 Authorization Code (3LO)

    Connect Parable to Monday.com using OAuth 2.0. You create a Monday.com app in the Developer Center, create the connection in Parable, register Parable's redirect URI on your app, then authorize through Parable's in-app wizard. Parable exchanges the authorization code for an access token and stores it securely.

    > **Info:** You do not enter an access token manually. The in-app wizard completes the OAuth flow for you.

    #### Boards & work items

    Boards, groups, columns, items, subitems, tags, activity logs

    #### People & workspaces

    Users, teams, workspaces

    #### Collaboration

    Updates, replies, WorkDocs

    ### OAuth 2.0 Authorization Code (3LO)

    Authorize (browser redirect):

    ```
    GET https://auth.monday.com/oauth2/authorize
    ```

    Token exchange (used by Parable after authorization):

    ```
    POST https://auth.monday.com/oauth2/token
    ```

    Token exchange uses `client_secret_post` (client ID and secret sent in the request body). Syncs call the GraphQL endpoint at `https://api.monday.com/v2` with `API-Version: 2025-04`.

    ## Data streams

    This Provider Plugin defines 9 data streams.

    | Stream          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                           | Sync        |
    | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
    | `boards`        | Extracts all boards from Monday.com, including metadata such as name, description, board kind, type, state, workspace, creator, owners, subscribers, top group, columns, groups, tags, and views. Uses page-based pagination with limit=50 per page. Requires boards:read scope.                                                                                                                                                                      | full        |
    | `items`         | Extracts all items (tasks/rows) from Monday.com boards using cursor-based pagination via items\_page per board, then next\_items\_page for subsequent pages. Includes column values, group membership, creator, board reference, parent item, assets, subscribers, and subitem references. Requires iterating over all boards first. Requires boards:read scope.                                                                                      | full        |
    | `users`         | Extracts all users from Monday.com, including profile details, admin/guest status, timezone, and team memberships. Uses page-based pagination with limit=500 per page. Requires users:read scope.                                                                                                                                                                                                                                                     | full        |
    | `teams`         | Extracts all teams from Monday.com, including team name, picture URL, and member user references. No pagination documented; returns all teams in a single response. Requires teams:read scope.                                                                                                                                                                                                                                                        | full        |
    | `workspaces`    | Extracts all workspaces from Monday.com, including name, kind, and description. Uses page-based pagination with limit=50 per page. Requires workspaces:read scope.                                                                                                                                                                                                                                                                                    | full        |
    | `updates`       | Extracts all updates (comments and activity posts) on Monday.com items, including body text, creator, timestamps, and nested replies. Uses page-based pagination with limit=100 per page. Requires updates:read scope.                                                                                                                                                                                                                                | full        |
    | `tags`          | Extracts all tags from Monday.com, including name and color. No pagination documented; returns all tags in a single response. Requires tags:read scope.                                                                                                                                                                                                                                                                                               | full        |
    | `docs`          | Extracts all WorkDocs from Monday.com, including name, kind, creation timestamp, associated object, relative URL, and content blocks. Uses page-based pagination with limit=50 per page. Requires docs:read scope.                                                                                                                                                                                                                                    | full        |
    | `activity_logs` | Extracts activity log entries per board from Monday.com (Enterprise plan only). Each entry records who performed what action on a board and when. Traverses all boards and fetches activity\_logs per board with time-range filtering for incremental sync. Confidence on data field schema is moderate (0.70) as the field is JSON-encoded and its internal structure is not fully documented. Requires boards:read scope; Enterprise plan required. | incremental |
  </Tab>

  <Tab title="Setup Guide">
    ### Personal API Token

    #### What You'll Need

    | Credential    | What it is                                      |
    | ------------- | ----------------------------------------------- |
    | **API Token** | Personal API token from your Monday.com account |

    > **Info:** **Setup access in Monday.com.** These steps require **Administrator (recommended, for full-account access)**, or a colleague with equivalent permissions who can create credentials for you.
    >
    > If that is not you, ask your Monday.com administrator.

    * Any account member can generate a personal token, but the token only reaches data that user can access.
    * An **Administrator** token is recommended so Parable can sync all boards, users, teams, and workspaces.
    * Activity logs require a Monday.com **Enterprise** plan.

    #### Step 1: Open your developer settings

    1. Sign in to Monday.com (use an administrator account for full-account access).
    2. Click your **avatar** (bottom-left) and open **Developers**.
    3. Select **API token**.

    #### Step 2: Copy your API token

    1. Click **Show** to reveal your personal token, or **Regenerate** to create a new one.
    2. Copy the token.

    You can return to this page and click **Show** whenever you need to display the token again.

    > **Warning:** Regenerating a token invalidates the previous one. Any connection still using the old token stops syncing until you update it.

    #### Step 3: Confirm the token's access level

    The token inherits the permissions of your user account:

    * **Administrators** reach every board, user, team, and workspace.
    * **Members** reach only the boards they are subscribed to.

    > **Tip:** Use an administrator account so Parable can sync your full account.

    #### Step 4: Enter the token in Parable

    1. Open the Monday.com **API Token** Provider in Parable and add a connection.
    2. Enter a **connection name**.
    3. Paste your **API Token**.
    4. Click **Save & test connection**.

    Use an environment variable so the token does not land in your shell history.

    ```bash Identity probe theme={null}
    read -rs -p "Monday API token: " MONDAY_TOKEN && echo
    curl --silent -X POST "https://api.monday.com/v2" \
      -H "Authorization: ${MONDAY_TOKEN}" \
      -H "API-Version: 2025-04" \
      -H "Content-Type: application/json" \
      -d '{"query": "{ me { id name email } }"}'
    ```

    ```bash List boards theme={null}
    curl --silent -X POST "https://api.monday.com/v2" \
      -H "Authorization: ${MONDAY_TOKEN}" \
      -H "API-Version: 2025-04" \
      -H "Content-Type: application/json" \
      -d '{"query": "{ boards(limit: 5) { id name } }"}'
    unset MONDAY_TOKEN
    ```

    > **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:** **Rate Limits:** Monday.com enforces rate limits of **complexity-based (up to 10,000,000 complexity points/minute depending on plan), plus a global cap of about 1.67 requests/second**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

    ### OAuth 2.0 Authorization Code (3LO)

    #### What You'll Need

    | Credential        | What it is                                                       |
    | ----------------- | ---------------------------------------------------------------- |
    | **Client ID**     | OAuth application client ID from the Monday.com Developer Center |
    | **Client Secret** | OAuth application client secret                                  |

    > **Info:** **Setup access in Monday.com.** These steps require **Administrator (to create apps in the Developer Center)**, or a colleague with equivalent permissions who can create credentials for you.
    >
    > If that is not you, ask your Monday.com administrator.

    * A Monday.com app created in the Developer Center with OAuth enabled
    * The read scopes listed in step 2 enabled on the app
    * Permission to register a redirect URI on the app's OAuth settings
    * Activity logs require a Monday.com **Enterprise** plan

    #### Step 1: Create a Monday.com app

    1. Sign in to Monday.com as an administrator.
    2. Open `https://{your-account}.monday.com/apps/manage`, replacing `{your-account}` with your Monday.com account subdomain. Confirm **My Apps** is selected, then click **Create app**.
    3. Open the app's **OAuth & Permissions** section and note the **Client ID** and **Client Secret**.
    4. If Monday.com requires a redirect URL before you can continue, enter a valid placeholder URL. You will replace it with the Parable redirect URI in step 4.

    > **Warning:** **Copy your Client Secret now!**
    >
    > This is the only time it will be displayed. Store it in a secure password manager before closing this page.

    #### Step 2: Enable the required scopes

    On the app's **OAuth & Permissions** page, enable every read scope below so Parable can sync all Monday.com data:

    | Scope             | Enables                                                 |
    | ----------------- | ------------------------------------------------------- |
    | `boards:read`     | Boards, groups, columns, items, subitems, activity logs |
    | `users:read`      | Users                                                   |
    | `teams:read`      | Teams                                                   |
    | `workspaces:read` | Workspaces                                              |
    | `updates:read`    | Updates and replies                                     |
    | `tags:read`       | Tags                                                    |
    | `docs:read`       | WorkDocs                                                |

    > **Info:** These are read-only scopes. Monday.com's OAuth here is 3-legged (authorization code); Parable stores the access token after you approve. Activity logs also require an Enterprise plan.

    #### Step 3: Create the connection in Parable

    1. Open the Monday.com **OAuth** Provider in Parable and add a connection.
    2. Enter a **connection name**.
    3. Copy the **Redirect URI** shown on the form.
    4. Click **Continue to OAuth setup**.

    Parable creates the connection and opens the OAuth authorization screen.

    #### Step 4: Register the redirect URI in Monday.com

    1. In your Monday.com app **OAuth & Permissions** settings, add the **Redirect URI** you copied from Parable under **Redirect URLs**, replacing any placeholder URL entered in step 1.
    2. Register it **exactly** as shown, including your workspace subdomain and path.

    > **Info:** The redirect URI includes your workspace subdomain. Example:
    > `https://{tenant-name}.parable.work/platform/providers/oauth/callback`.
    > Do **not** register the apex host alone (`https://parable.work/...`). Monday.com must match the subdomain of the workspace where you started the connection.

    #### Step 5: Authorize with Parable

    1. On the OAuth authorization screen, enter your **Client ID** and **Client Secret**.
    2. Click **Connect with OAuth**. You are redirected to Monday.com to approve the requested permissions.
    3. After you approve, Parable redirects back automatically, stores your access token securely, and validates the connection.

    > **Info:** Monday.com's legacy OAuth returns a long-lived access token that stays valid until the app is uninstalled. To rotate credentials or recover from a revoked token, click **Re-authorize with OAuth** on the connection page.
  </Tab>

  <Tab title="Permissions">
    ### OAuth 2.0 Authorization Code (3LO)

    | Scope             | Enables                                                 |
    | ----------------- | ------------------------------------------------------- |
    | `boards:read`     | Boards, groups, columns, items, subitems, activity logs |
    | `users:read`      | Users                                                   |
    | `teams:read`      | Teams                                                   |
    | `workspaces:read` | Workspaces                                              |
    | `updates:read`    | Updates and replies                                     |
    | `tags:read`       | Tags                                                    |
    | `docs:read`       | WorkDocs                                                |

    > **Info:** Enable all scopes above for complete coverage. Activity logs also require a Monday.com Enterprise plan.

    > **Success:** After authorization, Parable shows an authorized status and validates the connection automatically.

    > **Tip:** **Rate Limits:** Monday.com enforces rate limits of **complexity-based (up to 10,000,000 complexity points/minute depending on plan), plus a global cap of about 1.67 requests/second**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

    <AccordionGroup>
      <Accordion id="provider-permission-tap-monday-activity-logs-581b6547baec" title="Activity Logs" icon="user-shield" iconType="sharp-duotone-solid">
        Developer identifier: `activity_logs`

        Activity Logs contain activity log entries per board from Monday.com (Enterprise plan only). Each entry records who performed what action on a board and when. Traverses all boards and fetches `activity_logs` per board with an explicit time-range request for incremental sync. Confidence on data field schema is moderate (0.70) as the field is JSON-encoded and its internal structure is not fully documented. Requires boards:read scope; Enterprise plan required.

        * **Enables:** trace Enterprise board actions to the provider-reported actor, event, and time.
        * **Scope:** Reads provider changes through the declared GraphQL operation using the declared incremental request boundary. The operation requires the stated monday.com read scope and an Enterprise plan.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-activity-logs-account-id-d3ef3b649e24" title="Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.account_id`

            Account ID is the ID of the account that initiated the event. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-activity-logs-board-id-8788b047391f" title="Board ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.board_id`

            Board ID is the ID of the board on which the activity occurred. Derived from the parent boards query traversal. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-activity-logs-created-at-0f552e02ff0c" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.created_at`

            Created At records the timestamp indicating when the event occurred. Board logs use 17-digit Unix time. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place activity log records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per activity log 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-monday-activity-logs-data-c2cad213da2b" title="Data" icon="circle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.data`

            Data records JSON-encoded event-specific data payload. Internal structure varies by event type and is not fully documented. Confidence: 0.70. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret data according to the provider and Workspace configuration that produced each activity log record.
            * **Interpretation:** Keys and value shapes within `data` 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-monday-activity-logs-entity-3acd1c115e78" title="Entity" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.entity`

            Entity records entity the event refers to (e.g. board, pulse, column). It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-activity-logs-event-1a0e2f4d0745" title="Event" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.event`

            Event states event type describing the action performed (e.g., `create_item`, `change_column_value`). It preserves the provider's current classification of this record.

            * **Enables:** separate activity log records by the exact provider-reported event value when describing their recorded state.
            * **Interpretation:** The provider supplies `event` per activity log record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, event is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-activity-logs-id-39c76077d7ba" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.id`

            ID is the unique activity log entry identifier. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-monday-activity-logs-user-id-ea9ae335e056" title="User ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `activity_logs.user_id`

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

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

      <Accordion id="provider-permission-tap-monday-boards-0e50f395c96d" title="Boards" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `boards`

        Boards contain all boards from Monday.com, including metadata such as name, description, board kind, type, state, workspace, creator, owners, subscribers, top group, columns, groups, tags, and views. Uses page-based pagination with `limit=50` per page. Requires boards:read scope.

        * **Enables:** catalog monday.com boards and their workspace, owners, columns, groups, tags, and views.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-boards-board-folder-id-5e050674d2fa" title="Board Folder ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `boards.board_folder_id`

            Board Folder ID is the ID of the folder containing this board, if any. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-boards-board-kind-7aafcd221f8d" title="Board Kind" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `boards.board_kind`

            Board Kind states visibility kind of the board: public, private, or share. It preserves the provider's current classification of this record.

            * **Enables:** separate board records by the exact provider-reported board kind value when describing their recorded state.
            * **Interpretation:** The provider supplies `board_kind` per board record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, board kind is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-columns-ac56cc4a75e5" title="Columns" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `boards.columns`

            Columns records array of column definitions on this board. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared columns layout or dimensional scope of each board record.
            * **Interpretation:** The provider returns `columns` as a list on `Board`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-columns-id-eec96383a7f1" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.columns.id`

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

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

          <Accordion id="provider-permission-field-monday-boards-columns-title-dc19a8135446" title="Title" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `boards.columns.title`

            Title records display title of the column. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-boards-columns-type-44e4e5257122" title="Type" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `boards.columns.type`

            Type states column type identifier (e.g., text, status, date, people, numbers). It preserves the provider's current classification of this record.

            * **Enables:** separate board records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per column record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-creator-bf7442a7392d" title="Creator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `boards.creator`

            Creator captures the user who created this board. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the board record to the provider-reported actor represented by creator.
            * **Interpretation:** The provider supplies `creator` as identity or attribution context on each board record. In monday.com, creator is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-creator-email-c0f6dfad53b5" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `boards.creator.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 record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each user record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-creator-id-effa49f0c21e" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.creator.id`

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

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

          <Accordion id="provider-permission-field-monday-boards-creator-name-9c31afe12da2" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.creator.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 record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each user record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-description-a77829d0d0fb" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `boards.description`

            Description records optional description of the board. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-boards-groups-6109df70e2ec" title="Groups" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.groups`

            Groups records array of group definitions on this board. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each board record with the specific provider container named by groups.
            * **Interpretation:** The provider returns `groups` as a list on `Board`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-groups-color-d0f708397ae7" title="Color" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.groups.color`

            Color records hex color code associated with the group. It preserves the provider's visual treatment for the represented object.

            * **Enables:** reproduce or compare the provider-supplied color for the represented design or board object.
            * **Interpretation:** The provider supplies `color` in its own color, opacity, stroke, emoji, or style vocabulary for the represented object.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-groups-id-b4040d04aedd" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.groups.id`

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

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

          <Accordion id="provider-permission-field-monday-boards-groups-title-c792ec47ad03" title="Title" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `boards.groups.title`

            Title records display title of the group. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-boards-id-cfa026a3130b" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.id`

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

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

          <Accordion id="provider-permission-field-monday-boards-items-count-bf56d34c9d7e" title="Items Count" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `boards.items_count`

            Items Count reports the number of items on the board. It preserves the stated measure at this record's granularity.

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

          <Accordion id="provider-permission-field-monday-boards-name-c1691a7f74a4" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.name`

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

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

          <Accordion id="provider-permission-field-monday-boards-owners-bba7a44cf7da" title="Owners" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.owners`

            Owners records users who own this board. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the board record to the provider-reported actor represented by owners.
            * **Interpretation:** The provider supplies `owners` as identity or attribution context on each board record. In monday.com, owners is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-permissions-0645530416ce" title="Permissions" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `boards.permissions`

            Permissions states board permission setting. It documents the access-related value reported for this object or membership.

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

          <Accordion id="provider-permission-field-monday-boards-state-470add13c320" title="State" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `boards.state`

            State states lifecycle state of the board: active, archived, or deleted. It preserves the provider's current classification of this record.

            * **Enables:** separate board records by the exact provider-reported state value when describing their recorded state.
            * **Interpretation:** The provider supplies `state` per board record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, state is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-subscribers-b8f9d674b881" title="Subscribers" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `boards.subscribers`

            Subscribers records users subscribed to this board. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the board record to the provider-reported person or account represented by subscribers.
            * **Interpretation:** The provider supplies `subscribers` as identity or attribution context on each board record. In monday.com, subscribers is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-tags-1f56cbbde186" title="Tags" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `boards.tags`

            Tags records tags applied on this board. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** apply the provider-defined tags classifications to each board record.
            * **Interpretation:** The provider returns `tags` as a list on `Board`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-tags-color-0a2cc6093f73" title="Color" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `boards.tags.color`

            Color records tag color. It preserves the provider's visual treatment for the represented object.

            * **Enables:** reproduce or compare the provider-supplied color for the represented design or board object.
            * **Interpretation:** The provider supplies `color` in its own color, opacity, stroke, emoji, or style vocabulary for the represented object.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-tags-id-4523ec4ee471" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.tags.id`

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

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

          <Accordion id="provider-permission-field-monday-boards-tags-name-dd54c7f71019" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.tags.name`

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

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

          <Accordion id="provider-permission-field-monday-boards-top-group-84d041595007" title="Top Group" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `boards.top_group`

            Top Group captures the top group on this board. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each board record with the specific provider container named by top group.
            * **Interpretation:** The provider returns `top_group` as a nested object or reference on `Board`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-type-cbe37dce785f" title="Type" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `boards.type`

            Type states board object type (board, `sub_items_board`, document, `custom_object`). It preserves the provider's current classification of this record.

            * **Enables:** separate board records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per board record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-updated-at-8e826ab5228e" title="Updated At" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `boards.updated_at`

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

            * **Enables:** place board records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated_at` per board 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-monday-boards-url-4c9d208e7557" title="URL" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.url`

            URL records direct URL to the board. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-boards-views-8052f692fad4" title="Views" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `boards.views`

            Views records views configured on this board. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each board record with the specific provider container named by views.
            * **Interpretation:** The provider returns `views` as a list on `Board`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-views-id-86eb7a7b8e55" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.views.id`

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

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

          <Accordion id="provider-permission-field-monday-boards-views-name-d0340dd49d86" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.views.name`

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

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

          <Accordion id="provider-permission-field-monday-boards-views-type-9c63bc870aed" title="Type" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `boards.views.type`

            Type states view type. It preserves the provider's current classification of this record.

            * **Enables:** separate board records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per board view record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-workspace-a335c71c8829" title="Workspace" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `boards.workspace`

            Workspace captures the workspace this board belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each board record with the specific provider container named by workspace.
            * **Interpretation:** The provider returns `workspace` as a nested object or reference on `Board`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-workspace-id-051b61a4739d" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `boards.workspace.id`

            ID is the unique workspace identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match board 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 `Workspace`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-boards-workspace-name-c05e57101bc9" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `boards.workspace.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-monday-boards-workspace-id-57494581a788" title="Workspace ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `boards.workspace_id`

            Workspace ID identifies Workspace ID the board belongs to (scalar form). It is needed to resolve references that repeat the same provider identifier.

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

      <Accordion id="provider-permission-tap-monday-docs-3c4b98e3e2d0" title="Docs" icon="route" iconType="sharp-duotone-solid">
        Developer identifier: `docs`

        Docs contain all WorkDocs from Monday.com, including name, kind, creation timestamp, associated object, relative URL, and content blocks. Uses page-based pagination with `limit=50` per page. Requires docs:read scope.

        * **Enables:** inspect WorkDoc names, associated objects, links, and returned content blocks.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-docs-blocks-856008d7b55c" title="Blocks" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks`

            Blocks records ordered list of content blocks that make up the body of the doc. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-docs-blocks-content-8b61d8709ee6" title="Content" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.content`

            Content captures the raw content payload of the block. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret content according to the provider and Workspace configuration that produced each doc record.
            * **Interpretation:** Keys and value shapes within `content` 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-monday-docs-blocks-created-at-f4066404910e" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.created_at`

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

            * **Enables:** place doc records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per doc block 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-monday-docs-blocks-id-adb25f480dbd" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.id`

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

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

          <Accordion id="provider-permission-field-monday-docs-blocks-parent-block-id-6b4c899129e8" title="Parent Block ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.parent_block_id`

            Parent Block ID captures the parent block's unique identifier (null for first-level blocks). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-docs-blocks-position-8b9ead149c68" title="Position" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.position`

            Position captures the block's position in the document. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify doc records using the provider-defined position value.
            * **Interpretation:** The provider supplies `position` at doc block 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-monday-docs-blocks-type-949c8465c723" title="Type" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.type`

            Type captures the type of content block. It preserves the provider's current classification of this record.

            * **Enables:** separate doc records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per doc block record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-blocks-updated-at-24e5c18a8c4f" title="Updated At" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `docs.blocks.updated_at`

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

            * **Enables:** place doc records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated_at` per doc block 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-monday-docs-created-at-1c02902d1b37" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `docs.created_at`

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

            * **Enables:** place doc records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per doc 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-monday-docs-created-by-2df0970bdaf3" title="Created By" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.created_by`

            Created By captures the user who created the doc. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the doc record to the provider-reported person or account represented by created by.
            * **Interpretation:** The provider supplies `created_by` as identity or attribution context on each doc record. In monday.com, created by is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-created-by-id-51dd87a4a031" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `docs.created_by.id`

            ID is the unique user identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match doc 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 `UserRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-created-by-name-8d7e564e2bb1" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.created_by.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 ref record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each user ref record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-doc-folder-id-668506f66c93" title="Doc Folder ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `docs.doc_folder_id`

            Doc Folder ID is the ID of the folder containing the doc. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-docs-doc-kind-6e83f9bf8664" title="Doc Kind" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `docs.doc_kind`

            Doc Kind captures the kind/type of the WorkDoc. It preserves the provider's current classification of this record.

            * **Enables:** separate doc records by the exact provider-reported doc kind value when describing their recorded state.
            * **Interpretation:** The provider supplies `doc_kind` per doc record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, doc kind is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-id-4514129cdd6f" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `docs.id`

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

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

          <Accordion id="provider-permission-field-monday-docs-name-c83cab3157d9" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.name`

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

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

          <Accordion id="provider-permission-field-monday-docs-object-id-90fa9dc4dc8e" title="Object ID" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `docs.object_id`

            Object ID is the identifier of the associated Monday.com object this doc belongs to. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-docs-relative-url-733b8c83e0c4" title="Relative URL" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.relative_url`

            Relative URL records relative URL path to access the doc within Monday.com. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-docs-settings-eaa2710ab861" title="Settings" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `docs.settings`

            Settings states document-level settings, returned as escaped JSON. It preserves the provider's current classification of this record.

            * **Enables:** separate doc records by the exact provider-reported settings value when describing their recorded state.
            * **Interpretation:** The provider supplies `settings` per doc record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, settings is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-updated-at-03bc43fa786c" title="Updated At" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `docs.updated_at`

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

            * **Enables:** place doc records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated_at` per doc 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-monday-docs-url-5cc1405eb09f" title="URL" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.url`

            URL records absolute URL to access the doc. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-docs-workspace-8d1d0017a407" title="Workspace" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `docs.workspace`

            Workspace captures the workspace this doc belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each doc record with the specific provider container named by workspace.
            * **Interpretation:** The provider returns `workspace` as a nested object or reference on `Doc`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-workspace-id-60809b938ca6" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `docs.workspace.id`

            ID is the unique workspace identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match doc 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 `WorkspaceRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-workspace-name-3af473e903a4" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `docs.workspace.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 ref record.
            * **Interpretation:** The provider supplies `name` at workspace ref granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-monday-docs-workspace-id-69e2140939cd" title="Workspace ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `docs.workspace_id`

            Workspace ID is the ID of the workspace containing the doc. It is needed to resolve references that repeat the same provider identifier.

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

      <Accordion id="provider-permission-tap-monday-items-04549303903b" title="Items" icon="sitemap" iconType="sharp-duotone-solid">
        Developer identifier: `items`

        Items contain all items (tasks/rows) from Monday.com boards using cursor-based pagination via `items_page` per board, then `next_items_page` for subsequent pages. Includes column values, group membership, creator, board reference, parent item, assets, subscribers, and subitem references. Requires iterating over all boards first. Requires boards:read scope.

        * **Enables:** report board rows with their column values, group, parent, creator, and subscriber context.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-items-assets-3c1641344fa8" title="Assets" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `items.assets`

            Assets records assets/files attached to this item. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested assets records contained by each item record.
            * **Interpretation:** The provider returns `assets` as a list on `Item`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-assets-file-extension-ce63315fce6e" title="File Extension" icon="chart-pie" iconType="sharp-duotone-solid">
            Developer identifier: `items.assets.file_extension`

            File Extension records file extension of the asset. It preserves the configuration or technical value needed to explain how the provider object is defined.

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

          <Accordion id="provider-permission-field-monday-items-assets-id-d927811299bb" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.assets.id`

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

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

          <Accordion id="provider-permission-field-monday-items-assets-name-4484314dc0c3" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.assets.name`

            Name records asset file name. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-items-assets-url-278b2d0b7902" title="URL" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.assets.url`

            URL records public URL to the asset. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-items-board-e7b5888d8d43" title="Board" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.board`

            Board captures the board this item belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-items-board-id-75f043fda7d3" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.board.id`

            ID identifies board identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match 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 `BoardRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-board-name-1e70c7243651" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.board.name`

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

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

          <Accordion id="provider-permission-field-monday-items-board-id-5caabe92531d" title="Board ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.board_id`

            Board ID is the ID of the board this item belongs to. Derived from parent boards traversal. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-items-column-values-47167a6c391d" title="Column Values" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.column_values`

            Column Values records array of column values for this item. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the declared column values layout or dimensional scope of each item record.
            * **Interpretation:** The provider returns `column_values` as a list on `Item`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-column-values-id-80d568854fbb" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.column_values.id`

            ID identifies column identifier. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-monday-items-column-values-text-458731894e0d" title="Text" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `items.column_values.text`

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

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

          <Accordion id="provider-permission-field-monday-items-column-values-type-25fbad0db323" title="Type" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `items.column_values.type`

            Type states column type. It preserves the provider's current classification of this record.

            * **Enables:** separate item records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per column value record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-column-values-value-d6639200bb6b" title="Value" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `items.column_values.value`

            Value records raw JSON-encoded 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-monday-items-created-at-db903b59dbd5" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `items.created_at`

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

            * **Enables:** place item records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per item 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-monday-items-creator-8ddd65ee1ec5" title="Creator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `items.creator`

            Creator captures the user who created this item. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the item record to the provider-reported actor represented by creator.
            * **Interpretation:** The provider supplies `creator` as identity or attribution context on each item record. In monday.com, creator is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-creator-email-a1d46ce2d6ef" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `items.creator.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 record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each user record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-creator-id-dbcb847e5fd1" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.creator.id`

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

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

          <Accordion id="provider-permission-field-monday-items-creator-name-47bbf95e7f1d" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.creator.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 record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each user record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-creator-id-7ba29de48013" title="Creator ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `items.creator_id`

            Creator ID is the ID of the user who created the item. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-items-email-4cd25aa86215" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `items.email`

            Email records item email address for the board's item email integration. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the item record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each item record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-group-bff56d7339df" title="Group" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `items.group`

            Group records group the item belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-items-group-id-3debc4870cfb" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.group.id`

            ID identifies group identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match 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 `GroupRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-group-title-777b9d30d104" title="Title" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `items.group.title`

            Title records group title. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-items-id-78a2f97bed78" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.id`

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

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

          <Accordion id="provider-permission-field-monday-items-name-fb1ea8e63d3d" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.name`

            Name records item name/title. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-items-parent-item-7402fe937f30" title="Parent Item" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `items.parent_item`

            Parent Item captures the parent item, when this item is a subitem. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by parent item on each item record.
            * **Interpretation:** The provider returns `parent_item` as a nested object or reference on `Item`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-parent-item-id-8601ea752d31" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.parent_item.id`

            ID identifies item identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match 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 `ItemRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-parent-item-name-48e045ee8894" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.parent_item.name`

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

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

          <Accordion id="provider-permission-field-monday-items-relative-link-2d4e808a24aa" title="Relative Link" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.relative_link`

            Relative Link records relative link to the item. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-items-state-dd0f5dc3fa86" title="State" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `items.state`

            State states item state (active, archived, deleted). It preserves the provider's current classification of this record.

            * **Enables:** separate item records by the exact provider-reported state value when describing their recorded state.
            * **Interpretation:** The provider supplies `state` per item record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, state is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-subitems-e2af7efb7e11" title="Subitems" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `items.subitems`

            Subitems records array of subitem references. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-items-subitems-id-42008b635b84" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `items.subitems.id`

            ID identifies subitem identifier. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-monday-items-subitems-name-be39b7e17825" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.subitems.name`

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

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

          <Accordion id="provider-permission-field-monday-items-subscribers-802022784319" title="Subscribers" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `items.subscribers`

            Subscribers records users subscribed to this item. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the item record to the provider-reported person or account represented by subscribers.
            * **Interpretation:** The provider supplies `subscribers` as identity or attribution context on each item record. In monday.com, subscribers is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-items-updated-at-ebb83cb6d90a" title="Updated At" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `items.updated_at`

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

            * **Enables:** place item records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated_at` per item 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-monday-items-url-4fcb70054e29" title="URL" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `items.url`

            URL records direct URL to the item. It retains the exact provider location for the referenced resource.

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

      <Accordion id="provider-permission-tap-monday-tags-4505ee7847fa" title="Tags" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `tags`

        Tags contain all tags from Monday.com, including name and color. No pagination documented; returns all tags in a single response. Requires tags:read scope.

        * **Enables:** apply monday.com tag names and colors to records that reference them.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-tags-color-9d99c2d52330" title="Color" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `tags.color`

            Color records color associated with the tag. It preserves the provider's visual treatment for the represented object.

            * **Enables:** reproduce or compare the provider-supplied color for the represented design or board object.
            * **Interpretation:** The provider supplies `color` in its own color, opacity, stroke, emoji, or style vocabulary for the represented object.
          </Accordion>

          <Accordion id="provider-permission-field-monday-tags-id-a12c1d16d117" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `tags.id`

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

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

          <Accordion id="provider-permission-field-monday-tags-name-161df77bbafc" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `tags.name`

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

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

      <Accordion id="provider-permission-tap-monday-teams-827aee3f529e" title="Teams" icon="address-book" iconType="sharp-duotone-solid">
        Developer identifier: `teams`

        Teams contain all teams from Monday.com, including team name, picture URL, and member user references. No pagination documented; returns all teams in a single response. Requires teams:read scope.

        * **Enables:** map monday.com teams to their member accounts.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-teams-id-8a44768e1633" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `teams.id`

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

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

          <Accordion id="provider-permission-field-monday-teams-name-c0b45114b0d2" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `teams.name`

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

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

          <Accordion id="provider-permission-field-monday-teams-picture-url-50fa037af6f8" title="Picture URL" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `teams.picture_url`

            Picture URL records URL of the team's profile picture. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-teams-users-277deca99d0c" title="Users" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `teams.users`

            Users records list of users who are members of this team. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the team record to the provider-reported actor represented by users.
            * **Interpretation:** The provider supplies `users` as identity or attribution context on each team record. In monday.com, users is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-teams-users-email-0848ff02d4ba" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `teams.users.email`

            Email records email address of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the team user record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each team user record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-teams-users-id-b43e7b60f2ba" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `teams.users.id`

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

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

          <Accordion id="provider-permission-field-monday-teams-users-name-6e210a0f18d8" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `teams.users.name`

            Name records full display name of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the team user record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each team user record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-monday-updates-83cc7425f676" title="Updates" icon="comments" iconType="sharp-duotone-solid">
        Developer identifier: `updates`

        Updates contain all updates (comments and activity posts) on Monday.com items, including body text, creator, timestamps, and nested replies. Uses page-based pagination with `limit=100` per page. Requires updates:read scope.

        * **Enables:** inspect item update and reply text with creator and timestamp context.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-updates-assets-033dd300f57e" title="Assets" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `updates.assets`

            Assets records assets/files attached to the update. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-updates-assets-file-extension-7c37a97d6e85" title="File Extension" icon="chart-pie" iconType="sharp-duotone-solid">
            Developer identifier: `updates.assets.file_extension`

            File Extension records file extension of the asset. It preserves the configuration or technical value needed to explain how the provider object is defined.

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

          <Accordion id="provider-permission-field-monday-updates-assets-id-bc0bde92c5cb" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.assets.id`

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

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

          <Accordion id="provider-permission-field-monday-updates-assets-name-7bd648b7cf1b" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.assets.name`

            Name records asset file name. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-updates-assets-url-16a7b878f02e" title="URL" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.assets.url`

            URL records public URL to the asset. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-monday-updates-body-29cc2741b96a" title="Body" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.body`

            Body records HTML body of the update. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-updates-created-at-21a71245c052" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `updates.created_at`

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

            * **Enables:** place update records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per update 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-monday-updates-creator-74922247172c" title="Creator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `updates.creator`

            Creator carries the source person or account value named Creator for each update row. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the update record to the provider-reported actor represented by creator.
            * **Interpretation:** The provider supplies `creator` as identity or attribution context on each update record. In monday.com, creator is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-creator-email-0c680be92e2c" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `updates.creator.email`

            Email records email address of the creator. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the update creator record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each update creator record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-creator-id-ad70b9b17c18" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.creator.id`

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

            * **Enables:** match update 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 `UpdateCreator`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-creator-name-0c30acb7f293" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.creator.name`

            Name records display name of the creator. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the update creator record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each update creator record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-creator-id-0a170de4034a" title="Creator ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `updates.creator_id`

            Creator ID is the ID of the user who created the update. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-updates-edited-at-ba703ed38fe3" title="Edited At" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `updates.edited_at`

            Edited At records ISO 8601 timestamp when the update was last edited. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place update records on a timeline by edited at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `edited_at` per update 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-monday-updates-id-8a9708ba4983" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.id`

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

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

          <Accordion id="provider-permission-field-monday-updates-item-8e30964fae89" title="Item" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.item`

            Item captures the item this update belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-updates-item-id-482cebdfb7e9" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.item.id`

            ID identifies item identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match update 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 `ItemRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-item-id-a49b6b639cea" title="Item ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.item_id`

            Item ID is the ID of the item this update belongs to. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-updates-replies-91b092d7eb11" title="Replies" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies`

            Replies records array of replies to this update. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-monday-updates-replies-body-61f00c4d6a42" title="Body" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.body`

            Body records HTML body of the reply. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-updates-replies-created-at-09ff6089e3e9" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.created_at`

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

            * **Enables:** place update records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per reply 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-monday-updates-replies-creator-5c17cd654ce8" title="Creator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.creator`

            Creator carries the source person or account value named Creator for each reply row. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the reply record to the provider-reported actor represented by creator.
            * **Interpretation:** The provider supplies `creator` as identity or attribution context on each reply record. In monday.com, creator is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-replies-creator-id-c6497282c024" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.creator.id`

            ID is the unique identifier of the reply creator user. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match update 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 `ReplyCreator`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-replies-creator-name-158a2b7b3ef9" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.creator.name`

            Name records display name of the reply creator. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the reply creator record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each reply creator record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-updates-replies-creator-id-b33183bc9087" title="Creator ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.creator_id`

            Creator ID is the ID of the user who created the reply. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-updates-replies-id-6203ea0b6cbf" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.id`

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

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

          <Accordion id="provider-permission-field-monday-updates-replies-text-body-411858867dca" title="Text Body" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.text_body`

            Text Body records plain text body of the reply, stripped of HTML. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-updates-replies-updated-at-5634e5faf811" title="Updated At" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `updates.replies.updated_at`

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

            * **Enables:** place update records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated_at` per reply 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-monday-updates-text-body-cac40c23a363" title="Text Body" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `updates.text_body`

            Text Body records plain text body of the update, stripped of HTML. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-updates-updated-at-0832e0a6350d" title="Updated At" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `updates.updated_at`

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

            * **Enables:** place update records on a timeline by updated at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated_at` per update 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-monday-users-e5e236484c3a" title="Users" icon="user-tie" iconType="sharp-duotone-solid">
        Developer identifier: `users`

        Users contain all users from Monday.com, including profile details, admin/guest status, timezone, and team memberships. Uses page-based pagination with `limit=500` per page. Requires users:read scope.

        * **Enables:** resolve monday.com accounts, guest or administrator flags, time zones, and team memberships.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-users-account-0d266a40488a" title="Account" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.account`

            Account captures the Monday.com account this user belongs to. 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 user record.
            * **Interpretation:** The provider returns `account` as a nested object or reference on `User`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-account-id-12a0622a24e7" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `users.account.id`

            ID is the unique account identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match user 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 `AccountRef`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-account-name-b5cac5014712" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.account.name`

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

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

          <Accordion id="provider-permission-field-monday-users-account-slug-089ee9f850dd" title="Slug" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.account.slug`

            Slug identifies account slug (subdomain). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-monday-users-account-tier-d9ef45f53a87" title="Tier" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `users.account.tier`

            Tier states account subscription tier. It preserves the provider's current classification of this record.

            * **Enables:** separate user records by the exact provider-reported tier value when describing their recorded state.
            * **Interpretation:** The provider supplies `tier` per account ref record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, tier is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-country-code-fecdd3dcc260" title="Country Code" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `users.country_code`

            Country Code records user country code. It preserves the configuration or technical value needed to explain how the provider object is defined.

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

          <Accordion id="provider-permission-field-monday-users-created-at-494bc8afbaa1" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `users.created_at`

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

            * **Enables:** place user records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per 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-monday-users-current-language-238f586aa0ea" title="Current Language" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `users.current_language`

            Current Language records user's current language setting. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

          <Accordion id="provider-permission-field-monday-users-email-712ef96351a8" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.email`

            Email records user email address. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each user record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-enabled-3c2c270c14e8" title="Enabled" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `users.enabled`

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

            * **Enables:** select user records for which the provider reports enabled as true or false.
            * **Interpretation:** The provider supplies `enabled` as a boolean per user record; false and missing are distinct when the field is optional. In monday.com, enabled is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-id-5c30f35717b1" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `users.id`

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

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

          <Accordion id="provider-permission-field-monday-users-is-admin-748c8607c041" title="Is Admin" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.is_admin`

            Is Admin indicates whether the user has account admin privileges. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported is admin attached to each user record.
            * **Interpretation:** The provider supplies `is_admin` at user granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In monday.com, is admin is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-is-guest-f67b5ef63540" title="Is Guest" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.is_guest`

            Is Guest indicates whether the user is a guest (external collaborator). It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported is guest attached to each user record.
            * **Interpretation:** The provider supplies `is_guest` at user granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In monday.com, is guest is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-is-pending-b19030583866" title="Is Pending" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `users.is_pending`

            Is Pending indicates whether the user invitation is still pending. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports is pending as true or false.
            * **Interpretation:** The provider supplies `is_pending` as a boolean per user record; false and missing are distinct when the field is optional. In monday.com, is pending is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-is-view-only-98638f9482b6" title="Is View Only" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.is_view_only`

            Is View Only indicates whether the user has view-only access. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports is view only as true or false.
            * **Interpretation:** The provider supplies `is_view_only` as a boolean per user record; false and missing are distinct when the field is optional. In monday.com, is view only is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-join-date-56f9bf136155" title="Join Date" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `users.join_date`

            Join Date records the date the user joined the account. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place user records on a timeline by join date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `join_date` per 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-monday-users-location-b6f0bacea748" title="Location" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `users.location`

            Location records user location. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

          <Accordion id="provider-permission-field-monday-users-mobile-phone-b226a66370d5" title="Mobile Phone" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.mobile_phone`

            Mobile Phone records user mobile phone number. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user record to the provider-reported person or account represented by mobile phone.
            * **Interpretation:** The provider supplies `mobile_phone` as identity or attribution context on each user record. In monday.com, mobile phone is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-name-be0306c3f31f" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.name`

            Name records user display name. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each user record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-phone-2d3e62497a3f" title="Phone" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.phone`

            Phone records user phone number. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user record to the provider-reported person or account represented by phone.
            * **Interpretation:** The provider supplies `phone` as identity or attribution context on each user record. In monday.com, phone is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-teams-1b63835bf381" title="Teams" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.teams`

            Teams records list of teams the user belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each user record with the specific provider container named by teams.
            * **Interpretation:** The provider returns `teams` as a list on `User`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-teams-id-d7ad3dff4298" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `users.teams.id`

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

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

          <Accordion id="provider-permission-field-monday-users-teams-name-2008168164f7" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.teams.name`

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

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

          <Accordion id="provider-permission-field-monday-users-time-zone-identifier-3d9de18c633b" title="Time Zone Identifier" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.time_zone_identifier`

            Time Zone Identifier identifies IANA timezone identifier for 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 time zone identifier, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `time_zone_identifier` as a record-level identifier on `User`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-title-1b000b2926d6" title="Title" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.title`

            Title records user job title. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user record to the provider-reported person or account represented by title.
            * **Interpretation:** The provider supplies `title` as identity or attribution context on each user record. In monday.com, title is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-users-url-54c583362a76" title="URL" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.url`

            URL records URL to the user profile. It retains the exact provider location for the referenced resource.

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

      <Accordion id="provider-permission-tap-monday-workspaces-6449d3c4bd6c" title="Workspaces" icon="address-book" iconType="sharp-duotone-solid">
        Developer identifier: `workspaces`

        Workspaces contain all workspaces from Monday.com, including name, kind, and description. Uses page-based pagination with `limit=50` per page. Requires workspaces:read scope.

        * **Enables:** organize boards by the monday.com workspaces that contain them.
        * **Scope:** Reads the declared collection through the declared GraphQL operation as a full snapshot. Results are limited to objects returned under the tap's stated monday.com read scope.

        <AccordionGroup>
          <Accordion id="provider-permission-field-monday-workspaces-created-at-24052958ab78" title="Created At" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.created_at`

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

            * **Enables:** place workspace records on a timeline by created at and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created_at` per workspace 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-monday-workspaces-description-80bb4bfb5647" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.description`

            Description records optional description of the workspace. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-monday-workspaces-id-4e8931cbdf7f" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.id`

            ID is the unique workspace identifier. 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-monday-workspaces-is-default-workspace-c61930c6bec6" title="Is Default Workspace" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.is_default_workspace`

            Is Default Workspace indicates whether this is the default workspace of the product or account. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select workspace records for which the provider reports is default workspace as true or false.
            * **Interpretation:** The provider supplies `is_default_workspace` as a boolean per workspace record; false and missing are distinct when the field is optional. In monday.com, is default workspace is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-kind-da43db4967d5" title="Kind" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.kind`

            Kind captures the kind of workspace: open or closed. It preserves the provider's current classification of this record.

            * **Enables:** separate workspace records by the exact provider-reported kind value when describing their recorded state.
            * **Interpretation:** The provider supplies `kind` per workspace record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, kind is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-name-7f7f3b27cb12" title="Name" icon="shield-check" 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-monday-workspaces-owners-subscribers-ec708a150e81" title="Owners Subscribers" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.owners_subscribers`

            Owners Subscribers records users who own the workspace. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the workspace record to the provider-reported actor represented by owners subscribers.
            * **Interpretation:** The provider supplies `owners_subscribers` as identity or attribution context on each workspace record. In monday.com, owners subscribers is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-owners-subscribers-email-d3273abcf700" title="Email" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.owners_subscribers.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 record to the provider-reported person or account represented by email.
            * **Interpretation:** The provider supplies `email` as identity or attribution context on each user record. In monday.com, email is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-owners-subscribers-id-af37f9372d37" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.owners_subscribers.id`

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

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

          <Accordion id="provider-permission-field-monday-workspaces-owners-subscribers-name-c7336fede34f" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.owners_subscribers.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 record to the provider-reported person or account represented by name.
            * **Interpretation:** The provider supplies `name` as identity or attribution context on each user record. In monday.com, name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-state-0494a63a31a2" title="State" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.state`

            State states Workspace state (all, active, archived, deleted). It preserves the provider's current classification of this record.

            * **Enables:** separate workspace records by the exact provider-reported state value when describing their recorded state.
            * **Interpretation:** The provider supplies `state` per workspace record using its own state vocabulary; unknown and missing values must remain distinct. In monday.com, state is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-teams-subscribers-9c2510380ccd" title="Teams Subscribers" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.teams_subscribers`

            Teams Subscribers records teams subscribed to the workspace. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each workspace record with the specific provider container named by teams subscribers.
            * **Interpretation:** The provider returns `teams_subscribers` as a list on `Workspace`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-monday-workspaces-teams-subscribers-id-10267c11d035" title="ID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.teams_subscribers.id`

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

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

          <Accordion id="provider-permission-field-monday-workspaces-teams-subscribers-name-a1e13ae52e8d" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.teams_subscribers.name`

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

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

          <Accordion id="provider-permission-field-monday-workspaces-users-subscribers-11b105751be9" title="Users Subscribers" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `workspaces.users_subscribers`

            Users Subscribers records users subscribed to the workspace. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the workspace record to the provider-reported actor represented by users subscribers.
            * **Interpretation:** The provider supplies `users_subscribers` as identity or attribution context on each workspace record. In monday.com, users subscribers is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    ### Personal API Token

    | Error                               | Meaning                              | Solution                                                                |
    | ----------------------------------- | ------------------------------------ | ----------------------------------------------------------------------- |
    | `Not Authenticated`                 | Invalid or revoked token             | Re-copy the token from **API token**, or regenerate it                  |
    | `Unauthorized`                      | Token lacks access to the resource   | Use an administrator token for full-account access                      |
    | Missing users, teams, or workspaces | Member-level token                   | Reconnect with an administrator token                                   |
    | Empty activity logs                 | Non-Enterprise plan                  | Activity logs require an Enterprise plan                                |
    | `ComplexityException`               | Query exceeded the complexity budget | Parable batches and retries automatically; retry after the reset window |

    #### Common Issues

    #### Some boards are missing

    Token access is limited to boards the user can see. Reconnect with an administrator account for full access.

    #### Query complexity exceeded

    Monday.com meters queries by complexity. Parable splits large queries and backs off automatically; large initial syncs take longer.

    **[Monday.com API](https://developer.monday.com/api-reference/)** — Official GraphQL API documentation

    **[GraphQL Playground](https://monday.com/developers/v2/try-it-yourself)** — Test queries interactively

    ### OAuth 2.0 Authorization Code (3LO)

    | Error                        | Meaning                                    | Solution                                                                                                                                             |
    | ---------------------------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
    | `401 Unauthorized`           | Invalid client credentials or access token | Verify the Client ID and Secret, or re-authorize with OAuth                                                                                          |
    | `403 Forbidden`              | Missing OAuth scope                        | Enable the required scope on the app and re-authorize                                                                                                |
    | Authorization redirect fails | Redirect URI mismatch                      | Copy the redirect URI from Parable (must include your workspace subdomain, e.g. `{tenant-name}.parable.work`) and add it exactly under Redirect URLs |
    | Re-authorization required    | Access token revoked or app uninstalled    | Click **Re-authorize with OAuth** on the connection page                                                                                             |
    | Empty activity logs          | Non-Enterprise plan                        | Activity logs require an Enterprise plan                                                                                                             |
    | `ComplexityException`        | Query exceeded the complexity budget       | Parable batches and retries automatically; retry after the reset window                                                                              |

    **[Monday.com OAuth guide](https://developer.monday.com/apps/docs/oauth)** — Official OAuth 2.0 documentation

    **[Monday.com API](https://developer.monday.com/api-reference/)** — GraphQL API reference
  </Tab>
</Tabs>