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

# GitLab

> Sync projects, issues, merge requests, and commits from GitLab

Sync projects, issues, merge requests, and commits from GitLab.

<Tabs>
  <Tab title="Overview">
    Connect Parable to GitLab for comprehensive DevOps and repository data.

    #### Code & MRs

    Projects, merge requests, commits

    #### Issues & Planning

    Issues, milestones, labels

    ## Data streams

    This Provider Plugin defines 13 data streams.

    | Stream                | Description                                           | Sync        |
    | --------------------- | ----------------------------------------------------- | ----------- |
    | `projects`            | GitLab projects the authenticated user is a member of | incremental |
    | `groups`              | GitLab groups                                         | full        |
    | `group_members`       | Members of a group (including inherited members)      | full        |
    | `issues`              | Project issues                                        | incremental |
    | `merge_requests`      | Project merge requests                                | incremental |
    | `merge_request_notes` | Notes (comments) on merge requests                    | incremental |
    | `project_commits`     | Project repository commits                            | incremental |
    | `branches`            | Project repository branches                           | full        |
    | `project_members`     | Members of a project (including inherited members)    | full        |
    | `pipelines`           | Project CI/CD pipelines                               | incremental |
    | `repos`               | Project repository file tree                          | full        |
    | `branch_commits`      | Repository commits for a specific branch              | incremental |
    | `commit_diffs`        | Diff details for a specific commit                    | full        |
  </Tab>

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

    #### What You'll Need

    | Credential   | What it is                                          |
    | ------------ | --------------------------------------------------- |
    | **Token**    | Personal access token with API scope                |
    | **Base URL** | `https://gitlab.com` or your self-hosted GitLab URL |

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

    * **Owner** or **Maintainer** role in the group/project
    * For group-level access, group owner permissions

    #### Step 1: Access User Settings

    1. Log in to GitLab (gitlab.com or your instance)
    2. Click your avatar → **Preferences**
    3. Navigate to **Access Tokens** in the sidebar

    #### Step 2: Create Personal Access Token

    1. Click **Add new token**
    2. Fill in:

    | Field           | Value                  |
    | --------------- | ---------------------- |
    | Token name      | `Parable Integration`  |
    | Expiration date | 1 year (or per policy) |

    #### Step 3: Select Scopes

    Enable these scopes:

    | Scope             | Purpose                     |
    | ----------------- | --------------------------- |
    | `api`             | Full API access             |
    | `read_api`        | Read-only API (alternative) |
    | `read_user`       | Read user information       |
    | `read_repository` | Read repository contents    |

    > **Tip:** For read-only integration, use `read_api` instead of `api`.

    #### Step 4: Create and Copy Token

    1. Click **Create personal access token**
    2. Copy the token immediately

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

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

    1. **Token** and **GitLab URL**: Paste your personal access token and your GitLab instance base URL.
    2. Click **Save & test connection**.

    ```bash Test Authentication theme={null}
    curl -H "PRIVATE-TOKEN: YOUR_TOKEN" \
      "https://gitlab.com/api/v4/user"
    ```

    ```bash List Projects theme={null}
    curl -H "PRIVATE-TOKEN: YOUR_TOKEN" \
      "https://gitlab.com/api/v4/projects?membership=true&per_page=5"
    ```

    > **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:** GitLab enforces rate limits of **varies; typically 2,000 requests/minute for authenticated users**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
  </Tab>

  <Tab title="Permissions">
    <AccordionGroup>
      <Accordion id="provider-permission-tap-gitlab-branch-commits-3c40cc4483d4" title="Branch Commits" icon="code-commit" iconType="sharp-duotone-solid">
        Developer identifier: `branch_commits`

        Branch Commits covers repository commits for a specific branch.

        * **Enables:** trace each returned revision to its repository or project, author and committer identities, message, and provider-reported commit times.
        * **Scope:** Repository commits for a specific branch; the connector reads `/api/v4/projects/{project_id}/repository/commits` as an event stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-branch-commits-author-email-2f70b1e4f4db" title="Author Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.author_email`

            Author Email records email address of the commit author as recorded in Git. It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

            * **Enables:** attribute the Branch Commits row to the returned person or account and match the exact `author_email` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-author-name-59d3919df149" title="Author Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.author_name`

            Author Name records display name of the commit author as recorded in Git. It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

            * **Enables:** attribute the Branch Commits row to the returned person or account and match the exact `author_name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-authored-date-674a78c7301c" title="Authored Date" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.authored_date`

            Authored Date records timestamp when the commit was originally authored (may differ from committed date for rebased/cherry-picked commits). It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-committed-date-5df1e1dbc6ff" title="Committed Date" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.committed_date`

            Committed Date records timestamp when the commit was applied to the repository. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-committer-email-2b7df471db90" title="Committer Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.committer_email`

            Committer Email records email address of the committer as recorded in Git. It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

            * **Enables:** attribute the Branch Commits row to the returned person or account and match the exact `committer_email` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-committer-name-9663bde0462b" title="Committer Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.committer_name`

            Committer Name records display name of the person who committed the change (may differ from author for applied patches). It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

            * **Enables:** attribute the Branch Commits row to the returned person or account and match the exact `committer_name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-created-at-10dd2933b8b1" title="Created At" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-extended-trailers-0c4cdcd892be" title="Extended Trailers" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.extended_trailers`

            Extended Trailers records extended Git trailers supporting multiple values per key. It is needed to preserve the exact GitLab configuration or execution metadata attached to this GitLab Project Commit record.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-id-074ee8b9cf4e" title="ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.id`

            ID records full SHA-1 hash of the commit, serving as the primary key. It is needed to distinguish repeated deliveries of the same Branch Commits row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-0dbd9a14fc70" title="Last Pipeline" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline`

            Last Pipeline records summary of the last pipeline run for this commit, if any. It is needed to preserve the nested last pipeline relationship or details on the parent GitLab Project Commit record.

            * **Enables:** expand `last_pipeline` to connect the containing GitLab Project Commit row to its returned last pipeline entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is one nested object per containing GitLab Project Commit object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-created-at-bff04f0ff22d" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-id-d1cfb4fdb4e7" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.id`

            ID records unique numeric ID of the pipeline. It is needed to refer to the same commit last pipeline across records without relying on display text.

            * **Enables:** match `id` to commit last pipeline references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-iid-41a8c919cf32" title="Iid" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.iid`

            Iid records project-scoped internal ID of the pipeline. It is needed to refer to the same iid across records without relying on display text.

            * **Enables:** match `iid` to iid references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-ref-06409cee4952" title="Ref" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.ref`

            Ref records branch or tag name the pipeline ran against. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-sha-6ca53bbc59f8" title="Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.sha`

            Sha records full SHA of the commit the pipeline ran on. It is needed to refer to the same commit last pipeline across records without relying on display text.

            * **Enables:** match `sha` to commit last pipeline references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-source-4b27e3bccf28" title="Source" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.source`

            Source records what triggered the pipeline (e.g., push, web, `merge_request_event`, api, schedule). It is needed to distinguish Branch Commits rows by the exact GitLab-returned source value.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-status-5b4aa8bd3a42" title="Status" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.status`

            Status records current status of the pipeline (e.g., success, failed, pending, running, canceled). It is needed to distinguish Branch Commits rows by the exact GitLab-returned status value.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-updated-at-8f96deeb03c9" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.updated_at`

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

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-last-pipeline-web-url-fe448d9537f7" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.last_pipeline.web_url`

            Web URL records URL to view the pipeline in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-message-dd561071e4a3" title="Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.message`

            Message records full commit message including title and body. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `message` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-parent-ids-c1066487dbe2" title="Parent IDs" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.parent_ids`

            Parent IDs records SHA hashes of parent commits. Multiple entries indicate a merge commit. It is needed to preserve the nested parent i ds relationship or details on the parent GitLab Project Commit record.

            * **Enables:** expand `parent_ids` to connect the containing GitLab Project Commit row to its returned parent i ds entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is one returned collection per containing GitLab Project Commit object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-project-id-6cfd4c0f5d62" title="Project ID" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.project_id`

            Project ID records parent project's numeric id, injected by the ingestion service from the branches tap's parentContextFields. Absent from the GitLab commits API response body itself. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-short-id-d9d07a62dc81" title="Short ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.short_id`

            Short ID records abbreviated SHA hash of the commit for human-readable display. It is needed to refer to the same short across records without relying on display text.

            * **Enables:** match `short_id` to short references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-stats-6ececa96d2fa" title="Stats" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.stats`

            Stats records line-level change statistics for the commit (present when `with_stats`=true). It is needed to preserve the nested stats relationship or details on the parent GitLab Project Commit record.

            * **Enables:** expand `stats` to connect the containing GitLab Project Commit row to its returned stats entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is one nested object per containing GitLab Project Commit object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-stats-additions-28d5d83e7a2c" title="Additions" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.stats.additions`

            Additions records number of lines added in this commit. It is needed to measure the GitLab-reported number of lines added in this commit at one GitLab Commit Stats record per row.

            * **Enables:** measure and compare the GitLab-reported number of lines added in this commit in `additions` at one GitLab Commit Stats record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Stats object returned for Branch Commits; it is a GitLab-reported count at one GitLab Commit Stats record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-stats-deletions-8ce07960b9d6" title="Deletions" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.stats.deletions`

            Deletions records number of lines deleted in this commit. It is needed to measure the GitLab-reported number of lines deleted in this commit at one GitLab Commit Stats record per row.

            * **Enables:** measure and compare the GitLab-reported number of lines deleted in this commit in `deletions` at one GitLab Commit Stats record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Stats object returned for Branch Commits; it is a GitLab-reported count at one GitLab Commit Stats record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-stats-total-da92f184ef9d" title="Total" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.stats.total`

            Total records total number of lines changed (additions + deletions). It is needed to measure the GitLab-reported number of lines changed (additions + deletions) at one GitLab Commit Stats record per row.

            * **Enables:** measure and compare the GitLab-reported number of lines changed (additions + deletions) in `total` at one GitLab Commit Stats record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Stats object returned for Branch Commits; it is a GitLab-reported count at one GitLab Commit Stats record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-status-ebb612679da6" title="Status" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.status`

            Status records status of the latest pipeline associated with this commit, if any. It is needed to distinguish Branch Commits rows by the exact GitLab-returned status value.

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

          <Accordion id="provider-permission-field-gitlab-branch-commits-title-c9f7ba79fc3f" title="Title" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.title`

            Title records first line of the commit message, typically a summary of the change. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `title` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-trailers-070db4038e1b" title="Trailers" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.trailers`

            Trailers records key-value pairs parsed from Git trailers in the commit message (e.g., Signed-off-by, Co-authored-by). It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `trailers` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is commit message at one GitLab Project Commit record per row; the schema uses the `Generic.JSON` scalar; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branch-commits-web-url-d9c05cdfe141" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `branch_commits.web_url`

            Web URL records URL to view the commit in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

      <Accordion id="provider-permission-tap-gitlab-branches-7fc46ae0ef1c" title="Branches" icon="code-branch" iconType="sharp-duotone-solid">
        Developer identifier: `branches`

        Branches covers project repository branches.

        * **Enables:** inventory returned branches and connect each branch name to its head revision and protection details.
        * **Scope:** Project repository branches; the connector reads `/api/v4/projects/{id}/repository/branches` as a snapshot stream in full mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-branches-composite-id-ea41b1fb24d6" title="Composite ID" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branches._composite_id`

            Composite ID records synthetic primary key formed by joining `project_id` and branch name with ':' for global uniqueness. Injected by the ingestion service. It is needed to refer to the same composite across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-branches-can-push-7d3c3513c7f2" title="Can Push" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `branches.can_push`

            Can Push records whether the current authenticated user can push to this branch. It is needed to distinguish Branches rows by the exact GitLab-returned can push value.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-775ecd7a2d4b" title="Commit" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit`

            Commit records the latest commit on this branch. It is needed to preserve the nested commit relationship or details on the parent GitLab Branch record.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-author-email-f45c7a2167cb" title="Author Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.author_email`

            Author Email records email address of the commit author. It is needed to attribute this Branches row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-author-name-a428625d7ba4" title="Author Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.author_name`

            Author Name records name of the commit author. It is needed to attribute this Branches row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-authored-date-7f198f64eccc" title="Authored Date" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.authored_date`

            Authored Date records timestamp when the commit was authored. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-committed-date-4c329c4b5250" title="Committed Date" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.committed_date`

            Committed Date records timestamp when the commit was committed. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-committer-email-05934d4bcfbc" title="Committer Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.committer_email`

            Committer Email records email address of the committer. It is needed to attribute this Branches row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-committer-name-91c8fe0ee5db" title="Committer Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.committer_name`

            Committer Name records name of the committer. It is needed to compare the returned committer name for individual Branches rows and select rows with a specific `committer_name` value.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-created-at-832e89444fc2" title="Created At" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-extended-trailers-7082b09fc147" title="Extended Trailers" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.extended_trailers`

            Extended Trailers records extended git trailer key-value pairs parsed from the commit message, supporting multiple values per key. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `extended_trailers` and attribute it to the same record's repository or project, branch name, revision, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; the schema uses the `Generic.JSON` scalar; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-commit-id-b23b892ba156" title="ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.id`

            ID records full SHA hash of the commit. It is needed to refer to the same branch commit across records without relying on display text.

            * **Enables:** match `id` to branch commit references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-commit-message-653c1cd73189" title="Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.message`

            Message records full commit message including body. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `message` and attribute it to the same record's repository or project, branch name, revision, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-commit-parent-ids-3f21f3c05d6d" title="Parent IDs" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.parent_ids`

            Parent IDs records list of parent commit SHA hashes. It is needed to preserve the nested parent i ds relationship or details on the parent GitLab Branch Commit record.

            * **Enables:** expand `parent_ids` to connect the containing GitLab Branch Commit row to its returned parent i ds entries.
            * **Interpretation:** GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is one returned collection per containing GitLab Branch Commit object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-commit-short-id-4c9bdf015370" title="Short ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.short_id`

            Short ID records abbreviated SHA hash of the commit. It is needed to refer to the same short across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-branches-commit-title-f82a39c7afdd" title="Title" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.title`

            Title records first line of the commit message (subject). It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `title` and attribute it to the same record's repository or project, branch name, revision, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-commit-trailers-48f9a2556d8b" title="Trailers" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.trailers`

            Trailers records git trailer key-value pairs parsed from the commit message. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `trailers` and attribute it to the same record's repository or project, branch name, revision, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; the schema uses the `Generic.JSON` scalar; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-commit-web-url-338f55536a4a" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `branches.commit.web_url`

            Web URL records URL to view the commit in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-branches-default-d8996e622bb4" title="Default" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `branches.default`

            Default records whether this is the default branch of the repository. It is needed to distinguish Branches rows by the exact GitLab-returned default value.

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

          <Accordion id="provider-permission-field-gitlab-branches-developers-can-merge-a24110151b25" title="Developers Can Merge" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `branches.developers_can_merge`

            Developers Can Merge records whether developers are allowed to merge into this branch. It is needed to distinguish Branches rows by the exact GitLab-returned developers can merge value.

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

          <Accordion id="provider-permission-field-gitlab-branches-developers-can-push-6da8299089a5" title="Developers Can Push" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `branches.developers_can_push`

            Developers Can Push records whether developers are allowed to push to this branch. It is needed to distinguish Branches rows by the exact GitLab-returned developers can push value.

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

          <Accordion id="provider-permission-field-gitlab-branches-merged-8b56196943d2" title="Merged" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `branches.merged`

            Merged records whether the branch has been merged into the default branch. It is needed to distinguish Branches rows by the exact GitLab-returned merged value.

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

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

            Name records branch name. It is needed to distinguish repeated deliveries of the same Branches row using the declared ingestion key.

            * **Enables:** use `name` as the declared ingestion deduplication key for Branches and match repeated rows carrying the same GitLab identifier.
            * **Interpretation:** GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-branches-project-id-4c4ce8185957" title="Project ID" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `branches.project_id`

            Project ID records parent project's numeric id, injected by the ingestion service from the projects tap's parentContextFields. Absent from the GitLab branches API response body itself. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-branches-protected-6275a822c126" title="Protected" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `branches.protected`

            Protected records whether the branch is protected. It is needed to distinguish Branches rows by the exact GitLab-returned protected value.

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

          <Accordion id="provider-permission-field-gitlab-branches-web-url-e06fe306e9fb" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `branches.web_url`

            Web URL records URL to view the branch in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

      <Accordion id="provider-permission-tap-gitlab-commit-diffs-408c4694cc0e" title="Commit Diffs" icon="file-code" iconType="sharp-duotone-solid">
        Developer identifier: `commit_diffs`

        Commit Diffs covers diff details for a specific commit.

        * **Enables:** inspect each returned file diff in the context of its repository or project and parent commit.
        * **Scope:** Diff details for a specific commit; the connector reads `/api/v4/projects/{project_id}/repository/commits/{id}/diff` as an event stream in full mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-commit-diffs-a-mode-497c4110da98" title="A Mode" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.a_mode`

            A Mode records unix file mode of the file before the change (e.g., '100644' for regular file, '100755' for executable, '000000' for non-existent). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned a mode value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-b-mode-2e6be820bc3e" title="B Mode" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.b_mode`

            B Mode records unix file mode of the file after the change (e.g., '100644' for regular file, '100755' for executable, '000000' for deleted file). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned b mode value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-collapsed-a233359335b6" title="Collapsed" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.collapsed`

            Collapsed records whether the diff was returned in collapsed form (large diffs may be summarized rather than fully expanded). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned collapsed value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-committed-date-6fbc7cd04c8b" title="Committed Date" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.committed_date`

            Committed Date records timestamp when the parent commit was applied to the repository, injected by the ingestion service from the `branch_commits` tap's parentContextFields. Absent from the GitLab commit diff API response body itself. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Commit Diffs records by `committed_date`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab's child response does not supply this field; the connector injects parent context into each child row; it is interpreted at one GitLab Commit Diff record per row; the connector also declares it for record ordering; the schema assigns the `event_time` semantic role; the schema uses the `Temporal.DateTime` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-commit-diffs-deleted-file-62bb52e77ad4" title="Deleted File" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.deleted_file`

            Deleted File records whether the file was deleted in this commit. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned deleted file value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-diff-a993ccd4bbc5" title="Diff" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.diff`

            Diff records the actual unified diff content showing line-by-line additions and removals. May be truncated for very large diffs. It is needed to measure the GitLab-reported number of diff at one GitLab Commit Diff record per row.

            * **Enables:** measure and compare the GitLab-reported number of diff in `diff` at one GitLab Commit Diff record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is diff at one GitLab Commit Diff record per row; GitLab may omit, collapse, summarize, or truncate this code-change content as noted by the field description.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-commit-diffs-generated-file-4ac4927b7147" title="Generated File" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.generated_file`

            Generated File records whether GitLab considers this file to be a generated file (e.g., compiled assets, lock files). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned generated file value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-id-e645c22070f0" title="ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.id`

            ID records synthetic primary key computed by the ingestor from `old_path`, `new_path`, diff (sha1). Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to distinguish repeated deliveries of the same Commit Diffs row using the declared ingestion key.

            * **Enables:** use `id` as the declared ingestion deduplication key for Commit Diffs and match repeated rows carrying the same GitLab identifier.
            * **Interpretation:** GitLab's child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-commit-diffs-new-file-6e0a89448daa" title="New File" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.new_file`

            New File records whether this diff entry represents a newly created file. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned new file value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-new-path-70d4d8cd51b1" title="New Path" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.new_path`

            New Path records new file path after the change. Identifies which files were modified in each commit. Serves as the primary key for this diff entry. It is needed to refer to the same new path across records without relying on display text.

            * **Enables:** match `new_path` to new path references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is an identifier, not a measured quantity; the schema uses the `Asset.FilePath` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-commit-diffs-old-path-fc641f515fb5" title="Old Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.old_path`

            Old Path records original file path before the change. Used to track file renames and moves across commits. It is needed to compare the returned old path for individual Commit Diffs rows and select rows with a specific `old_path` value.

            * **Enables:** trace the old path relationship returned in `old_path` from the GitLab Commit Diff row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; the schema uses the `Asset.FilePath` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-commit-diffs-project-id-ab697caa7510" title="Project ID" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.project_id`

            Project ID records parent project's numeric id, injected by the ingestion service from the `branch_commits` tap's parentContextFields. Absent from the GitLab commit diff API response body itself. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-renamed-file-244d3ad2c801" title="Renamed File" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.renamed_file`

            Renamed File records whether the file was renamed in this commit. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned renamed file value.

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

          <Accordion id="provider-permission-field-gitlab-commit-diffs-too-large-54c0046f0975" title="Too Large" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `commit_diffs.too_large`

            Too Large records whether the diff exceeded the API's size limit and was truncated. When true, only a summary is returned. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned too large value.

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

      <Accordion id="provider-permission-tap-gitlab-group-members-742d892040cd" title="Group Members" icon="people-group" iconType="sharp-duotone-solid">
        Developer identifier: `group_members`

        Group Members covers members of a group (including inherited members).

        * **Enables:** map the GitLab accounts and memberships represented by Group Members records and trace a returned access assignment to its account or group.
        * **Scope:** Members of a group (including inherited members); the connector reads `/api/v4/groups/{id}/members/all` as a snapshot stream in full mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-group-members-access-level-38025b515e7b" title="Access Level" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.access_level`

            Access Level records numeric permission level granted to the member within the group (0=No access, 5=Minimal, 10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). GitLab returns this as an integer, not a string. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-group-members-avatar-url-63d976cf6f6f" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.avatar_url`

            Avatar URL records URL to the member's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-group-members-created-at-6d1481715f6a" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_at`

            Created At records timestamp when the user account was created. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-421ba358dc32" title="Created By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by`

            Created By records user who added this member to the group. It is needed to preserve the nested created by relationship or details on the parent GitLab Group Member record.

            * **Enables:** expand `created_by` to connect the containing GitLab Group Member row to its returned created by entries.
            * **Interpretation:** GitLab reports this value on the GitLab Group Member object returned for Group Members; it is one nested object per containing GitLab Group Member object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-avatar-url-29dcda29edf9" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by.avatar_url`

            Avatar URL records URL to the creator's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-id-261151a63012" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by.id`

            ID records user ID of the creator. It is needed to refer to the same member created by across records without relying on display text.

            * **Enables:** match `id` to member created by references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Member Created By object returned for Group Members; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-name-3184581b77bb" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by.name`

            Name records display name of the creator. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

            * **Enables:** attribute the Group Members row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the Member Created By object returned for Group Members; it is interpreted at one Member Created By record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-state-122653951b0c" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by.state`

            State records account state of the creator. It is needed to distinguish Group Members rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-username-b1cf48ca82f0" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by.username`

            User Name records GitLab username of the creator. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-group-members-created-by-web-url-314837bc0380" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.created_by.web_url`

            Web URL records URL to the creator's GitLab profile page. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-group-members-email-eeb0445a8cc6" title="Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.email`

            Email records email address of the member, if visible. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-group-members-expires-at-39988c16d1f7" title="Expires At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.expires_at`

            Expires At records membership expiration date if set (YYYY-MM-DD format). It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-group-members-group-saml-identity-9377d469c7ee" title="Group SAML Identity" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.group_saml_identity`

            Group SAML Identity records SAML identity information for the member if group SAML SSO is configured. It is needed to preserve the nested group saml identity relationship or details on the parent GitLab Group Member record.

            * **Enables:** expand `group_saml_identity` to connect the containing GitLab Group Member row to its returned group saml identity entries.
            * **Interpretation:** GitLab reports this value on the GitLab Group Member object returned for Group Members; it is one nested object per containing GitLab Group Member object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-group-saml-identity-extern--654ea8c1c510" title="Extern Uid" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.group_saml_identity.extern_uid`

            Extern Uid records external UID from the SAML identity provider. It is needed to refer to the same extern uid across records without relying on display text.

            * **Enables:** match `extern_uid` to extern uid references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Group Saml Identity object returned for Group Members; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-group-saml-identity-provide-963a05ac9f22" title="Provider" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.group_saml_identity.provider`

            Provider records name of the SAML identity provider. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

            * **Enables:** compare `provider` among Group Members records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** GitLab reports this value on the Group Saml Identity object returned for Group Members; it is interpreted at one Group Saml Identity record per row; the value is a GitLab-returned or configured label at the Group Saml Identity grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-group-saml-identity-saml-pr-41ed1ddac8d5" title="SAML Provider ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.group_saml_identity.saml_provider_id`

            SAML Provider ID records ID of the SAML provider configuration in GitLab. It is needed to refer to the same saml provider across records without relying on display text.

            * **Enables:** match `saml_provider_id` to saml provider references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Group Saml Identity object returned for Group Members; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-group-members-id-0fd9ceb995a0" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.id`

            ID records user ID of the member. It is needed to distinguish repeated deliveries of the same Group Members row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-group-members-is-using-seat-424d33ba1a26" title="Is Using Seat" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.is_using_seat`

            Is Using Seat records whether the member is consuming a license seat. It is needed to distinguish Group Members rows by the exact GitLab-returned is using seat value.

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

          <Accordion id="provider-permission-field-gitlab-group-members-membership-state-bf18139c3d01" title="Membership State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.membership_state`

            Membership State records state of the membership itself (active, awaiting, etc.). It is needed to distinguish Group Members rows by the exact GitLab-returned membership state value.

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

          <Accordion id="provider-permission-field-gitlab-group-members-name-e64642e2cc8e" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.name`

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

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

          <Accordion id="provider-permission-field-gitlab-group-members-override-2dfed306b883" title="Override" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.override`

            Override records whether the member's access level has been overridden from the inherited value. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-group-members-state-1b85906eff53" title="State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.state`

            State records account state of the member (active, blocked, etc.). It is needed to distinguish Group Members rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-group-members-username-d42e8d38bf57" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.username`

            User Name records GitLab username of the member. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-group-members-web-url-2e03fa525678" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `group_members.web_url`

            Web URL records URL to the member's GitLab profile page. It is needed to inspect the exact link included with this record.

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

      <Accordion id="provider-permission-tap-gitlab-groups-0e6fa0e7d939" title="Groups" icon="sitemap" iconType="sharp-duotone-solid">
        Developer identifier: `groups`

        Groups covers GitLab groups.

        * **Enables:** map the GitLab accounts and memberships represented by Groups records and trace a returned access assignment to its account or group.
        * **Scope:** GitLab groups; the connector reads `/api/v4/groups` as a snapshot stream in full mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-groups-auto-devops-enabled-789d7d456d3f" title="Auto Devops Enabled" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.auto_devops_enabled`

            Auto Devops Enabled records whether Auto DevOps is enabled by default for projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned auto devops enabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-avatar-url-a9315ec26d89" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.avatar_url`

            Avatar URL records URL of the group avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-created-at-6c1f67c897a8" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `groups.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-804b3d928ea6" title="Default Branch" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch`

            Default Branch records default branch name for projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned default branch value.

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

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-73a84c1dfd76" title="Default Branch Protection" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection`

            Default Branch Protection records default branch protection level for projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned default branch protection value.

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

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-defaults-76e272f23510" title="Default Branch Protection Defaults" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection_defaults`

            Default Branch Protection Defaults records default branch protection settings. It is needed to preserve the nested default branch protection defaults relationship or details on the parent GitLab Group record.

            * **Enables:** expand `default_branch_protection_defaults` to connect the containing GitLab Group row to its returned default branch protection defaults entries.
            * **Interpretation:** GitLab reports this value on the GitLab Group object returned for Groups; it is one nested object per containing GitLab Group object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-defaults-81ceae0b6872" title="Allow Force Push" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection_defaults.allow_force_push`

            Allow Force Push records whether force push is allowed on the default branch. It is needed to distinguish Groups rows by the exact GitLab-returned allow force push value.

            * **Enables:** select Groups rows where `allow_force_push` is true or false when comparing the condition described by Allow Force Push.
            * **Interpretation:** GitLab reports this value on the Default Branch Protection Defaults object returned for Groups; it is interpreted at one Default Branch Protection Defaults record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-defaults-dad172767e4a" title="Allowed To Merge" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection_defaults.allowed_to_merge`

            Allowed To Merge records roles allowed to merge into the default branch. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-defaults-8dd1bf10e042" title="Access Level" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection_defaults.allowed_to_merge.access_level`

            Access Level records numeric access level (e.g., 30 for developer, 40 for maintainer). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-defaults-ad611114e851" title="Allowed To Push" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection_defaults.allowed_to_push`

            Allowed To Push records roles allowed to push to the default branch. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-default-branch-protection-defaults-fdd7f0c4280a" title="Developer Can Initial Push" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.default_branch_protection_defaults.developer_can_initial_push`

            Developer Can Initial Push records whether developers can perform the initial push. It is needed to distinguish Groups rows by the exact GitLab-returned developer can initial push value.

            * **Enables:** select Groups rows where `developer_can_initial_push` is true or false when comparing the condition described by Developer Can Initial Push.
            * **Interpretation:** GitLab reports this value on the Default Branch Protection Defaults object returned for Groups; it is interpreted at one Default Branch Protection Defaults record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-description-9754ff63d460" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.description`

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

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

          <Accordion id="provider-permission-field-gitlab-groups-duo-features-enabled-02e394954d7a" title="Duo Features Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.duo_features_enabled`

            Duo Features Enabled records whether GitLab Duo features are enabled. It is needed to distinguish Groups rows by the exact GitLab-returned duo features enabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-emails-disabled-25f4e780b287" title="Emails Disabled" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `groups.emails_disabled`

            Emails Disabled records whether email notifications are disabled for the group. It is needed to distinguish Groups rows by the exact GitLab-returned emails disabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-emails-enabled-9d36291cb549" title="Emails Enabled" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `groups.emails_enabled`

            Emails Enabled records whether email notifications are enabled for the group. It is needed to distinguish Groups rows by the exact GitLab-returned emails enabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-enabled-git-access-protocol-754f7812329d" title="Enabled Git Access Protocol" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.enabled_git_access_protocol`

            Enabled Git Access Protocol records allowed Git access protocol (ssh, http, or all). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-extra-shared-runners-minutes-limit-c838dc1f8379" title="Extra Shared Runners Minutes Limit" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.extra_shared_runners_minutes_limit`

            Extra Shared Runners Minutes Limit records extra CI/CD minutes limit purchased for the group. It is needed to measure the reported extra shared runners minutes limit for one gitlab group record.

            * **Enables:** measure and compare `extra_shared_runners_minutes_limit` per GitLab Group record in minutes.
            * **Interpretation:** GitLab reports this value on the GitLab Group object returned for Groups; its unit or granularity is minutes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-file-template-project-id-25441819deb2" title="File Template Project ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.file_template_project_id`

            File Template Project ID records project ID used for file templates. It is needed to refer to the same file template project across records without relying on display text.

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

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

            Full Name records full human-readable name including parent group names separated by slashes. It is needed to compare the returned full name for individual Groups rows and select rows with a specific `full_name` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-full-path-991820616194" title="Full Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.full_path`

            Full Path records full path including parent groups, used for namespace resolution. It is needed to compare the returned full path for individual Groups rows and select rows with a specific `full_path` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-full-path-with-namespace-f3690dd6813e" title="Full Path With Namespace" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.full_path_with_namespace`

            Full Path With Namespace records alias for `full_path` including namespace. It is needed to compare the returned full path with namespace for individual Groups rows and select rows with a specific `full_path_with_namespace` value.

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

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

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

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

          <Accordion id="provider-permission-field-gitlab-groups-ip-restriction-ranges-9f572cec1485" title="IP Restriction Ranges" icon="ip" iconType="sharp-duotone-solid">
            Developer identifier: `groups.ip_restriction_ranges`

            IP Restriction Ranges records comma-separated list of IP address ranges allowed to access the group. It is needed to preserve the GitLab-reported network address context for the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-ldap-access-3eb6bdb71dd6" title="LDAP Access" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `groups.ldap_access`

            LDAP Access records minimum LDAP access level for group members. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-ldap-cn-8d931077f210" title="LDAP Cn" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.ldap_cn`

            LDAP Cn records LDAP Common Name linked to this group. It is needed to preserve the exact GitLab-reported business, directory, or identity attribute represented by this field.

            * **Enables:** match or segment Groups records by `ldap_cn` only within the same GitLab attribute contract.
            * **Interpretation:** GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the value is a GitLab-returned or configured label and is not a universal identity or business taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-lfs-enabled-f7797f2c5115" title="Lfs Enabled" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.lfs_enabled`

            Lfs Enabled records whether Git Large File Storage is enabled. It is needed to distinguish Groups rows by the exact GitLab-returned lfs enabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-lock-duo-features-enabled-2d169feee1a5" title="Lock Duo Features Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.lock_duo_features_enabled`

            Lock Duo Features Enabled records whether the Duo features setting is locked. It is needed to distinguish Groups rows by the exact GitLab-returned lock duo features enabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-lock-math-rendering-limits-enabled-ad332d6ae86e" title="Lock Math Rendering Limits Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.lock_math_rendering_limits_enabled`

            Lock Math Rendering Limits Enabled records whether the math rendering limits setting is locked. It is needed to distinguish Groups rows by the exact GitLab-returned lock math rendering limits enabled value.

            * **Enables:** select Groups rows where `lock_math_rendering_limits_enabled` is true or false when comparing the condition described by Lock Math Rendering Limits Enabled.
            * **Interpretation:** GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-marked-for-deletion-on-d1d8ed350752" title="Marked For Deletion On" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `groups.marked_for_deletion_on`

            Marked For Deletion On records date when the group was marked for deletion. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-groups-math-rendering-limits-enabled-f6e5323389f3" title="Math Rendering Limits Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.math_rendering_limits_enabled`

            Math Rendering Limits Enabled records whether math rendering limits are enabled. It is needed to distinguish Groups rows by the exact GitLab-returned math rendering limits enabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-membership-lock-6fc0cb2101c0" title="Membership Lock" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.membership_lock`

            Membership Lock records whether membership is locked and cannot be changed by non-owners. It is needed to distinguish Groups rows by the exact GitLab-returned membership lock value.

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

          <Accordion id="provider-permission-field-gitlab-groups-mentions-disabled-b382d3d6264e" title="Mentions Disabled" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.mentions_disabled`

            Mentions Disabled records whether mentions are disabled for the group. It is needed to distinguish Groups rows by the exact GitLab-returned mentions disabled value.

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

          <Accordion id="provider-permission-field-gitlab-groups-name-6ce2933bd844" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.name`

            Name records human-readable group name. It is needed to compare the returned name for individual Groups rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-parent-id-1684a2ef9f6d" title="Parent ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.parent_id`

            Parent ID records ID of the parent group, null if top-level. It is needed to refer to the same parent across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-groups-path-9a9859ccb5b7" title="Path" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.path`

            Path records URL-friendly path slug for the group. It is needed to compare the returned path for individual Groups rows and select rows with a specific `path` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-prevent-forking-outside-group-5bf9d07d37da" title="Prevent Forking Outside Group" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.prevent_forking_outside_group`

            Prevent Forking Outside Group records whether forking projects outside the group is prevented. It is needed to distinguish Groups rows by the exact GitLab-returned prevent forking outside group value.

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

          <Accordion id="provider-permission-field-gitlab-groups-prevent-sharing-groups-outside-hie-9984f98e650b" title="Prevent Sharing Groups Outside Hierarchy" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.prevent_sharing_groups_outside_hierarchy`

            Prevent Sharing Groups Outside Hierarchy records whether sharing groups outside the hierarchy is prevented. It is needed to distinguish Groups rows by the exact GitLab-returned prevent sharing groups outside hierarchy value.

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

          <Accordion id="provider-permission-field-gitlab-groups-project-creation-level-0270ec577936" title="Project Creation Level" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.project_creation_level`

            Project Creation Level records who can create projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned project creation level value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-9843c029f008" title="Projects" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects`

            Projects records list of projects within the group (when requested). It is needed to preserve the nested projects relationship or details on the parent GitLab Group record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-avatar-url-88ac91b842ea" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.avatar_url`

            Avatar URL records URL of the project avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-created-at-384fecdbf6a0" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-default-branch-0668a4e400a1" title="Default Branch" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.default_branch`

            Default Branch records default branch name. It is needed to distinguish Groups rows by the exact GitLab-returned default branch value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-description-4e4157a6a263" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.description`

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

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-forks-count-0da7f2006086" title="Forks Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.forks_count`

            Forks Count records number of forks. It is needed to measure the GitLab-reported number of forks at one Group Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of forks in `forks_count` at one Group Project record per row.
            * **Interpretation:** GitLab reports this value on the Group Project object returned for Groups; it is a GitLab-reported count at one Group Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-http-url-to-repo-04c933a800c6" title="HTTP URL To Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.http_url_to_repo`

            HTTP URL To Repo records HTTP URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Groups record.

            * **Enables:** use `http_url_to_repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

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

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

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-last-activity-at-2ce548f469a4" title="Last Activity At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.last_activity_at`

            Last Activity At records timestamp of the last activity on the project. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-name-ee90cfc32c53" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.name`

            Name records human-readable project name. It is needed to compare the returned name for individual Groups rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-name-with-namespace-666f625f0b27" title="Name With Namespace" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.name_with_namespace`

            Name With Namespace records full project name including namespace. It is needed to compare the returned name with namespace for individual Groups rows and select rows with a specific `name_with_namespace` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-ca7291edc761" title="Namespace" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace`

            Namespace records namespace the project belongs to. It is needed to preserve the nested namespace relationship or details on the parent Group Project record.

            * **Enables:** expand `namespace` to connect the containing Group Project row to its returned namespace entries.
            * **Interpretation:** GitLab reports this value on the Group Project object returned for Groups; it is one nested object per containing Group Project object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-avatar-url-24fe76bac5b7" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.avatar_url`

            Avatar URL records URL of the namespace avatar. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-full-path-f8b462e821db" title="Full Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.full_path`

            Full Path records full namespace path. It is needed to compare the returned full path for individual Groups rows and select rows with a specific `full_path` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-id-95b0d9b35caf" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.id`

            ID records namespace ID. It is needed to refer to the same project namespace across records without relying on display text.

            * **Enables:** match `id` to project namespace references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Project Namespace object returned for Groups; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-kind-8ee4c907288b" title="Kind" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.kind`

            Kind records namespace kind (group or user). It is needed to distinguish Groups rows by the exact GitLab-returned kind value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-name-f7317c84b3bf" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.name`

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

            * **Enables:** locate Groups rows whose returned name exactly matches `name` and retain the GitLab identifier for any cross-record match.
            * **Interpretation:** GitLab reports this value on the Project Namespace object returned for Groups; it is interpreted at one Project Namespace record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-parent-id-68e7b9501930" title="Parent ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.parent_id`

            Parent ID records parent namespace ID. It is needed to refer to the same parent across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-path-94cd3d8ad233" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.path`

            Path records namespace path. It is needed to compare the returned path for individual Groups rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the Project Namespace row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the Project Namespace object returned for Groups; it is interpreted at one Project Namespace record per row; the schema uses the `Identity.Slug` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-namespace-web-url-d19e8c65bf5a" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.namespace.web_url`

            Web URL records URL to the namespace page. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-path-81de83f8134a" title="Path" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.path`

            Path records URL-friendly path slug for the project. It is needed to compare the returned path for individual Groups rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the Group Project row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the `Identity.Slug` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-path-with-namespace-4c6fd5a2407f" title="Path With Namespace" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.path_with_namespace`

            Path With Namespace records full path including namespace. It is needed to compare the returned path with namespace for individual Groups rows and select rows with a specific `path_with_namespace` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-readme-url-7d33ebeb1c9b" title="Readme URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.readme_url`

            Readme URL records URL to the project README file. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-ssh-url-to-repo-fcf62be3b71e" title="SSH URL To Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.ssh_url_to_repo`

            SSH URL To Repo records SSH URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Groups record.

            * **Enables:** use `ssh_url_to_repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-star-count-696ff6772083" title="Star Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.star_count`

            Star Count records number of stars. It is needed to measure the GitLab-reported number of stars at one Group Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of stars in `star_count` at one Group Project record per row.
            * **Interpretation:** GitLab reports this value on the Group Project object returned for Groups; it is a GitLab-reported count at one Group Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-projects-tag-list-a5f2c3e5df30" title="Tag List" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.tag_list`

            Tag List records deprecated: List of tags. Use topics instead. It is needed to preserve the nested tag list relationship or details on the parent Group Project record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-topics-8ca8f693f412" title="Topics" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.topics`

            Topics records list of topic tags associated with the project. It is needed to preserve the nested topics relationship or details on the parent Group Project record.

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

          <Accordion id="provider-permission-field-gitlab-groups-projects-web-url-86b02180ac7c" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.projects.web_url`

            Web URL records URL to the project page in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-repository-storage-156133087384" title="Repository Storage" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.repository_storage`

            Repository Storage records name of the repository storage shard. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

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

          <Accordion id="provider-permission-field-gitlab-groups-request-access-enabled-ba6f162ef47f" title="Request Access Enabled" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `groups.request_access_enabled`

            Request Access Enabled records whether users can request access to the group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-require-two-factor-authentication-765805d3bfc0" title="Require Two Factor Authentication" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.require_two_factor_authentication`

            Require Two Factor Authentication records whether two-factor authentication is required for group members. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-runners-token-db88aeee3151" title="Runners Token" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `groups.runners_token`

            Runners Token records token used to register runners for this group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-share-with-group-lock-3b1e1f7bb445" title="Share With Group Lock" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.share_with_group_lock`

            Share With Group Lock records whether sharing projects with other groups is locked. It is needed to distinguish Groups rows by the exact GitLab-returned share with group lock value.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-projects-b20d4763156d" title="Shared Projects" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_projects`

            Shared Projects records list of projects shared with this group. It is needed to preserve the nested shared projects relationship or details on the parent GitLab Group record.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-runners-minutes-limit-24b59d085f65" title="Shared Runners Minutes Limit" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_runners_minutes_limit`

            Shared Runners Minutes Limit records CI/CD minutes limit for shared runners. It is needed to measure the reported shared runners minutes limit for one gitlab group record.

            * **Enables:** measure and compare `shared_runners_minutes_limit` per GitLab Group record in minutes.
            * **Interpretation:** GitLab reports this value on the GitLab Group object returned for Groups; its unit or granularity is minutes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-shared-runners-setting-c5be29f8cc34" title="Shared Runners Setting" icon="gear" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_runners_setting`

            Shared Runners Setting records shared runners availability setting. It is needed to distinguish Groups rows by the exact GitLab-returned shared runners setting value.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-with-groups-21a559ae291d" title="Shared With Groups" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_with_groups`

            Shared With Groups records list of groups this group is shared with. It is needed to preserve the explicit GitLab group references attached to this row.

            * **Enables:** split the references in `shared_with_groups` and match each returned group identifier to the corresponding GitLab group record when available.
            * **Interpretation:** GitLab reports this value on the GitLab Group object returned for Groups; it is one returned collection per containing GitLab Group object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-shared-with-groups-expires-at-3aae518331c0" title="Expires At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_with_groups.expires_at`

            Expires At records date when the sharing expires. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-with-groups-group-access-le-b888475a35ad" title="Group Access Level" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_with_groups.group_access_level`

            Group Access Level records access level granted to the shared group (e.g., 10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-with-groups-group-full-path-68dcd6b53970" title="Group Full Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_with_groups.group_full_path`

            Group Full Path records full path of the shared group. It is needed to compare the returned group full path for individual Groups rows and select rows with a specific `group_full_path` value.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-with-groups-group-id-5268b383299a" title="Group ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_with_groups.group_id`

            Group ID records ID of the shared group. It is needed to distinguish repeated deliveries of the same Groups row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-groups-shared-with-groups-group-name-e7866f2f75f9" title="Group Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `groups.shared_with_groups.group_name`

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

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

          <Accordion id="provider-permission-field-gitlab-groups-statistics-a7b49404a124" title="Statistics" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics`

            Statistics records storage and usage statistics for the group. It is needed to preserve the nested statistics relationship or details on the parent GitLab Group record.

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

          <Accordion id="provider-permission-field-gitlab-groups-statistics-job-artifacts-size-b9107fd3e37a" title="Job Artifacts Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.job_artifacts_size`

            Job Artifacts Size records total job artifacts size in bytes. It is needed to measure the reported job artifacts size for one group statistics record.

            * **Enables:** measure and compare `job_artifacts_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-lfs-objects-size-09de975b4040" title="Lfs Objects Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.lfs_objects_size`

            Lfs Objects Size records total LFS objects size in bytes. It is needed to measure the reported lfs objects size for one group statistics record.

            * **Enables:** measure and compare `lfs_objects_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-packages-size-531356852df8" title="Packages Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.packages_size`

            Packages Size records total packages size in bytes. It is needed to measure the reported packages size for one group statistics record.

            * **Enables:** measure and compare `packages_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-pipeline-artifacts-size-d5fce7fc8c9f" title="Pipeline Artifacts Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.pipeline_artifacts_size`

            Pipeline Artifacts Size records total pipeline artifacts size in bytes. It is needed to measure the reported pipeline artifacts size for one group statistics record.

            * **Enables:** measure and compare `pipeline_artifacts_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-repository-size-538bb2b00ccb" title="Repository Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.repository_size`

            Repository Size records total repository size in bytes. It is needed to measure the reported repository size for one group statistics record.

            * **Enables:** measure and compare `repository_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-snippets-size-0b2b128e427f" title="Snippets Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.snippets_size`

            Snippets Size records total snippets size in bytes. It is needed to measure the reported snippets size for one group statistics record.

            * **Enables:** measure and compare `snippets_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-storage-size-4eabf62c1fb5" title="Storage Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.storage_size`

            Storage Size records total storage size in bytes. It is needed to measure the reported storage size for one group statistics record.

            * **Enables:** measure and compare `storage_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-uploads-size-ce0d89257c69" title="Uploads Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.uploads_size`

            Uploads Size records total uploads size in bytes. It is needed to measure the reported uploads size for one group statistics record.

            * **Enables:** measure and compare `uploads_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-statistics-wiki-size-1724a8d60f69" title="Wiki Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.statistics.wiki_size`

            Wiki Size records total wiki size in bytes. It is needed to measure the reported wiki size for one group statistics record.

            * **Enables:** measure and compare `wiki_size` per Group Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-groups-subgroup-creation-level-946979d3f368" title="Subgroup Creation Level" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.subgroup_creation_level`

            Subgroup Creation Level records who can create subgroups in this group. It is needed to distinguish Groups rows by the exact GitLab-returned subgroup creation level value.

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

          <Accordion id="provider-permission-field-gitlab-groups-two-factor-grace-period-bf203e77bbb0" title="Two Factor Grace Period" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `groups.two_factor_grace_period`

            Two Factor Grace Period records grace period in hours before 2FA enforcement. It is needed to measure the reported two factor grace period for one gitlab group record.

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

          <Accordion id="provider-permission-field-gitlab-groups-visibility-81f7a570d8c6" title="Visibility" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.visibility`

            Visibility records group visibility level (private, internal, or public). It is needed to distinguish Groups rows by the exact GitLab-returned visibility value.

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

          <Accordion id="provider-permission-field-gitlab-groups-web-url-f3c69acca482" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `groups.web_url`

            Web URL records URL to the group page in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-groups-wiki-access-level-b2cf3fce488b" title="Wiki Access Level" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `groups.wiki_access_level`

            Wiki Access Level records access level for the group wiki. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

      <Accordion id="provider-permission-tap-gitlab-issues-3fcb6e21f94f" title="Issues" icon="list-check" iconType="sharp-duotone-solid">
        Developer identifier: `issues`

        Issues covers project issues.

        * **Enables:** follow each returned issue from its repository or project and issue number through author, assignee, state, and update time.
        * **Scope:** Project issues; the connector reads `/api/v4/projects/{id}/issues` as a changelog stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-issues-links-e965012e27b0" title="Links" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `issues._links`

            Links records related resource links for the issue. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact GitLab resource referenced by `_links` while retaining the containing Issues record as provenance.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is link at one GitLab Issue record per row; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-links-award-emoji-9720f91058f0" title="Award Emoji" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues._links.award_emoji`

            Award Emoji records API URL for award emoji on this issue. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-links-closed-as-duplicate-of-6dbbd2d1c6c5" title="Closed As Duplicate Of" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues._links.closed_as_duplicate_of`

            Closed As Duplicate Of records API URL of the issue this was closed as a duplicate of. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-links-notes-2bdae1a73e55" title="Notes" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues._links.notes`

            Notes records API URL for notes on this issue. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-links-project-77ad5adcb620" title="Project" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues._links.project`

            Project records API URL for the project this issue belongs to. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-links-self-f5603c9ab074" title="Self" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues._links.self`

            Self records API URL for this issue. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-assignees-7cc7289c8007" title="Assignees" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees`

            Assignees records array of users assigned to the issue. It is needed to preserve the nested assignees relationship or details on the parent GitLab Issue record.

            * **Enables:** expand `assignees` to connect the containing GitLab Issue row to its returned assignees entries.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is one returned collection per containing GitLab Issue object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-assignees-avatar-url-ca7002cb0659" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.avatar_url`

            Avatar URL records URL to the user's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-assignees-id-269e808af6ae" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.id`

            ID records unique numeric user ID. It is needed to distinguish repeated deliveries of the same Issues row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-issues-assignees-locked-7f935788040f" title="Locked" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.locked`

            Locked records whether the user account is locked. It is needed to distinguish Issues rows by the exact GitLab-returned locked value.

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

          <Accordion id="provider-permission-field-gitlab-issues-assignees-name-fa69fd3ac81a" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.name`

            Name records display name of the user. It is needed to attribute this Issues row to the returned person, account, or organization reference.

            * **Enables:** attribute the Issues row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-assignees-public-email-2a27c8aaba57" title="Public Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.public_email`

            Public Email records public email address of the user, enriched by the ingestion service via the GitLab Users API. Absent when the user has no public email set or when the enrichment call is suppressed (e.g. rate-limited backfills). Silver layers must treat this field as optional. It is needed to distinguish Issues rows by the exact GitLab-returned public email value.

            * **Enables:** separate Issues rows by the exact GitLab-returned `public_email` label when comparing public email.
            * **Interpretation:** GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row; the schema uses the `Contact.Email` scalar; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-assignees-state-fc7862a859ef" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.state`

            State records user account state (e.g., active, blocked). It is needed to distinguish Issues rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-issues-assignees-username-bad4f883fffe" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.username`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-assignees-web-url-573567f4eea5" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.assignees.web_url`

            Web URL records URL to the user's GitLab profile. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-author-384e9fb6b35c" title="Author" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `issues.author`

            Author records user who created the issue. It is needed to preserve the nested author relationship or details on the parent GitLab Issue record.

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

          <Accordion id="provider-permission-field-gitlab-issues-blocking-issues-count-c8de441f56ff" title="Blocking Issues Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.blocking_issues_count`

            Blocking Issues Count records number of issues this issue is blocking. It is needed to measure the GitLab-reported number of issues this issue is blocking at one GitLab Issue record per row.

            * **Enables:** measure and compare the GitLab-reported number of issues this issue is blocking in `blocking_issues_count` at one GitLab Issue record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-closed-at-41ad41f22bfb" title="Closed At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.closed_at`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-closed-by-f745dcd277d3" title="Closed By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `issues.closed_by`

            Closed By records user who closed the issue. It is needed to preserve the nested closed by relationship or details on the parent GitLab Issue record.

            * **Enables:** expand `closed_by` to connect the containing GitLab Issue row to its returned closed by entries.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-confidential-e97a28b4600e" title="Confidential" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.confidential`

            Confidential records whether the issue is confidential. It is needed to distinguish Issues rows by the exact GitLab-returned confidential value.

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

          <Accordion id="provider-permission-field-gitlab-issues-created-at-62cb5a606390" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-description-10ef0412fbea" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.description`

            Description records full issue description in Markdown. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is description text at one GitLab Issue record per row; the schema uses the `Text.Markdown` scalar; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-discussion-locked-abc9d42656cc" title="Discussion Locked" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.discussion_locked`

            Discussion Locked records whether discussion on the issue is locked. It is needed to distinguish Issues rows by the exact GitLab-returned discussion locked value.

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

          <Accordion id="provider-permission-field-gitlab-issues-downvotes-ecc2c8ec2ef2" title="Downvotes" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.downvotes`

            Downvotes records number of downvotes (thumbs down) on the issue. It is needed to measure the GitLab-reported number of downvotes (thumbs down) on the issue at one GitLab Issue record per row.

            * **Enables:** measure and compare the GitLab-reported number of downvotes (thumbs down) on the issue in `downvotes` at one GitLab Issue record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-due-date-2d35d6e60522" title="Due Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.due_date`

            Due Date records due date for the issue in YYYY-MM-DD format. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-issues-epic-e63eeb3869dc" title="Epic" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic`

            Epic records epic this issue belongs to. It is needed to preserve the nested epic relationship or details on the parent GitLab Issue record.

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

          <Accordion id="provider-permission-field-gitlab-issues-epic-group-id-f86141cd462e" title="Group ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic.group_id`

            Group ID records ID of the group this epic belongs to. It is needed to refer to the same group across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-epic-id-653399205baf" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic.id`

            ID records unique global numeric identifier for the epic. It is needed to refer to the same epic reference across records without relying on display text.

            * **Enables:** match `id` to epic reference references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-epic-iid-266f9b0fd47d" title="Iid" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic.iid`

            Iid records group-scoped epic number. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-epic-title-fb7665509389" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic.title`

            Title records epic title. It is needed to inspect the exact title text included with this record.

            * **Enables:** inspect the title text returned in `title` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is title text at one GitLab Epic Reference record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-epic-url-1b6e2cce26f0" title="URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic.url`

            URL records URL to view the epic in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-epic-iid-ac726d3e4df1" title="Epic Iid" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `issues.epic_iid`

            Epic Iid records IID of the epic this issue belongs to. It is needed to refer to the same epic iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-has-tasks-43718fcbf96d" title="Has Tasks" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.has_tasks`

            Has Tasks records whether the issue description contains task list items. It is needed to distinguish Issues rows by the exact GitLab-returned has tasks value.

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

          <Accordion id="provider-permission-field-gitlab-issues-health-status-773c337e8cf2" title="Health Status" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.health_status`

            Health Status records health status of the issue (`on_track`, `needs_attention`, `at_risk`). It is needed to distinguish Issues rows by the exact GitLab-returned health status value.

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

          <Accordion id="provider-permission-field-gitlab-issues-id-d61b496fbd74" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.id`

            ID records unique global numeric identifier for the issue. It is needed to distinguish repeated deliveries of the same Issues row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-issues-iid-3d83bccba941" title="Iid" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iid`

            Iid records project-scoped issue number. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-imported-904854bdb982" title="Imported" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `issues.imported`

            Imported records whether this issue was imported from an external source. It is needed to distinguish Issues rows by the exact GitLab-returned imported value.

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

          <Accordion id="provider-permission-field-gitlab-issues-imported-from-8ff87dd5346f" title="Imported From" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `issues.imported_from`

            Imported From records the source from which this issue was imported, if applicable. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

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

          <Accordion id="provider-permission-field-gitlab-issues-issue-type-2881697e2172" title="Issue Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `issues.issue_type`

            Issue Type records type classification of the issue. It is needed to distinguish Issues rows by the exact GitLab-returned issue type value.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-0ae759824490" title="Iteration" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration`

            Iteration records iteration this issue is assigned to. It is needed to preserve the nested iteration relationship or details on the parent GitLab Issue record.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-created-at-43fd5f61b3e4" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-description-20238c428b45" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.description`

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

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Iteration object returned for Issues; it is description text at one GitLab Iteration record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-iteration-due-date-3348636a311d" title="Due Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.due_date`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-group-id-aa1fa2842646" title="Group ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.group_id`

            Group ID records ID of the group this iteration belongs to. It is needed to refer to the same group across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-id-62fafb4c7a57" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.id`

            ID records unique global numeric identifier for the iteration. It is needed to refer to the same iteration across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-iid-50bed004a1e5" title="Iid" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.iid`

            Iid records group-scoped iteration number. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-sequence-60b41ef09e2c" title="Sequence" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.sequence`

            Sequence records sequence number of the iteration. It is needed to measure the GitLab-reported number of sequence at one GitLab Iteration record per row.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-start-date-11e901887098" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.start_date`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-state-be733fe84e46" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.state`

            State records iteration state as numeric value. It is needed to distinguish Issues rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-title-13a126f6f5c6" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.title`

            Title records iteration title. It is needed to inspect the exact title text included with this record.

            * **Enables:** inspect the title text returned in `title` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Iteration object returned for Issues; it is title text at one GitLab Iteration record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

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

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

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

          <Accordion id="provider-permission-field-gitlab-issues-iteration-web-url-9cec9aee9233" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.iteration.web_url`

            Web URL records URL to view the iteration in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-labels-b6bbf53357b3" title="Labels" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.labels`

            Labels records array of label names applied to the issue. It is needed to preserve the nested labels relationship or details on the parent GitLab Issue record.

            * **Enables:** expand `labels` to connect the containing GitLab Issue row to its returned labels entries.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is one returned collection per containing GitLab Issue object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-merge-requests-count-e44ef9a09b2b" title="Merge Requests Count" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `issues.merge_requests_count`

            Merge Requests Count records number of merge requests related to this issue. It is needed to measure the GitLab-reported number of merge requests related to this issue at one GitLab Issue record per row.

            * **Enables:** measure and compare the GitLab-reported number of merge requests related to this issue in `merge_requests_count` at one GitLab Issue record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-milestone-32e49b84f712" title="Milestone" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone`

            Milestone records milestone the issue is assigned to. It is needed to preserve the nested milestone relationship or details on the parent GitLab Issue record.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-created-at-5faee45a56a1" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-description-0fb0620cd838" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.description`

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

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Milestone object returned for Issues; it is description text at one GitLab Milestone record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-milestone-due-date-9e9a5cc5b524" title="Due Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.due_date`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-expired-a4a7fd93316e" title="Expired" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.expired`

            Expired records whether the milestone is past its due date. It is needed to distinguish Issues rows by the exact GitLab-returned expired value.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-group-id-9de9fe6cec7d" title="Group ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.group_id`

            Group ID records ID of the group this milestone belongs to (for group milestones). It is needed to refer to the same group across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-id-1e6dd97b02bd" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.id`

            ID records unique global numeric identifier for the milestone. It is needed to refer to the same milestone across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-iid-57d34af58332" title="Iid" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.iid`

            Iid records project-scoped milestone number. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-project-id-e970422891eb" title="Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.project_id`

            Project ID records ID of the project this milestone belongs to. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-start-date-1d3765c9f9e6" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.start_date`

            Start Date records start date for the milestone. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-state-5e6290b78c78" title="State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.state`

            State records milestone state (active or closed). It is needed to distinguish Issues rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-title-6d6006aec168" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.title`

            Title records milestone title. It is needed to inspect the exact title text included with this record.

            * **Enables:** inspect the title text returned in `title` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Milestone object returned for Issues; it is title text at one GitLab Milestone record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-milestone-updated-at-0950694a4520" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.updated_at`

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

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

          <Accordion id="provider-permission-field-gitlab-issues-milestone-web-url-4d4bf8459659" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.milestone.web_url`

            Web URL records URL to view the milestone in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-moved-to-id-ad349faf921b" title="Moved To ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.moved_to_id`

            Moved To ID records ID of the issue this was moved to, if moved. It is needed to refer to the same moved to across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-project-id-54d9bfeedd57" title="Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.project_id`

            Project ID records ID of the project this issue belongs to. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-issues-references-cf1b5e5cd09f" title="References" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `issues.references`

            References records short and full reference strings for the issue. It is needed to preserve the nested references relationship or details on the parent GitLab Issue record.

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

          <Accordion id="provider-permission-field-gitlab-issues-references-full-9107048418e6" title="Full" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `issues.references.full`

            Full records full reference including project path (e.g., group/project#123). It is needed to compare the returned full for individual Issues rows and select rows with a specific `full` value.

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

          <Accordion id="provider-permission-field-gitlab-issues-references-relative-38ca95e2d544" title="Relative" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `issues.references.relative`

            Relative records relative reference within the project. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-issues-references-short-02a64800f982" title="Short" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `issues.references.short`

            Short records short reference (e.g., #123). It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-issues-service-desk-reply-to-8b1454faf50d" title="Service Desk Reply To" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.service_desk_reply_to`

            Service Desk Reply To records email address for service desk replies. It is needed to attribute this Issues row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-issues-severity-87af137c14e7" title="Severity" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `issues.severity`

            Severity records severity level for incident-type issues. It is needed to distinguish Issues rows by the exact GitLab-returned severity value.

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

          <Accordion id="provider-permission-field-gitlab-issues-state-f66e13b7b0cf" title="State" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `issues.state`

            State records issue state (opened or closed). It is needed to distinguish Issues rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-issues-task-completion-status-007a45bfb2d1" title="Task Completion Status" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.task_completion_status`

            Task Completion Status records completion status of tasks within the issue description. It is needed to preserve the nested task completion status relationship or details on the parent GitLab Issue record.

            * **Enables:** expand `task_completion_status` to connect the containing GitLab Issue row to its returned task completion status entries.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-task-completion-status-completed-c-fa0a71bac06f" title="Completed Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.task_completion_status.completed_count`

            Completed Count records number of completed tasks. It is needed to measure the GitLab-reported number of completed tasks at one GitLab Task Completion Status record per row.

            * **Enables:** measure and compare the GitLab-reported number of completed tasks in `completed_count` at one GitLab Task Completion Status record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Task Completion Status object returned for Issues; it is a GitLab-reported count at one GitLab Task Completion Status record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-task-completion-status-count-0177fe96c6fe" title="Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.task_completion_status.count`

            Count records total number of tasks. It is needed to measure the GitLab-reported number of tasks at one GitLab Task Completion Status record per row.

            * **Enables:** measure and compare the GitLab-reported number of tasks in `count` at one GitLab Task Completion Status record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Task Completion Status object returned for Issues; it is a GitLab-reported count at one GitLab Task Completion Status record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-task-status-dee753229cc8" title="Task Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `issues.task_status`

            Task Status records human-readable task completion status string. It is needed to distinguish Issues rows by the exact GitLab-returned task status value.

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

          <Accordion id="provider-permission-field-gitlab-issues-time-stats-1dcc9c95aaeb" title="Time Stats" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.time_stats`

            Time Stats records time tracking statistics for the issue. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Issues records by `time_stats`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-time-stats-human-time-estimate-285402cf5638" title="Human Time Estimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.time_stats.human_time_estimate`

            Human Time Estimate records human-readable time estimate string. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-issues-time-stats-human-total-time-spent-2bdd56101b47" title="Human Total Time Spent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.time_stats.human_total_time_spent`

            Human Total Time Spent records human-readable total time spent string. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-issues-time-stats-time-estimate-76f840e90d76" title="Time Estimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.time_stats.time_estimate`

            Time Estimate records estimated time in seconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Issues records by `time_estimate`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab reports this value on the GitLab Time Stats object returned for Issues; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-time-stats-total-time-spent-0b52ad99aa46" title="Total Time Spent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.time_stats.total_time_spent`

            Total Time Spent records total time spent in seconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Issues records by `total_time_spent`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab reports this value on the GitLab Time Stats object returned for Issues; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-title-6f55d5b0109f" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.title`

            Title records issue title. It is needed to inspect the exact title text included with this record.

            * **Enables:** inspect the title text returned in `title` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is title text at one GitLab Issue record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

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

            Type records issue type (e.g., issue, incident, `test_case`, task). It is needed to distinguish Issues rows by the exact GitLab-returned type value.

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

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

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

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

          <Accordion id="provider-permission-field-gitlab-issues-upvotes-8abb3328e76f" title="Upvotes" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.upvotes`

            Upvotes records number of upvotes (thumbs up) on the issue. It is needed to measure the GitLab-reported number of upvotes (thumbs up) on the issue at one GitLab Issue record per row.

            * **Enables:** measure and compare the GitLab-reported number of upvotes (thumbs up) on the issue in `upvotes` at one GitLab Issue record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-user-notes-count-a1fd73f9be3e" title="User Notes Count" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `issues.user_notes_count`

            User Notes Count records number of user-created notes (comments) on the issue. It is needed to measure the GitLab-reported number of user-created notes (comments) on the issue at one GitLab Issue record per row.

            * **Enables:** measure and compare the GitLab-reported number of user-created notes (comments) on the issue in `user_notes_count` at one GitLab Issue record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-issues-web-url-0f0c90ff7db7" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.web_url`

            Web URL records URL to view the issue in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-issues-weight-a9e634fc24c9" title="Weight" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `issues.weight`

            Weight records issue weight (effort estimate). It is needed to compare the numeric weight reported for one GitLab Issue record without assuming an unstated unit.

            * **Enables:** compare the numeric `weight` value per GitLab Issue record without assigning a unit not declared by the schema description.
            * **Interpretation:** GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-gitlab-merge-request-notes-9875b3ca26b5" title="Merge Request Notes" icon="code-merge" iconType="sharp-duotone-solid">
        Developer identifier: `merge_request_notes`

        Merge Request Notes covers notes (comments) on merge requests.

        * **Enables:** attribute each returned review comment or note to its work item, author, file or diff position, and time where those fields are present.
        * **Scope:** Notes (comments) on merge requests; the connector reads `/api/v4/projects/{project_id}/merge_requests/{iid}/notes` as a changelog stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-merge-request-notes-attachment-8894b1ba7baf" title="Attachment" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.attachment`

            Attachment records the filename of an attachment on the note, if any. It is needed to inspect the exact attachment filename returned for this GitLab Merge Request Note record.

            * **Enables:** attribute the attachment filename in `attachment` to the containing Merge Request Notes identifier, owner or author, status, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; this is only the attachment filename included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-1b4a3e4a4f4a" title="Author" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author`

            Author records the user who authored the note. It is needed to preserve the nested author relationship or details on the parent GitLab Merge Request Note record.

            * **Enables:** expand `author` to connect the containing GitLab Merge Request Note row to its returned author entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-avatar-url-c6d5caa73245" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.avatar_url`

            Avatar URL records URL to the user's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-email-11e1c9eba89b" title="Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.email`

            Email records the email address of the user (may be empty if private). It is needed to attribute this Merge Request Notes row to the returned person, account, or organization reference.

            * **Enables:** attribute the Merge Request Notes row to the returned person or account and match the exact `email` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; the schema uses the `Contact.Email` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-id-22134f14c5b3" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.id`

            ID records unique identifier of the user. It is needed to refer to the same note author across records without relying on display text.

            * **Enables:** match `id` to note author references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Note Author object returned for Merge Request Notes; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-locked-395c27c7fe49" title="Locked" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.locked`

            Locked records whether the user account is locked. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned locked value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-name-7adb25c54c87" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.name`

            Name records the display name of the user. It is needed to attribute this Merge Request Notes row to the returned person, account, or organization reference.

            * **Enables:** attribute the Merge Request Notes row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-public-email-5a95554ab5c1" title="Public Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.public_email`

            Public Email records public email address, enriched by the ingestion service via the GitLab Users API. Absent when the user has no public email set or when enrichment is suppressed (e.g. rate-limited backfills). Silver layers must treat this field as optional. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned public email value.

            * **Enables:** separate Merge Request Notes rows by the exact GitLab-returned `public_email` label when comparing public email.
            * **Interpretation:** GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; the schema uses the `Contact.Email` scalar; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-state-a58527a03dbd" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.state`

            State records the current state of the user account. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-username-5b9c9a6a3e3f" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.username`

            User Name records the username/handle of the user. It is needed to attribute this Merge Request Notes row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-author-web-url-c6945c334c59" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.author.web_url`

            Web URL records URL to the user's GitLab profile page. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-body-5451577072be" title="Body" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.body`

            Body records the text content of the note/comment. It is needed to inspect the exact comment body included with this record.

            * **Enables:** inspect the comment body returned in `body` and attribute it to the same record's repository or project, revision, file path, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is comment body at one GitLab Merge Request Note record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-04c136301871" title="Change Position" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position`

            Change Position records updated position information if the diff has changed since the note was created. It is needed to preserve the nested change position relationship or details on the parent GitLab Merge Request Note record.

            * **Enables:** expand `change_position` to connect the containing GitLab Merge Request Note row to its returned change position entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-base--334f439f8fb4" title="Base Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.base_sha`

            Base Sha records the base commit SHA of the diff. It is needed to refer to the same base across records without relying on display text.

            * **Enables:** match `base_sha` to base references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-head--fc00e2235333" title="Head Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.head_sha`

            Head Sha records the head commit SHA of the diff. It is needed to refer to the same head across records without relying on display text.

            * **Enables:** match `head_sha` to head references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-heigh-5959e81c221d" title="Height" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.height`

            Height records height of the image, for image diff notes. It is needed to compare the numeric height reported for one Diff Position record without assuming an unstated unit.

            * **Enables:** compare the numeric `height` value per Diff Position record without assigning a unit not declared by the schema description.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--be703bb863c5" title="Line Range" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range`

            Line Range records the range of lines this note covers, for multi-line diff notes. It is needed to preserve the nested line range relationship or details on the parent Diff Position record.

            * **Enables:** expand `line_range` to connect the containing Diff Position row to its returned line range entries.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is one nested object per containing Diff Position object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--7f42722a2269" title="End" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range.end`

            End records the end position of the line range. It is needed to preserve the nested end relationship or details on the parent Line Range record.

            * **Enables:** expand `end` to connect the containing Line Range row to its returned end entries.
            * **Interpretation:** GitLab reports this value on the Line Range object returned for Merge Request Notes; it is one nested object per containing Line Range object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--f752a9d0f688" title="Line Code" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range.end.line_code`

            Line Code records the internal line code identifier. It is needed to refer to the same line code across records without relying on display text.

            * **Enables:** match `line_code` to line code references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Line Position object returned for Merge Request Notes; it is an identifier, not a measured quantity; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--0d8e1a6e5e56" title="New Line" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range.end.new_line`

            New Line records the line number in the new version. It is needed to compare the exact new line configuration returned for this Line Position record.

            * **Enables:** compare the exact `new_line` configuration returned for each Line Position record and select records with the configuration under review.
            * **Interpretation:** GitLab reports this value on the Line Position object returned for Merge Request Notes; it is interpreted at one Line Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--a2fb5eb9b11f" title="Old Line" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range.end.old_line`

            Old Line records the line number in the old version. It is needed to compare the exact old line configuration returned for this Line Position record.

            * **Enables:** compare the exact `old_line` configuration returned for each Line Position record and select records with the configuration under review.
            * **Interpretation:** GitLab reports this value on the Line Position object returned for Merge Request Notes; it is interpreted at one Line Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--5374e11798b1" title="Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range.end.type`

            Type records the type of line (new or old). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned type value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-line--70668ce51205" title="Start" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.line_range.start`

            Start records the start position of the line range. It is needed to preserve the nested start relationship or details on the parent Line Range record.

            * **Enables:** expand `start` to connect the containing Line Range row to its returned start entries.
            * **Interpretation:** GitLab reports this value on the Line Range object returned for Merge Request Notes; it is one nested object per containing Line Range object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-new-l-4ceee5892e22" title="New Line" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.new_line`

            New Line records the line number in the new version of the file. It is needed to compare the exact new line configuration returned for this Diff Position record.

            * **Enables:** compare the exact `new_line` configuration returned for each Diff Position record and select records with the configuration under review.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-new-p-c77fa7298427" title="New Path" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.new_path`

            New Path records the file path in the new version of the diff. It is needed to compare the exact new path configuration returned for this Diff Position record.

            * **Enables:** compare the exact `new_path` configuration returned for each Diff Position record and select records with the configuration under review.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-old-l-e77947ac0d76" title="Old Line" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.old_line`

            Old Line records the line number in the old version of the file. It is needed to compare the exact old line configuration returned for this Diff Position record.

            * **Enables:** compare the exact `old_line` configuration returned for each Diff Position record and select records with the configuration under review.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-old-p-cca83d374d68" title="Old Path" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.old_path`

            Old Path records the file path in the old version of the diff. It is needed to compare the exact old path configuration returned for this Diff Position record.

            * **Enables:** compare the exact `old_path` configuration returned for each Diff Position record and select records with the configuration under review.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-posit-0f0763a4a86b" title="Position Type" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.position_type`

            Position Type records the type of position (e.g., text, image, file). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned position type value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-start-175cf92911fd" title="Start Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.start_sha`

            Start Sha records the start commit SHA of the diff. It is needed to refer to the same start across records without relying on display text.

            * **Enables:** match `start_sha` to start references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-width-064750a2a568" title="Width" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.width`

            Width records width of the image, for image diff notes. It is needed to compare the numeric width reported for one Diff Position record without assuming an unstated unit.

            * **Enables:** compare the numeric `width` value per Diff Position record without assigning a unit not declared by the schema description.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-x-8d0bc704c8bf" title="X Coordinate" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.x`

            X Coordinate records x coordinate on the image, for image diff notes. It is needed to measure the reported x coordinate for one diff position record.

            * **Enables:** measure and compare `x` per Diff Position record in provider-reported geographic coordinates.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; its unit or granularity is provider-reported geographic coordinates.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-change-position-y-0cc0c1577168" title="Y Coordinate" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.change_position.y`

            Y Coordinate records y coordinate on the image, for image diff notes. It is needed to measure the reported y coordinate for one diff position record.

            * **Enables:** measure and compare `y` per Diff Position record in provider-reported geographic coordinates.
            * **Interpretation:** GitLab reports this value on the Diff Position object returned for Merge Request Notes; its unit or granularity is provider-reported geographic coordinates.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-commands-changes-59292cbafb8b" title="Commands Changes" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.commands_changes`

            Commands Changes records quick action commands that were applied when the note was created. It is needed to preserve the exact GitLab configuration or execution metadata attached to this GitLab Merge Request Note record.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-commit-id-ee6d5e767ea7" title="Commit ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.commit_id`

            Commit ID records the commit SHA this diff note references, if applicable. It is needed to refer to the same commit across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-confidential-4e39747a3139" title="Confidential" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.confidential`

            Confidential records whether this note is confidential (visible only to project members with Reporter role or above). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-created-at-0df4d199fcdc" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.created_at`

            Created At records when the note was created. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-id-711746e13c3d" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.id`

            ID records unique identifier of the note. It is needed to distinguish repeated deliveries of the same Merge Request Notes row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-imported-e9f9a2f140dc" title="Imported" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.imported`

            Imported records whether this note was imported from an external source. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned imported value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-imported-from-8b8855e640c0" title="Imported From" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.imported_from`

            Imported From records the source from which this note was imported, if applicable. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

            * **Enables:** compare `imported_from` among Merge Request Notes records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the value is a GitLab-returned or configured label at the GitLab Merge Request Note grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-internal-751637d5c812" title="Internal" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.internal`

            Internal records whether this note is internal (same as confidential in newer API versions). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned internal value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-line-type-746c7718faf9" title="Line Type" icon="comment-dots" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.line_type`

            Line Type records for diff notes, whether the comment is on an old or new line. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned line type value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-noteable-id-0a20d1d18f58" title="Noteable ID" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.noteable_id`

            Noteable ID records ID of the merge request this note belongs to. It is needed to refer to the same noteable across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-noteable-iid-a450cec3d055" title="Noteable Iid" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.noteable_iid`

            Noteable Iid records internal ID (IID) of the merge request within the project. It is needed to refer to the same noteable iid across records without relying on display text.

            * **Enables:** match `noteable_iid` to noteable iid references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-noteable-type-95c4d9ce3c35" title="Noteable Type" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.noteable_type`

            Noteable Type records the type of the parent noteable object (e.g., MergeRequest). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned noteable type value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-position-e7dae0f4c15f" title="Position" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.position`

            Position records position information for diff notes, indicating the file and line location. It is needed to preserve the nested position relationship or details on the parent GitLab Merge Request Note record.

            * **Enables:** expand `position` to connect the containing GitLab Merge Request Note row to its returned position entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-project-id-69c0c37a8b04" title="Project ID" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.project_id`

            Project ID records ID of the project containing the merge request. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-resolvable-17164ca49fb9" title="Resolvable" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.resolvable`

            Resolvable records whether this note is a resolvable discussion thread. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned resolvable value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-resolved-b90b6d3a37d5" title="Resolved" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.resolved`

            Resolved records whether this resolvable note has been resolved. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned resolved value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-resolved-at-a5d93f204892" title="Resolved At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.resolved_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-resolved-by-a7b076880b46" title="Resolved By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.resolved_by`

            Resolved By records the user who resolved this note, if resolved. It is needed to preserve the nested resolved by relationship or details on the parent GitLab Merge Request Note record.

            * **Enables:** expand `resolved_by` to connect the containing GitLab Merge Request Note row to its returned resolved by entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-suggestions-43715f579104" title="Suggestions" icon="headset" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.suggestions`

            Suggestions records inline code suggestions attached to a diff note, enriched by the ingestion service via a follow-up call to the GitLab Notes Suggestions API. Absent on non-diff notes or when enrichment is suppressed. Silver layers must treat this field as optional and JSON-encoded. It is needed to compare the exact suggestions configuration returned for this GitLab Merge Request Note record.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-system-0d8831fb248e" title="System" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.system`

            System records whether this is a system-generated note (e.g., status changes, label additions). It is needed to measure the GitLab-reported number of system at one GitLab Merge Request Note record per row.

            * **Enables:** measure and compare the GitLab-reported number of system in `system` at one GitLab Merge Request Note record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is a GitLab-reported count at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-type-007b1df36698" title="Type" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.type`

            Type records the type of the note (e.g., DiffNote, DiscussionNote, or null for regular notes). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned type value.

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

          <Accordion id="provider-permission-field-gitlab-merge-request-notes-updated-at-203491d73ba1" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `merge_request_notes.updated_at`

            Updated At records when the note was last updated. It is needed to place the record at the time or date reported for this event or state.

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

      <Accordion id="provider-permission-tap-gitlab-merge-requests-d50aa4430514" title="Merge Requests" icon="code-merge" iconType="sharp-duotone-solid">
        Developer identifier: `merge_requests`

        Merge Requests covers project merge requests.

        * **Enables:** follow each returned code-review request from its repository or project and source revision through reviewer, state, and merge outcome.
        * **Scope:** Project merge requests; the connector reads `/api/v4/projects/{id}/merge_requests` as a changelog stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-merge-requests-allow-collaboration-1792fd2656e1" title="Allow Collaboration" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.allow_collaboration`

            Allow Collaboration records whether collaboration from upstream members is allowed on the source branch. It is needed to distinguish Merge Requests rows by the exact GitLab-returned allow collaboration value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-allow-maintainer-to-push-09138d84b9bf" title="Allow Maintainer To Push" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.allow_maintainer_to_push`

            Allow Maintainer To Push records deprecated alias for `allow_collaboration`. It is needed to distinguish Merge Requests rows by the exact GitLab-returned allow maintainer to push value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-approvals-before-merge-5954b6fa22ce" title="Approvals Before Merge" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.approvals_before_merge`

            Approvals Before Merge records number of approvals required before merge (project-level setting override). It is needed to measure the GitLab-reported number of approvals required before merge (project-level setting override) at one GitLab Merge Request record per row.

            * **Enables:** measure and compare the GitLab-reported number of approvals required before merge (project-level setting override) in `approvals_before_merge` at one GitLab Merge Request record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-196ff4dc2339" title="Assignees" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees`

            Assignees records array of users assigned to review the MR. It is needed to preserve the nested assignees relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `assignees` to connect the containing GitLab Merge Request row to its returned assignees entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one returned collection per containing GitLab Merge Request object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-avatar-url-161a336567f8" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.avatar_url`

            Avatar URL records URL to the user's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-id-b2afcbfcaef9" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.id`

            ID records unique numeric user ID. It is needed to distinguish repeated deliveries of the same Merge Requests row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-locked-38a30279cf65" title="Locked" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.locked`

            Locked records whether the user account is locked. It is needed to distinguish Merge Requests rows by the exact GitLab-returned locked value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-name-df25105ef955" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.name`

            Name records display name of the user. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Merge Requests row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-public-email-6bf8b1105a84" title="Public Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.public_email`

            Public Email records public email address, enriched by the ingestion service via the GitLab Users API. Absent when the user has no public email set or when enrichment is suppressed (e.g. rate-limited backfills). Silver layers must treat this field as optional. It is needed to distinguish Merge Requests rows by the exact GitLab-returned public email value.

            * **Enables:** separate Merge Requests rows by the exact GitLab-returned `public_email` label when comparing public email.
            * **Interpretation:** GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row; the schema uses the `Contact.Email` scalar; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-state-b21f26361753" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.state`

            State records user account state (e.g., active, blocked). It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-username-76bbc15e7ac8" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.username`

            User Name records GitLab username. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Merge Requests row to the returned person or account and match the exact `username` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-assignees-web-url-daf1a246cecb" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.assignees.web_url`

            Web URL records URL to the user's GitLab profile. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-author-16f5c632961b" title="Author" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.author`

            Author records user who created the merge request. It is needed to preserve the nested author relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `author` to connect the containing GitLab Merge Request row to its returned author entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-blocking-discussions-resol-13d5524f8e20" title="Blocking Discussions Resolved" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.blocking_discussions_resolved`

            Blocking Discussions Resolved records whether all blocking discussions have been resolved. It is needed to distinguish Merge Requests rows by the exact GitLab-returned blocking discussions resolved value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-changes-count-ff0659bcd040" title="Changes Count" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.changes_count`

            Changes Count records number of file changes as a string (may be '100+' for large diffs). It is needed to measure the GitLab-reported number of file changes as a string (may be '100+' for large diffs) at one GitLab Merge Request record per row.

            * **Enables:** measure and compare the GitLab-reported number of file changes as a string (may be '100+' for large diffs) in `changes_count` at one GitLab Merge Request record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-at-cfa802cb34f5" title="Closed At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_at`

            Closed At records timestamp when the MR was closed, null if not closed. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-b43ab1b23f8e" title="Closed By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by`

            Closed By records user who closed the MR. It is needed to preserve the nested closed by relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `closed_by` to connect the containing GitLab Merge Request row to its returned closed by entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-avatar-url-e3ff029c8347" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.avatar_url`

            Avatar URL records URL to the user's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-id-dccb5f709ad4" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.id`

            ID records unique numeric user ID. It is needed to refer to the same user ref across records without relying on display text.

            * **Enables:** match `id` to user ref references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-locked-5c4562983395" title="Locked" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.locked`

            Locked records whether the user account is locked. It is needed to distinguish Merge Requests rows by the exact GitLab-returned locked value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-name-8c3d97a9d757" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.name`

            Name records display name of the user. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Merge Requests row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-public-email-8f895102a8b4" title="Public Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.public_email`

            Public Email records public email address returned by GitLab when present. Silver layers must treat this field as optional. It is needed to distinguish Merge Requests rows by the exact GitLab-returned public email value.

            * **Enables:** separate Merge Requests rows by the exact GitLab-returned `public_email` label when comparing public email.
            * **Interpretation:** GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row; the schema uses the `Contact.Email` scalar; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-state-e7d4e7ed00bb" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.state`

            State records user account state (e.g., active, blocked). It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-username-3ad77d72d919" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.username`

            User Name records GitLab username. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

            * **Enables:** attribute the Merge Requests row to the returned person or account and match the exact `username` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-closed-by-web-url-6f731f7ac489" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.closed_by.web_url`

            Web URL records URL to the user's GitLab profile. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-created-at-23a468c1acfc" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-description-951acd22e633" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.description`

            Description records merge request description body, may contain Markdown. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is description text at one GitLab Merge Request record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-detailed-merge-status-9f45ea031ef4" title="Detailed Merge Status" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.detailed_merge_status`

            Detailed Merge Status records detailed merge readiness status with specific blocking reasons. It is needed to distinguish Merge Requests rows by the exact GitLab-returned detailed merge status value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-diff-refs-1bc95c6e36b4" title="Diff Refs" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.diff_refs`

            Diff Refs records references to the base, head, and start SHAs for the diff. It is needed to preserve the nested diff refs relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `diff_refs` to connect the containing GitLab Merge Request row to its returned diff refs entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-diff-refs-base-sha-cf6049c1da0b" title="Base Sha" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.diff_refs.base_sha`

            Base Sha records SHA of the merge base commit. It is needed to refer to the same base across records without relying on display text.

            * **Enables:** match `base_sha` to base references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Diff Refs object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-diff-refs-head-sha-7740edeebf41" title="Head Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.diff_refs.head_sha`

            Head Sha records SHA of the head commit of the source branch. It is needed to refer to the same head across records without relying on display text.

            * **Enables:** match `head_sha` to head references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Diff Refs object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-diff-refs-start-sha-50a1c962e7cf" title="Start Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.diff_refs.start_sha`

            Start Sha records SHA of the start commit for the diff. It is needed to refer to the same start across records without relying on display text.

            * **Enables:** match `start_sha` to start references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Diff Refs object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-discussion-locked-f3f73cc42e57" title="Discussion Locked" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.discussion_locked`

            Discussion Locked records whether discussions on the MR are locked. It is needed to distinguish Merge Requests rows by the exact GitLab-returned discussion locked value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-downvotes-99263452c0c8" title="Downvotes" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.downvotes`

            Downvotes records number of downvote (thumbs down) reactions. It is needed to measure the GitLab-reported number of downvote (thumbs down) reactions at one GitLab Merge Request record per row.

            * **Enables:** measure and compare the GitLab-reported number of downvote (thumbs down) reactions in `downvotes` at one GitLab Merge Request record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-draft-66b9992d18a3" title="Draft" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.draft`

            Draft records whether the merge request is a draft (work in progress). It is needed to distinguish Merge Requests rows by the exact GitLab-returned draft value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-force-remove-source-branch-3cb4fe1a1498" title="Force Remove Source Branch" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.force_remove_source_branch`

            Force Remove Source Branch records whether the source branch will be force-removed after merge. It is needed to distinguish Merge Requests rows by the exact GitLab-returned force remove source branch value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-has-conflicts-8dc2367e4843" title="Has Conflicts" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.has_conflicts`

            Has Conflicts records whether the MR has merge conflicts. It is needed to distinguish Merge Requests rows by the exact GitLab-returned has conflicts value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-211ab0a697e5" title="Head Pipeline" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline`

            Head Pipeline records pipeline running on the head commit of the source branch. It is needed to preserve the nested head pipeline relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `head_pipeline` to connect the containing GitLab Merge Request row to its returned head pipeline entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-created-at-61c68942fa21" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-id-58c3551158da" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.id`

            ID records unique pipeline ID. It is needed to refer to the same pipeline reference across records without relying on display text.

            * **Enables:** match `id` to pipeline reference references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-iid-2597725b6e17" title="Iid" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.iid`

            Iid records project-scoped pipeline ID. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-project-id-a433045218ec" title="Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.project_id`

            Project ID records ID of the project the pipeline belongs to. It is needed to refer to the same project across records without relying on display text.

            * **Enables:** match `project_id` to project references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-ref-0a70a9fd57a5" title="Ref" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.ref`

            Ref records branch or tag name the pipeline ran on. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-sha-9b70691eef15" title="Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.sha`

            Sha records SHA of the commit the pipeline ran on. It is needed to refer to the same pipeline reference across records without relying on display text.

            * **Enables:** match `sha` to pipeline reference references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-source-5642fa2b8523" title="Source" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.source`

            Source records source that triggered the pipeline (e.g., push, `merge_request_event`). It is needed to distinguish Merge Requests rows by the exact GitLab-returned source value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-status-2b5a33ff6e28" title="Status" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.status`

            Status records pipeline status (e.g., running, pending, success, failed, canceled, skipped). It is needed to distinguish Merge Requests rows by the exact GitLab-returned status value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-updated-at-dea289e33b87" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.updated_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-head-pipeline-web-url-ca685185da44" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.head_pipeline.web_url`

            Web URL records URL to view the pipeline in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-id-34f36f0aed79" title="ID" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.id`

            ID records unique global numeric identifier for the merge request. It is needed to distinguish repeated deliveries of the same Merge Requests row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-iid-2c0b59f84fd1" title="Iid" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.iid`

            Iid records project-scoped merge request number. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-imported-ef8c3e1b09dd" title="Imported" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.imported`

            Imported records whether this merge request was imported from an external source. It is needed to distinguish Merge Requests rows by the exact GitLab-returned imported value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-imported-from-075b84d5b78a" title="Imported From" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.imported_from`

            Imported From records the source from which this merge request was imported, if applicable. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-labels-208532510776" title="Labels" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.labels`

            Labels records array of label names applied to the MR. It is needed to preserve the nested labels relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `labels` to connect the containing GitLab Merge Request row to its returned labels entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one returned collection per containing GitLab Merge Request object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-merge-after-ab6b5d9a21ca" title="Merge After" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merge_after`

            Merge After records timestamp after which the merge request may be merged (auto-merge scheduling). It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-merge-commit-sha-8c549ee8241c" title="Merge Commit Sha" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merge_commit_sha`

            Merge Commit Sha records SHA of the merge commit, null if not yet merged. It is needed to refer to the same merge commit across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-merge-status-aa19da565001" title="Merge Status" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merge_status`

            Merge Status records merge readiness status of the MR. It is needed to distinguish Merge Requests rows by the exact GitLab-returned merge status value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-merge-user-517c6e9ee354" title="Merge User" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merge_user`

            Merge User records user who triggered the merge (may differ from `merged_by` for auto-merge). It is needed to preserve the nested merge user relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `merge_user` to connect the containing GitLab Merge Request row to its returned merge user entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-merge-when-pipeline-succee-ad0560d47988" title="Merge When Pipeline Succeeds" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merge_when_pipeline_succeeds`

            Merge When Pipeline Succeeds records whether auto-merge is enabled when the pipeline succeeds. It is needed to distinguish Merge Requests rows by the exact GitLab-returned merge when pipeline succeeds value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-merged-at-598c1a9a723a" title="Merged At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merged_at`

            Merged At records timestamp when the MR was merged, null if not yet merged. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-merged-by-90b871052e01" title="Merged By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.merged_by`

            Merged By records user who merged the MR. It is needed to preserve the nested merged by relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `merged_by` to connect the containing GitLab Merge Request row to its returned merged by entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-abc007c85cb6" title="Milestone" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone`

            Milestone records milestone associated with the MR. It is needed to preserve the nested milestone relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `milestone` to connect the containing GitLab Merge Request row to its returned milestone entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-created-at-bd3ee06a566a" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-description-ae39634f23df" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.description`

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

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the Milestone object returned for Merge Requests; it is description text at one Milestone record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-due-date-d4cdb18e577d" title="Due Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.due_date`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-expired-4a3599babd50" title="Expired" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.expired`

            Expired records whether the milestone is past its due date. It is needed to distinguish Merge Requests rows by the exact GitLab-returned expired value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-group-id-aa11a5151e87" title="Group ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.group_id`

            Group ID records ID of the group the milestone belongs to (for group milestones). It is needed to refer to the same group across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-id-92661ab25c73" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.id`

            ID records global milestone ID. It is needed to refer to the same milestone across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-iid-4cecc6292f07" title="Iid" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.iid`

            Iid records project-scoped milestone ID. It is needed to refer to the same iid across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-project-id-a208b42af962" title="Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.project_id`

            Project ID records ID of the project the milestone belongs to. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-start-date-1f9779e7c2a2" title="Start Date" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.start_date`

            Start Date records start date for the milestone. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-state-46ceadb07db0" title="State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.state`

            State records milestone state (active or closed). It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-title-9304456455c1" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.title`

            Title records milestone title. It is needed to inspect the exact title text included with this record.

            * **Enables:** inspect the title text returned in `title` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the Milestone object returned for Merge Requests; it is title text at one Milestone record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-updated-at-6fa2dec540f1" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.updated_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-milestone-web-url-1378e4058aed" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.milestone.web_url`

            Web URL records URL to view the milestone in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-overflow-857acfc5798e" title="Overflow" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.overflow`

            Overflow records whether the diff is too large to display. It is needed to distinguish Merge Requests rows by the exact GitLab-returned overflow value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-pipeline-410aeac7918e" title="Pipeline" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.pipeline`

            Pipeline records latest pipeline associated with the MR. It is needed to preserve the nested pipeline relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `pipeline` to connect the containing GitLab Merge Request row to its returned pipeline entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-prepared-at-f3ce0ec381ba" title="Prepared At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.prepared_at`

            Prepared At records timestamp when the MR was marked as prepared. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-project-id-e6d2cae1602d" title="Project ID" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.project_id`

            Project ID records ID of the project this merge request belongs to. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-rebase-in-progress-7305b2829c40" title="Rebase In Progress" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.rebase_in_progress`

            Rebase In Progress records whether a rebase operation is currently in progress. It is needed to distinguish Merge Requests rows by the exact GitLab-returned rebase in progress value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-reference-04f2bd853f20" title="Reference" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.reference`

            Reference records short reference string for the MR (e.g., !123). It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-references-fef11fe2137f" title="References" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.references`

            References records short and full reference strings for the MR. It is needed to preserve the nested references relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `references` to connect the containing GitLab Merge Request row to its returned references entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-references-full-91d2722d8061" title="Full" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.references.full`

            Full records full reference including namespace and project path. It is needed to compare the returned full for individual Merge Requests rows and select rows with a specific `full` value.

            * **Enables:** trace the full relationship returned in `full` from the References row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the References object returned for Merge Requests; it is interpreted at one References record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-references-relative-57c87732c3a9" title="Relative" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.references.relative`

            Relative records relative reference including project path. It is needed to compare the returned relative for individual Merge Requests rows and select rows with a specific `relative` value.

            * **Enables:** trace the relative relationship returned in `relative` from the References row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the References object returned for Merge Requests; it is interpreted at one References record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-references-short-02c525308738" title="Short" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.references.short`

            Short records short reference (e.g., !123). It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-reviewers-5c2d45807a15" title="Reviewers" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.reviewers`

            Reviewers records array of users designated as reviewers. It is needed to preserve the nested reviewers relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `reviewers` to connect the containing GitLab Merge Request row to its returned reviewers entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one returned collection per containing GitLab Merge Request object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-sha-d1cbfec1b2c2" title="Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.sha`

            Sha records SHA of the latest commit on the source branch at the head of the MR. It is needed to refer to the same merge request across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-should-remove-source-branc-0a6c0422fdbd" title="Should Remove Source Branch" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.should_remove_source_branch`

            Should Remove Source Branch records whether the source branch should be deleted after merge. It is needed to distinguish Merge Requests rows by the exact GitLab-returned should remove source branch value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-source-branch-6aa1cea879c4" title="Source Branch" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.source_branch`

            Source Branch records name of the source branch. It is needed to distinguish Merge Requests rows by the exact GitLab-returned source branch value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-source-project-id-71b014a0aa01" title="Source Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.source_project_id`

            Source Project ID records ID of the source project (may differ from `project_id` for cross-project MRs). It is needed to refer to the same source project across records without relying on display text.

            * **Enables:** match `source_project_id` to source project references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-squash-8dc842b857de" title="Squash" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.squash`

            Squash records whether commits will be squashed on merge. It is needed to distinguish Merge Requests rows by the exact GitLab-returned squash value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-squash-commit-sha-e861e0e1c09f" title="Squash Commit Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.squash_commit_sha`

            Squash Commit Sha records SHA of the squash commit, null if squash was not used. It is needed to refer to the same squash commit across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-squash-on-merge-bb52207bac77" title="Squash On Merge" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.squash_on_merge`

            Squash On Merge records whether squash on merge is enabled. It is needed to distinguish Merge Requests rows by the exact GitLab-returned squash on merge value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-state-6efb155af47c" title="State" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.state`

            State records current state of the merge request. It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-target-branch-b74fdcf0456b" title="Target Branch" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.target_branch`

            Target Branch records name of the target branch. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-target-project-id-38263a7f326e" title="Target Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.target_project_id`

            Target Project ID records ID of the target project. It is needed to refer to the same target project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-task-completion-status-829371d73b52" title="Task Completion Status" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.task_completion_status`

            Task Completion Status records completion status of tasks/checklists in the MR description. It is needed to preserve the nested task completion status relationship or details on the parent GitLab Merge Request record.

            * **Enables:** expand `task_completion_status` to connect the containing GitLab Merge Request row to its returned task completion status entries.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-task-completion-status-com-a07dd1f78b8f" title="Completed Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.task_completion_status.completed_count`

            Completed Count records number of completed tasks. It is needed to measure the GitLab-reported number of completed tasks at one Task Completion Status record per row.

            * **Enables:** measure and compare the GitLab-reported number of completed tasks in `completed_count` at one Task Completion Status record per row.
            * **Interpretation:** GitLab reports this value on the Task Completion Status object returned for Merge Requests; it is a GitLab-reported count at one Task Completion Status record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-task-completion-status-cou-0978d3fc7a7c" title="Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.task_completion_status.count`

            Count records total number of tasks. It is needed to measure the GitLab-reported number of tasks at one Task Completion Status record per row.

            * **Enables:** measure and compare the GitLab-reported number of tasks in `count` at one Task Completion Status record per row.
            * **Interpretation:** GitLab reports this value on the Task Completion Status object returned for Merge Requests; it is a GitLab-reported count at one Task Completion Status record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-time-stats-3e08bddc77fa" title="Time Stats" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.time_stats`

            Time Stats records time tracking statistics for the MR. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Merge Requests records by `time_stats`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-time-stats-human-time-esti-d79ed262ab1e" title="Human Time Estimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.time_stats.human_time_estimate`

            Human Time Estimate records human-readable estimated time (e.g., '3h 30m'). It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-time-stats-human-total-tim-a797aafa8b64" title="Human Total Time Spent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.time_stats.human_total_time_spent`

            Human Total Time Spent records human-readable total time spent. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-time-stats-time-estimate-3e2426a4ed87" title="Time Estimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.time_stats.time_estimate`

            Time Estimate records estimated time in seconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Merge Requests records by `time_estimate`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab reports this value on the Time Stats object returned for Merge Requests; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-time-stats-total-time-spen-51b765254125" title="Total Time Spent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.time_stats.total_time_spent`

            Total Time Spent records total time spent in seconds. It is needed to place the record at the time or date reported for this event or state.

            * **Enables:** bound Merge Requests records by `total_time_spent`, order their returned events or state changes, and correlate records reported at the same time.
            * **Interpretation:** GitLab reports this value on the Time Stats object returned for Merge Requests; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-title-9406eeeebe90" title="Title" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.title`

            Title records merge request title. It is needed to inspect the exact title text included with this record.

            * **Enables:** inspect the title text returned in `title` and attribute it to the same record's repository or project, work-item number, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is title text at one GitLab Merge Request record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-updated-at-649d6239dc2e" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.updated_at`

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

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-upvotes-be2482019d8f" title="Upvotes" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.upvotes`

            Upvotes records number of upvote (thumbs up) reactions. It is needed to measure the GitLab-reported number of upvote (thumbs up) reactions at one GitLab Merge Request record per row.

            * **Enables:** measure and compare the GitLab-reported number of upvote (thumbs up) reactions in `upvotes` at one GitLab Merge Request record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-user-notes-count-a0586a2f8068" title="User Notes Count" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.user_notes_count`

            User Notes Count records number of user-created notes (comments) on the MR. It is needed to measure the GitLab-reported number of user-created notes (comments) on the MR at one GitLab Merge Request record per row.

            * **Enables:** measure and compare the GitLab-reported number of user-created notes (comments) on the MR in `user_notes_count` at one GitLab Merge Request record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-merge-requests-web-url-8ea340055fdb" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.web_url`

            Web URL records URL to view the merge request in the GitLab web UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-merge-requests-work-in-progress-c58639ba0a07" title="Work In Progress" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `merge_requests.work_in_progress`

            Work In Progress records deprecated alias for draft. It is needed to distinguish Merge Requests rows by the exact GitLab-returned work in progress value.

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

      <Accordion id="provider-permission-tap-gitlab-pipelines-0929d9125256" title="Pipelines" icon="route" iconType="sharp-duotone-solid">
        Developer identifier: `pipelines`

        Pipelines covers project CI/CD pipelines.

        * **Enables:** trace each returned CI/CD pipeline to its project, revision, trigger source, status, user, and timing values.
        * **Scope:** Project CI/CD pipelines; the connector reads `/api/v4/projects/{id}/pipelines` as a changelog stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-pipelines-before-sha-8716c44a1094" title="Before Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.before_sha`

            Before Sha records SHA of the commit just before the pipeline source commit. It is needed to refer to the same before across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-committed-at-2a9f2ee44176" title="Committed At" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.committed_at`

            Committed At records timestamp of the commit that triggered the pipeline. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-coverage-ef584ef98193" title="Coverage" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.coverage`

            Coverage records code coverage percentage reported by the pipeline. It is needed to measure the code-coverage percentage reported for this pipeline execution.

            * **Enables:** compare `coverage` at one pipeline grain while preserving the project, revision, and pipeline identifiers.
            * **Interpretation:** GitLab reports this value on the GitLab Pipeline object returned for Pipelines; its unit or granularity is percent; the value is a GitLab-reported percentage string and does not by itself establish test quality or change causality.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-pipelines-created-at-96b62c4d9795" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-pipelines-duration-5146f0b67149" title="Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.duration`

            Duration records total duration of the pipeline in seconds (wall time from start to finish). It is needed to measure the exact duration reported for one GitLab Pipeline record using the GitLab duration encoding described by the field.

            * **Enables:** measure and compare `duration` per GitLab Pipeline record in seconds.
            * **Interpretation:** GitLab reports this value on the GitLab Pipeline object returned for Pipelines; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-pipelines-finished-at-5a7207d97b2f" title="Finished At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.finished_at`

            Finished At records timestamp when the pipeline finished. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-id-1fe05e608935" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.id`

            ID records unique numeric identifier for the pipeline. It is needed to distinguish repeated deliveries of the same Pipelines row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-iid-061f7cbd11fc" title="Iid" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.iid`

            Iid records project-scoped pipeline number, human-readable reference. It is needed to refer to the same iid across records without relying on display text.

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

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

            Name records name of the pipeline, if set via workflow:name in CI config. It is needed to compare the exact name configuration returned for this GitLab Pipeline record.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-project-id-566cedde0451" title="Project ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.project_id`

            Project ID records ID of the project this pipeline belongs to. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-queued-duration-82905a1dd3c0" title="Queued Duration" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.queued_duration`

            Queued Duration records total time in seconds the pipeline spent queued before running. It is needed to measure the exact duration reported for one GitLab Pipeline record using the GitLab duration encoding described by the field.

            * **Enables:** measure and compare `queued_duration` per GitLab Pipeline record in seconds.
            * **Interpretation:** GitLab reports this value on the GitLab Pipeline object returned for Pipelines; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-pipelines-ref-aa8bcca9eef1" title="Ref" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.ref`

            Ref records branch or tag name that triggered the pipeline. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-sha-d4dfc3c2b4ac" title="Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.sha`

            Sha records full commit SHA that triggered the pipeline. It is needed to refer to the same pipeline across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-source-ceec23fefb24" title="Source" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.source`

            Source records what triggered the pipeline. It is needed to distinguish Pipelines rows by the exact GitLab-returned source value.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-started-at-c6668cc17ef1" title="Started At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.started_at`

            Started At records timestamp when the pipeline started running. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-status-ed31594574a0" title="Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.status`

            Status records current status of the pipeline. It is needed to distinguish Pipelines rows by the exact GitLab-returned status value.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-tag-cdc854607853" title="Tag" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.tag`

            Tag records whether the pipeline was triggered by a tag. It is needed to distinguish Pipelines rows by the exact GitLab-returned tag value.

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

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

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

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

          <Accordion id="provider-permission-field-gitlab-pipelines-user-11d987b44e3c" title="User" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user`

            User records the user who triggered the pipeline. It is needed to preserve the nested user relationship or details on the parent GitLab Pipeline record.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-user-avatar-url-babf56e55f65" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.avatar_url`

            Avatar URL records URL to the user's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-user-id-a8a0ceccf874" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.id`

            ID records unique numeric identifier of the user. It is needed to refer to the same pipeline user across records without relying on display text.

            * **Enables:** match `id` to pipeline user references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Pipeline User object returned for Pipelines; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-pipelines-user-locked-d78d0d9f73e6" title="Locked" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.locked`

            Locked records whether the user account is locked. It is needed to distinguish Pipelines rows by the exact GitLab-returned locked value.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-user-name-aefde524aeea" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.name`

            Name records display name of the user. It is needed to attribute this Pipelines row to the returned person, account, or organization reference.

            * **Enables:** attribute the Pipelines row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the Pipeline User object returned for Pipelines; it is interpreted at one Pipeline User record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-pipelines-user-state-ee9735f70987" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.state`

            State records account state of the user (e.g., active, blocked). It is needed to distinguish Pipelines rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-user-username-54adddb50b30" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.username`

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

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

          <Accordion id="provider-permission-field-gitlab-pipelines-user-web-url-3996c417ffa9" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.user.web_url`

            Web URL records URL to the user's GitLab profile page. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-web-url-a054d4af6857" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.web_url`

            Web URL records URL to view the pipeline in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-pipelines-yaml-errors-906e3c5325aa" title="Yaml Errors" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `pipelines.yaml_errors`

            Yaml Errors records errors found in the CI YAML configuration, if any. It is needed to compare the exact yaml errors configuration returned for this GitLab Pipeline record.

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

      <Accordion id="provider-permission-tap-gitlab-project-commits-dfcb8980aeaa" title="Project Commits" icon="code-commit" iconType="sharp-duotone-solid">
        Developer identifier: `project_commits`

        Project Commits covers project repository commits.

        * **Enables:** trace each returned revision to its repository or project, author and committer identities, message, and provider-reported commit times.
        * **Scope:** Project repository commits; the connector reads `/api/v4/projects/{id}/repository/commits` as an event stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-project-commits-author-email-f84422d10ebd" title="Author Email" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.author_email`

            Author Email records email of the commit author. Used for cross-system identity resolution. It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-author-name-8ce66bf29235" title="Author Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.author_name`

            Author Name records name of the commit author as recorded in Git. It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-authored-date-c1f11200f8e5" title="Authored Date" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.authored_date`

            Authored Date records timestamp when the commit was originally authored. Tracks when code was actually written. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-committed-date-5ac7ff8cfa4b" title="Committed Date" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.committed_date`

            Committed Date records timestamp when the commit was committed. Used as incremental sync cursor and activity timeline signal. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-committer-email-17b021c436ba" title="Committer Email" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.committer_email`

            Committer Email records email of the committer. It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-committer-name-cd2bcb2d426c" title="Committer Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.committer_name`

            Committer Name records name of the person who committed the code (may differ from author in rebases/cherry-picks). It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-created-at-34320abf747a" title="Created At" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-project-commits-extended-trailers-16410d63abbd" title="Extended Trailers" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.extended_trailers`

            Extended Trailers records extended Git trailers from the commit message, supporting multiple values per key. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `extended_trailers` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; the schema uses the `Generic.JSON` scalar; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-id-e1cc8ff01dd8" title="ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.id`

            ID records full SHA hash of the commit. Primary key for commit-level attribution and cross-referencing. It is needed to distinguish repeated deliveries of the same Project Commits row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-faea46f0c71a" title="Last Pipeline" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline`

            Last Pipeline records summary of the last CI/CD pipeline that ran for this commit. It is needed to preserve the nested last pipeline relationship or details on the parent GitLab Project Commit record.

            * **Enables:** expand `last_pipeline` to connect the containing GitLab Project Commit row to its returned last pipeline entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is one nested object per containing GitLab Project Commit object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-created-at-9cbe60723b6d" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-id-fd514e4d1f15" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.id`

            ID records numeric ID of the pipeline. It is needed to refer to the same commit pipeline across records without relying on display text.

            * **Enables:** match `id` to commit pipeline references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-ref-3c043ccc27e1" title="Ref" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.ref`

            Ref records branch or tag name that triggered the pipeline. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-sha-b9d92eb9c84b" title="Sha" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.sha`

            Sha records SHA of the commit the pipeline ran against. It is needed to refer to the same commit pipeline across records without relying on display text.

            * **Enables:** match `sha` to commit pipeline references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-status-433f02427ecb" title="Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.status`

            Status records current status of the pipeline. It is needed to distinguish Project Commits rows by the exact GitLab-returned status value.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-updated-at-f1a800f2e8d0" title="Updated At" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.updated_at`

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

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

          <Accordion id="provider-permission-field-gitlab-project-commits-last-pipeline-web-url-310781d1cdf9" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.last_pipeline.web_url`

            Web URL records URL to view the pipeline in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-message-12923ae1a48c" title="Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.message`

            Message records full commit message including title and body. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `message` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-parent-ids-379082e9405b" title="Parent IDs" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.parent_ids`

            Parent IDs records array of parent commit SHA hashes. Merge commits will have multiple parents. It is needed to preserve the nested parent i ds relationship or details on the parent GitLab Project Commit record.

            * **Enables:** expand `parent_ids` to connect the containing GitLab Project Commit row to its returned parent i ds entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is one returned collection per containing GitLab Project Commit object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-project-id-c47fb0977f41" title="Project ID" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.project_id`

            Project ID records parent project id injected by the ingestor when iterating per-project (from the (id) path parameter in the `project_commits` endpoint). Not part of the upstream GitLab API response; written into each row at bronze ingestion time. It is needed to refer to the same project across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-short-id-fb14812abcba" title="Short ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.short_id`

            Short ID records short SHA hash of the commit, typically 8 characters. Human-readable commit reference. It is needed to refer to the same short across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-stats-5c6adf67e4e9" title="Stats" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.stats`

            Stats records diff statistics for the commit including lines added, deleted, and total changes. Only present when `with_stats`=true. It is needed to preserve the nested stats relationship or details on the parent GitLab Project Commit record.

            * **Enables:** expand `stats` to connect the containing GitLab Project Commit row to its returned stats entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is one nested object per containing GitLab Project Commit object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-stats-additions-a07f9466d45f" title="Additions" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.stats.additions`

            Additions records number of lines added in this commit. Quantifies code contribution volume. It is needed to measure the GitLab-reported number of lines added in this commit. Quantifies code contribution volume at one Commit Stats record per row.

            * **Enables:** measure and compare the GitLab-reported number of lines added in this commit. Quantifies code contribution volume in `additions` at one Commit Stats record per row.
            * **Interpretation:** GitLab reports this value on the Commit Stats object returned for Project Commits; it is a GitLab-reported count at one Commit Stats record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-stats-deletions-78544d9ceed5" title="Deletions" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.stats.deletions`

            Deletions records number of lines deleted in this commit. It is needed to measure the GitLab-reported number of lines deleted in this commit at one Commit Stats record per row.

            * **Enables:** measure and compare the GitLab-reported number of lines deleted in this commit in `deletions` at one Commit Stats record per row.
            * **Interpretation:** GitLab reports this value on the Commit Stats object returned for Project Commits; it is a GitLab-reported count at one Commit Stats record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-stats-total-95a8e1259f8a" title="Total" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.stats.total`

            Total records total number of lines changed (additions + deletions). It is needed to measure the GitLab-reported number of lines changed (additions + deletions) at one Commit Stats record per row.

            * **Enables:** measure and compare the GitLab-reported number of lines changed (additions + deletions) in `total` at one Commit Stats record per row.
            * **Interpretation:** GitLab reports this value on the Commit Stats object returned for Project Commits; it is a GitLab-reported count at one Commit Stats record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-status-1c3791862470" title="Status" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.status`

            Status records status of the latest pipeline associated with this commit, if any. It is needed to distinguish Project Commits rows by the exact GitLab-returned status value.

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

          <Accordion id="provider-permission-field-gitlab-project-commits-title-7372e08471d0" title="Title" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.title`

            Title records first line of the commit message. Enables commit message analysis for work categorization. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `title` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-trailers-bf2483587c33" title="Trailers" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.trailers`

            Trailers records git trailers parsed from the commit message as key-value pairs (e.g., Signed-off-by, Co-authored-by). It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `trailers` and attribute it to the same record's repository or project, revision, author, and timestamp where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; the schema uses the `Generic.JSON` scalar; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-commits-web-url-c08082af6b59" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `project_commits.web_url`

            Web URL records URL to view the commit in the GitLab web interface. It is needed to inspect the exact link included with this record.

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

      <Accordion id="provider-permission-tap-gitlab-project-members-f0b0f8652f8d" title="Project Members" icon="people-group" iconType="sharp-duotone-solid">
        Developer identifier: `project_members`

        Project Members covers members of a project (including inherited members).

        * **Enables:** map the GitLab accounts and memberships represented by Project Members records and trace a returned access assignment to its account or group.
        * **Scope:** Members of a project (including inherited members); the connector reads `/api/v4/projects/{id}/members/all` as a snapshot stream in full mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-project-members-access-level-22a59b69109f" title="Access Level" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.access_level`

            Access Level records permission level granted to the member (10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-project-members-avatar-url-59acdaf389e6" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.avatar_url`

            Avatar URL records URL to the member's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-project-members-created-at-5f8ee1186aa0" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_at`

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

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

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-bffdf1b8b37b" title="Created By" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by`

            Created By records user who added this member to the project. It is needed to preserve the nested created by relationship or details on the parent GitLab Project Member record.

            * **Enables:** expand `created_by` to connect the containing GitLab Project Member row to its returned created by entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Member object returned for Project Members; it is one nested object per containing GitLab Project Member object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-avatar-url-6eda83445aa3" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by.avatar_url`

            Avatar URL records URL to the creator's avatar image. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-id-85f477823d5d" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by.id`

            ID records user ID of the creator. It is needed to refer to the same member created by across records without relying on display text.

            * **Enables:** match `id` to member created by references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Member Created By object returned for Project Members; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-name-fb6ca467890e" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by.name`

            Name records display name of the creator. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

            * **Enables:** attribute the Project Members row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the Member Created By object returned for Project Members; it is interpreted at one Member Created By record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-state-7610eec74131" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by.state`

            State records account state of the creator. It is needed to distinguish Project Members rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-username-fe4f435cfef5" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by.username`

            User Name records GitLab username of the creator. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-members-created-by-web-url-d6b77b3120d9" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.created_by.web_url`

            Web URL records URL to the creator's GitLab profile page. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-project-members-email-f42808385fb5" title="Email" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.email`

            Email records email address of the member, if visible. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-members-expires-at-301f0d6bbb9b" title="Expires At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.expires_at`

            Expires At records membership expiration date if set (YYYY-MM-DD format). It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-project-members-group-saml-identity-8ce61ec3c50c" title="Group SAML Identity" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.group_saml_identity`

            Group SAML Identity records SAML identity information if the member authenticated via group SAML. It is needed to preserve the nested group saml identity relationship or details on the parent GitLab Project Member record.

            * **Enables:** expand `group_saml_identity` to connect the containing GitLab Project Member row to its returned group saml identity entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project Member object returned for Project Members; it is one nested object per containing GitLab Project Member object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-group-saml-identity-exter-16039f55a58a" title="Extern Uid" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.group_saml_identity.extern_uid`

            Extern Uid records external UID from the SAML identity provider. It is needed to refer to the same extern uid across records without relying on display text.

            * **Enables:** match `extern_uid` to extern uid references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Group Saml Identity object returned for Project Members; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-group-saml-identity-provi-5ec587c557cf" title="Provider" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.group_saml_identity.provider`

            Provider records name of the SAML identity provider. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

            * **Enables:** compare `provider` among Project Members records when reconciling this specific configuration, source, or classification.
            * **Interpretation:** GitLab reports this value on the Group Saml Identity object returned for Project Members; it is interpreted at one Group Saml Identity record per row; the value is a GitLab-returned or configured label at the Group Saml Identity grain rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-group-saml-identity-saml--4cb4a86de954" title="SAML Provider ID" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.group_saml_identity.saml_provider_id`

            SAML Provider ID records ID of the SAML provider configuration. It is needed to refer to the same saml provider across records without relying on display text.

            * **Enables:** match `saml_provider_id` to saml provider references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the Group Saml Identity object returned for Project Members; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-id-48b377022b4f" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.id`

            ID records user ID of the member. It is needed to distinguish repeated deliveries of the same Project Members row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-project-members-is-using-seat-4dbf5b7e002a" title="Is Using Seat" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.is_using_seat`

            Is Using Seat records whether the member is using a license seat. It is needed to distinguish Project Members rows by the exact GitLab-returned is using seat value.

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

          <Accordion id="provider-permission-field-gitlab-project-members-membership-state-fd7becd87183" title="Membership State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.membership_state`

            Membership State records state of the membership (active, awaiting, etc.). It is needed to distinguish Project Members rows by the exact GitLab-returned membership state value.

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

          <Accordion id="provider-permission-field-gitlab-project-members-name-4fa9512bea04" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.name`

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

            * **Enables:** attribute the Project Members row to the returned person or account and match the exact `name` value where it recurs in GitLab.
            * **Interpretation:** GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; the schema uses the `Identity.Name` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-project-members-state-0e537dd1aec5" title="State" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.state`

            State records account state of the user (active, blocked, etc.). It is needed to distinguish Project Members rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-project-members-username-3a71d9519cb4" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.username`

            User Name records GitLab username of the member. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-project-members-web-url-264f8b3bdfc0" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `project_members.web_url`

            Web URL records URL to the member's GitLab profile page. It is needed to inspect the exact link included with this record.

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

      <Accordion id="provider-permission-tap-gitlab-projects-e0a663c517d9" title="Projects" icon="sitemap" iconType="sharp-duotone-solid">
        Developer identifier: `projects`

        Projects covers GitLab projects the authenticated user is a member of.

        * **Enables:** inventory returned projects and correlate each project with its namespace, owner, visibility, default branch, and last reported update.
        * **Scope:** GitLab projects the authenticated user is a member of; the connector reads `/api/v4/projects` as a snapshot stream in incremental mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

        Provider-defined fields may also be returned for this data stream.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-projects-links-003913d45ab5" title="Links" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links`

            Links records hypermedia links for the project. GitLab returns this object under the \_links key; the whole object was dropped when declared as links. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact GitLab resource referenced by `_links` while retaining the containing Projects record as provenance.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is link at one GitLab Project record per row; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-links-cluster-agents-915335c7b8e8" title="Cluster Agents" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.cluster_agents`

            Cluster Agents records API URL for cluster agents. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-links-events-569932997f92" title="Events" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.events`

            Events records API URL for project events. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-links-issues-b81fad7f4d96" title="Issues" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.issues`

            Issues records API URL for project issues. It is needed to inspect the exact link included with this record.

            * **Enables:** open or correlate the exact GitLab resource referenced by `issues` while retaining the containing Projects record as provenance.
            * **Interpretation:** GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-links-labels-dda4ec80155a" title="Labels" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.labels`

            Labels records API URL for project labels. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-links-members-71674835ecb6" title="Members" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.members`

            Members records API URL for project members. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-links-merge-requests-fcfcc2213d5f" title="Merge Requests" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.merge_requests`

            Merge Requests records API URL for project merge requests. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-links-repo-branches-af45f123306a" title="Repo Branches" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.repo_branches`

            Repo Branches records API URL for repository branches. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-links-self-f24ad7dcd2fc" title="Self" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects._links.self`

            Self records API URL for this project. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-allow-merge-on-skipped-pipeline-73c6fd6d7a00" title="Allow Merge On Skipped Pipeline" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.allow_merge_on_skipped_pipeline`

            Allow Merge On Skipped Pipeline records whether merges are allowed when the pipeline is skipped. It is needed to distinguish Projects rows by the exact GitLab-returned allow merge on skipped pipeline value.

            * **Enables:** select Projects rows where `allow_merge_on_skipped_pipeline` is true or false when comparing the condition described by Allow Merge On Skipped Pipeline.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-analytics-access-level-2b8057f8407f" title="Analytics Access Level" icon="chart-column" iconType="sharp-duotone-solid">
            Developer identifier: `projects.analytics_access_level`

            Analytics Access Level records access level for analytics. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-archived-4ab4bf171a43" title="Archived" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archived`

            Archived records whether the project is archived. It is needed to distinguish Projects rows by the exact GitLab-returned archived value.

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

          <Accordion id="provider-permission-field-gitlab-projects-auto-cancel-pending-pipelines-36f4e7725393" title="Auto Cancel Pending Pipelines" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.auto_cancel_pending_pipelines`

            Auto Cancel Pending Pipelines records whether pending pipelines are auto-cancelled. It is needed to distinguish Projects rows by the exact GitLab-returned auto cancel pending pipelines value.

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

          <Accordion id="provider-permission-field-gitlab-projects-auto-devops-deploy-strategy-667b3e359359" title="Auto Devops Deploy Strategy" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.auto_devops_deploy_strategy`

            Auto Devops Deploy Strategy records auto DevOps deployment strategy. It is needed to distinguish Projects rows by the exact GitLab-returned auto devops deploy strategy value.

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

          <Accordion id="provider-permission-field-gitlab-projects-auto-devops-enabled-5c0e546249b8" title="Auto Devops Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.auto_devops_enabled`

            Auto Devops Enabled records whether Auto DevOps is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned auto devops enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-autoclose-referenced-issues-1f323a4723ab" title="Autoclose Referenced Issues" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.autoclose_referenced_issues`

            Autoclose Referenced Issues records whether referenced issues are automatically closed on merge. It is needed to distinguish Projects rows by the exact GitLab-returned autoclose referenced issues value.

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

          <Accordion id="provider-permission-field-gitlab-projects-avatar-url-bb445b30567c" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.avatar_url`

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

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

          <Accordion id="provider-permission-field-gitlab-projects-build-coverage-regex-4d64c2e2ce38" title="Build Coverage Regex" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `projects.build_coverage_regex`

            Build Coverage Regex records regex for extracting code coverage from build output. It is needed to measure the code-coverage percentage reported for this pipeline execution.

            * **Enables:** compare `build_coverage_regex` at one pipeline grain while preserving the project, revision, and pipeline identifiers.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the value is a GitLab-reported percentage string and does not by itself establish test quality or change causality.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-build-git-strategy-297ffa49497c" title="Build Git Strategy" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `projects.build_git_strategy`

            Build Git Strategy records git strategy for CI/CD builds (fetch or clone). It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

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

          <Accordion id="provider-permission-field-gitlab-projects-build-timeout-7e7be64c095d" title="Build Timeout" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.build_timeout`

            Build Timeout records CI/CD build timeout in seconds. It is needed to measure the reported build timeout for one gitlab project record.

            * **Enables:** measure and compare `build_timeout` per GitLab Project record in seconds.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; its unit or granularity is seconds.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-builds-access-level-e0897cf9a02f" title="Builds Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.builds_access_level`

            Builds Access Level records access level for CI/CD builds. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-can-create-merge-request-in-3cb5e9c318b6" title="Can Create Merge Request In" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.can_create_merge_request_in`

            Can Create Merge Request In records whether the current user can create merge requests in this project. It is needed to distinguish Projects rows by the exact GitLab-returned can create merge request in value.

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

          <Accordion id="provider-permission-field-gitlab-projects-ci-allow-fork-pipelines-to-run-i-adb742b8dd02" title="Ci Allow Fork Pipelines To Run In Parent Project" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_allow_fork_pipelines_to_run_in_parent_project`

            Ci Allow Fork Pipelines To Run In Parent Project records whether fork pipelines can run in the parent project. It is needed to distinguish Projects rows by the exact GitLab-returned ci allow fork pipelines to run in parent project value.

            * **Enables:** select Projects rows where `ci_allow_fork_pipelines_to_run_in_parent_project` is true or false when comparing the condition described by Ci Allow Fork Pipelines To Run In Parent Project.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-ci-config-path-89e905ec28dc" title="Ci Config Path" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_config_path`

            Ci Config Path records path to the CI/CD configuration file. It is needed to compare the exact ci config path configuration returned for this GitLab Project record.

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

          <Accordion id="provider-permission-field-gitlab-projects-ci-default-git-depth-1b10c6d465ad" title="Ci Default Git Depth" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_default_git_depth`

            Ci Default Git Depth records default git depth for CI/CD pipelines. It is needed to distinguish Projects rows by the exact GitLab-returned ci default git depth value.

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

          <Accordion id="provider-permission-field-gitlab-projects-ci-forward-deployment-enabled-e2f18064ce0d" title="Ci Forward Deployment Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_forward_deployment_enabled`

            Ci Forward Deployment Enabled records whether forward deployment is enabled for CI/CD. It is needed to distinguish Projects rows by the exact GitLab-returned ci forward deployment enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-ci-forward-deployment-rollback-a-939c4561fb62" title="Ci Forward Deployment Rollback Allowed" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_forward_deployment_rollback_allowed`

            Ci Forward Deployment Rollback Allowed records whether rollback is allowed for forward deployments. It is needed to distinguish Projects rows by the exact GitLab-returned ci forward deployment rollback allowed value.

            * **Enables:** select Projects rows where `ci_forward_deployment_rollback_allowed` is true or false when comparing the condition described by Ci Forward Deployment Rollback Allowed.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-ci-job-token-scope-enabled-7a44fd3253ef" title="Ci Job Token Scope Enabled" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_job_token_scope_enabled`

            Ci Job Token Scope Enabled records whether CI job token scope is enabled. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-ci-restrict-pipeline-cancellatio-217f594f4d6d" title="Ci Restrict Pipeline Cancellation Role" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_restrict_pipeline_cancellation_role`

            Ci Restrict Pipeline Cancellation Role records role required to cancel pipelines. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-ci-separated-caches-ef12602322a4" title="Ci Separated Caches" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ci_separated_caches`

            Ci Separated Caches records whether CI/CD caches are separated by ref. It is needed to distinguish Projects rows by the exact GitLab-returned ci separated caches value.

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

          <Accordion id="provider-permission-field-gitlab-projects-compliance-frameworks-183076616af8" title="Compliance Frameworks" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `projects.compliance_frameworks`

            Compliance Frameworks records compliance frameworks applied to the project. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `compliance_frameworks` to examine the returned compliance frameworks details for the containing GitLab Project record.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; a returned framework label or feature setting does not demonstrate that a framework requirement is satisfied.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-container-registry-access-level-6438c4786619" title="Container Registry Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.container_registry_access_level`

            Container Registry Access Level records access level for the container registry. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-container-registry-enabled-c42f875eff38" title="Container Registry Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.container_registry_enabled`

            Container Registry Enabled records whether the container registry is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned container registry enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-container-registry-image-prefix-351b6becb6d8" title="Container Registry Image Prefix" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `projects.container_registry_image_prefix`

            Container Registry Image Prefix records prefix for container registry images. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

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

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

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

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

          <Accordion id="provider-permission-field-gitlab-projects-creator-id-46a59b85d563" title="Creator ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.creator_id`

            Creator ID records user ID of the project creator. It is needed to refer to the same creator across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-projects-default-branch-7777377cbc9d" title="Default Branch" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.default_branch`

            Default Branch records name of the default branch (e.g., main, master). It is needed to distinguish Projects rows by the exact GitLab-returned default branch value.

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

          <Accordion id="provider-permission-field-gitlab-projects-description-cdc12c971028" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.description`

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

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is description text at one GitLab Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-description-html-57db11fef7d9" title="Description HTML" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.description_html`

            Description HTML records HTML-rendered project description. It is needed to inspect the exact description text included with this record.

            * **Enables:** inspect the description text returned in `description_html` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is description text at one GitLab Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-emails-disabled-ca63b95c964d" title="Emails Disabled" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `projects.emails_disabled`

            Emails Disabled records whether email notifications are disabled. It is needed to distinguish Projects rows by the exact GitLab-returned emails disabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-emails-enabled-4bf69034c6ed" title="Emails Enabled" icon="envelope" iconType="sharp-duotone-solid">
            Developer identifier: `projects.emails_enabled`

            Emails Enabled records whether email notifications are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned emails enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-empty-repo-f3b72a37702c" title="Empty Repo" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.empty_repo`

            Empty Repo records whether the repository is empty (no commits). It is needed to distinguish Projects rows by the exact GitLab-returned empty repo value.

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

          <Accordion id="provider-permission-field-gitlab-projects-enforce-auth-checks-on-uploads-45677845868f" title="Enforce Auth Checks On Uploads" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.enforce_auth_checks_on_uploads`

            Enforce Auth Checks On Uploads records whether authorization checks are enforced on file uploads. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-environments-access-level-ac1f34891de3" title="Environments Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.environments_access_level`

            Environments Access Level records access level for environments. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-external-authorization-classific-957ff1b6fe54" title="External Authorization Classification Label" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.external_authorization_classification_label`

            External Authorization Classification Label records classification label used for external authorization. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-feature-flags-access-level-24801813b3a2" title="Feature Flags Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.feature_flags_access_level`

            Feature Flags Access Level records access level for feature flags. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-97f9dbc98d25" title="Forked From Project" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project`

            Forked From Project records the project this was forked from, if applicable. It is needed to preserve the nested forked from project relationship or details on the parent GitLab Project record.

            * **Enables:** expand `forked_from_project` to connect the containing GitLab Project row to its returned forked from project entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is one nested object per containing GitLab Project object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-avatar-url-c3c2f4843baa" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.avatar_url`

            Avatar URL records avatar URL of the upstream project. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-created-at-d84d4f7dc231" title="Created At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.created_at`

            Created At records creation timestamp of the upstream project. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-default-bran-89783ba122ac" title="Default Branch" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.default_branch`

            Default Branch records default branch of the upstream project. It is needed to distinguish Projects rows by the exact GitLab-returned default branch value.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-description-512d9345b07c" title="Description" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.description`

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

            * **Enables:** inspect the description text returned in `description` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is description text at one GitLab Forked From Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-forks-count-e6ae029cc7a6" title="Forks Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.forks_count`

            Forks Count records fork count of the upstream project. It is needed to measure the GitLab-reported number of forks at one GitLab Forked From Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of forks in `forks_count` at one GitLab Forked From Project record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is a GitLab-reported count at one GitLab Forked From Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-http-url-to--6b7b4f109b6e" title="HTTP URL To Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.http_url_to_repo`

            HTTP URL To Repo records HTTP clone URL of the upstream project. It is needed to reproduce the returned code or dependency configuration for this Projects record.

            * **Enables:** use `http_url_to_repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-id-b0794176aaf0" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.id`

            ID records ID of the upstream project. It is needed to refer to the same forked from project across records without relying on display text.

            * **Enables:** match `id` to forked from project references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-last-activit-b3aee320c795" title="Last Activity At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.last_activity_at`

            Last Activity At records last activity timestamp of the upstream project. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-name-a1f869e0070a" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.name`

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

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-name-with-na-c98805323877" title="Name With Namespace" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.name_with_namespace`

            Name With Namespace records full name with namespace of the upstream project. It is needed to compare the returned name with namespace for individual Projects rows and select rows with a specific `name_with_namespace` value.

            * **Enables:** locate Projects rows whose returned name with namespace exactly matches `name_with_namespace` and retain the GitLab identifier for any cross-record match.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-7be32e99920c" title="Namespace" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace`

            Namespace records namespace of the upstream project. It is needed to preserve the nested namespace relationship or details on the parent GitLab Forked From Project record.

            * **Enables:** expand `namespace` to connect the containing GitLab Forked From Project row to its returned namespace entries.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is one nested object per containing GitLab Forked From Project object when present.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-av-2b29eb810c89" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.avatar_url`

            Avatar URL records URL to the namespace avatar. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-fu-301b9f74bb08" title="Full Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.full_path`

            Full Path records full path of the namespace including parent groups. It is needed to compare the returned full path for individual Projects rows and select rows with a specific `full_path` value.

            * **Enables:** trace the full path relationship returned in `full_path` from the GitLab Namespace row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the GitLab Namespace object returned for Projects; it is interpreted at one GitLab Namespace record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-id-056fce5b8035" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.id`

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

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-ki-14335fd46644" title="Kind" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.kind`

            Kind records kind of namespace (group or user). It is needed to distinguish Projects rows by the exact GitLab-returned kind value.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-na-8195ebebe317" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.name`

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

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-pa-3acd1c19967d" title="Parent ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.parent_id`

            Parent ID records ID of the parent namespace, if any. It is needed to refer to the same parent across records without relying on display text.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-pa-d7c3ca170f60" title="Path" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.path`

            Path records URL-safe path of the namespace. It is needed to compare the returned path for individual Projects rows and select rows with a specific `path` value.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-namespace-we-412803a6d55d" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.namespace.web_url`

            Web URL records web URL to the namespace. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-path-50752f67bfed" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.path`

            Path records path slug of the upstream project. It is needed to compare the returned path for individual Projects rows and select rows with a specific `path` value.

            * **Enables:** trace the path relationship returned in `path` from the GitLab Forked From Project row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-path-with-na-bb313ee6d184" title="Path With Namespace" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.path_with_namespace`

            Path With Namespace records full path with namespace of the upstream project. It is needed to compare the returned path with namespace for individual Projects rows and select rows with a specific `path_with_namespace` value.

            * **Enables:** locate Projects rows whose returned path with namespace exactly matches `path_with_namespace` and retain the GitLab identifier for any cross-record match.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-readme-url-b2537797f4ea" title="Readme URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.readme_url`

            Readme URL records README URL of the upstream project. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-ssh-url-to-r-0990d0d81aa0" title="SSH URL To Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.ssh_url_to_repo`

            SSH URL To Repo records SSH clone URL of the upstream project. It is needed to reproduce the returned code or dependency configuration for this Projects record.

            * **Enables:** use `ssh_url_to_repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-star-count-c31f6e6a7b07" title="Star Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.star_count`

            Star Count records star count of the upstream project. It is needed to measure the GitLab-reported number of star at one GitLab Forked From Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of star in `star_count` at one GitLab Forked From Project record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is a GitLab-reported count at one GitLab Forked From Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-tag-list-f6b7edbf88f2" title="Tag List" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.tag_list`

            Tag List records tags of the upstream project. It is needed to preserve the nested tag list relationship or details on the parent GitLab Forked From Project record.

            * **Enables:** expand `tag_list` to connect the containing GitLab Forked From Project row to its returned tag list entries.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is one returned collection per containing GitLab Forked From Project object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-topics-ae6104496d16" title="Topics" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.topics`

            Topics records topics of the upstream project. It is needed to preserve the nested topics relationship or details on the parent GitLab Forked From Project record.

            * **Enables:** expand `topics` to connect the containing GitLab Forked From Project row to its returned topics entries.
            * **Interpretation:** GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is one returned collection per containing GitLab Forked From Project object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-forked-from-project-web-url-6b5e643ed904" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forked_from_project.web_url`

            Web URL records web URL of the upstream project. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forking-access-level-85992eb582de" title="Forking Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forking_access_level`

            Forking Access Level records access level for forking. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-forks-count-ad3ad5dd3766" title="Forks Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.forks_count`

            Forks Count records number of forks of this project. It is needed to measure the GitLab-reported number of forks of this project at one GitLab Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of forks of this project in `forks_count` at one GitLab Project record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is a GitLab-reported count at one GitLab Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-group-runners-enabled-334b85569e32" title="Group Runners Enabled" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `projects.group_runners_enabled`

            Group Runners Enabled records whether group runners are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned group runners enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-http-url-to-repo-f908b31c5c0f" title="HTTP URL To Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.http_url_to_repo`

            HTTP URL To Repo records HTTP URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Projects record.

            * **Enables:** use `http_url_to_repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the `Network.Url` scalar; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-id-8daf2c625db2" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.id`

            ID records unique numeric identifier for the project. It is needed to distinguish repeated deliveries of the same Projects row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-projects-import-error-0c5994875947" title="Import Error" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `projects.import_error`

            Import Error records error message from the project import. It is needed to inspect the exact error message included with this record.

            * **Enables:** inspect the error message returned in `import_error` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is error message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-import-status-1c939782c3d0" title="Import Status" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `projects.import_status`

            Import Status records status of the project import. It is needed to distinguish Projects rows by the exact GitLab-returned import status value.

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

          <Accordion id="provider-permission-field-gitlab-projects-import-type-e5eff6e9d1fb" title="Import Type" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `projects.import_type`

            Import Type records type of import used to create the project. It is needed to distinguish Projects rows by the exact GitLab-returned import type value.

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

          <Accordion id="provider-permission-field-gitlab-projects-import-url-882f66cf78ea" title="Import URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.import_url`

            Import URL records URL used to import the project. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-infrastructure-access-level-16b9059ef12a" title="Infrastructure Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.infrastructure_access_level`

            Infrastructure Access Level records access level for infrastructure. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-issue-branch-template-e8a79928d9b4" title="Issue Branch Template" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issue_branch_template`

            Issue Branch Template records custom template for issue branch names. It is needed to distinguish Projects rows by the exact GitLab-returned issue branch template value.

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

          <Accordion id="provider-permission-field-gitlab-projects-issues-access-level-45e1fe5c7ea4" title="Issues Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issues_access_level`

            Issues Access Level records access level for issues. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-issues-enabled-a707f4bb5988" title="Issues Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issues_enabled`

            Issues Enabled records whether issues are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned issues enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-jobs-enabled-57307ba80390" title="Jobs Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.jobs_enabled`

            Jobs Enabled records whether CI/CD jobs are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned jobs enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-keep-latest-artifact-233761796a65" title="Keep Latest Artifact" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.keep_latest_artifact`

            Keep Latest Artifact records whether the latest artifact is kept. It is needed to distinguish Projects rows by the exact GitLab-returned keep latest artifact value.

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

          <Accordion id="provider-permission-field-gitlab-projects-last-activity-at-e1350e5b8b98" title="Last Activity At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.last_activity_at`

            Last Activity At records timestamp of the most recent activity on the project. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-projects-lfs-enabled-6641e7ff2ccb" title="Lfs Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lfs_enabled`

            Lfs Enabled records whether Git LFS is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned lfs enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-marked-for-deletion-at-d94780dfd56c" title="Marked For Deletion At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.marked_for_deletion_at`

            Marked For Deletion At records date when the project was marked for deletion. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-projects-marked-for-deletion-on-6b7b90496b56" title="Marked For Deletion On" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.marked_for_deletion_on`

            Marked For Deletion On records date when the project was marked for deletion. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-projects-merge-commit-template-f4ecfe7b3a60" title="Merge Commit Template" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.merge_commit_template`

            Merge Commit Template records custom template for merge commit messages. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `merge_commit_template` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is commit message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-merge-method-1c4ff96ed063" title="Merge Method" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.merge_method`

            Merge Method records merge method used for the project. It is needed to distinguish Projects rows by the exact GitLab-returned merge method value.

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

          <Accordion id="provider-permission-field-gitlab-projects-merge-pipelines-enabled-a5443ae13624" title="Merge Pipelines Enabled" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.merge_pipelines_enabled`

            Merge Pipelines Enabled records whether merged results pipelines are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned merge pipelines enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-merge-requests-access-level-c049a60fc619" title="Merge Requests Access Level" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.merge_requests_access_level`

            Merge Requests Access Level records access level for merge requests. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-merge-requests-enabled-6120c71d43ed" title="Merge Requests Enabled" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.merge_requests_enabled`

            Merge Requests Enabled records whether merge requests are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned merge requests enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-merge-trains-enabled-1bf3248f1af1" title="Merge Trains Enabled" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.merge_trains_enabled`

            Merge Trains Enabled records whether merge trains are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned merge trains enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-mirror-6fd17599fd56" title="Mirror" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.mirror`

            Mirror records whether the project is a mirror. It is needed to distinguish Projects rows by the exact GitLab-returned mirror value.

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

          <Accordion id="provider-permission-field-gitlab-projects-model-experiments-access-level-d572496cdba1" title="Model Experiments Access Level" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `projects.model_experiments_access_level`

            Model Experiments Access Level records access level for model experiments. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-model-registry-access-level-c8b81ce54499" title="Model Registry Access Level" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `projects.model_registry_access_level`

            Model Registry Access Level records access level for model registry. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-monitor-access-level-fea76b57212f" title="Monitor Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.monitor_access_level`

            Monitor Access Level records access level for monitoring. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-mr-default-target-self-a09042543288" title="Mr Default Target Self" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.mr_default_target_self`

            Mr Default Target Self records whether MRs default to targeting the same project. It is needed to distinguish Projects rows by the exact GitLab-returned mr default target self value.

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

          <Accordion id="provider-permission-field-gitlab-projects-name-4b36848cadda" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.name`

            Name records human-readable project name. It is needed to compare the returned name for individual Projects rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-gitlab-projects-name-with-namespace-72346c5eac0f" title="Name With Namespace" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.name_with_namespace`

            Name With Namespace records full name including namespace (e.g., 'Group / Subgroup / Project'). It is needed to compare the returned name with namespace for individual Projects rows and select rows with a specific `name_with_namespace` value.

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

          <Accordion id="provider-permission-field-gitlab-projects-namespace-1618f89e56b7" title="Namespace" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `projects.namespace`

            Namespace records the group/namespace this project belongs to. It is needed to preserve the nested namespace relationship or details on the parent GitLab Project record.

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

          <Accordion id="provider-permission-field-gitlab-projects-only-allow-merge-if-all-discussi-249979ed2f5d" title="Only Allow Merge If All Discussions Are Resolved" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.only_allow_merge_if_all_discussions_are_resolved`

            Only Allow Merge If All Discussions Are Resolved records whether merges require all discussions to be resolved. It is needed to distinguish Projects rows by the exact GitLab-returned only allow merge if all discussions are resolved value.

            * **Enables:** select Projects rows where `only_allow_merge_if_all_discussions_are_resolved` is true or false when comparing the condition described by Only Allow Merge If All Discussions Are Resolved.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-only-allow-merge-if-pipeline-suc-26fc85f12e9d" title="Only Allow Merge If Pipeline Succeeds" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.only_allow_merge_if_pipeline_succeeds`

            Only Allow Merge If Pipeline Succeeds records whether merges require a successful pipeline. It is needed to distinguish Projects rows by the exact GitLab-returned only allow merge if pipeline succeeds value.

            * **Enables:** select Projects rows where `only_allow_merge_if_pipeline_succeeds` is true or false when comparing the condition described by Only Allow Merge If Pipeline Succeeds.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-open-issues-count-a0c41652e763" title="Open Issues Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.open_issues_count`

            Open Issues Count records number of open issues in this project. It is needed to measure the GitLab-reported number of open issues in this project at one GitLab Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of open issues in this project in `open_issues_count` at one GitLab Project record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is a GitLab-reported count at one GitLab Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-owner-83b10b3f71bf" title="Owner" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner`

            Owner records owner of the project (present for personal projects). It is needed to preserve the nested owner relationship or details on the parent GitLab Project record.

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-avatar-url-b9ec9160d922" title="Avatar URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.avatar_url`

            Avatar URL records URL to the user avatar. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-id-aa7d7455ef82" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.id`

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

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-locked-b5b1b6f34508" title="Locked" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.locked`

            Locked records whether the user account is locked. It is needed to distinguish Projects rows by the exact GitLab-returned locked value.

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-name-d65a642736c7" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.name`

            Name records display name of the owner. It is needed to attribute this Projects row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-state-6cc5e0630ca9" title="State" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.state`

            State records account state (e.g., active, blocked). It is needed to distinguish Projects rows by the exact GitLab-returned state value.

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-username-d71fe2e49d89" title="User Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.username`

            User Name records username of the owner. It is needed to attribute this Projects row to the returned person, account, or organization reference.

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

          <Accordion id="provider-permission-field-gitlab-projects-owner-web-url-7b489dd8a9b8" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.owner.web_url`

            Web URL records web URL to the user profile. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-packages-enabled-ecaaca6db906" title="Packages Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.packages_enabled`

            Packages Enabled records whether the package registry is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned packages enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-pages-access-level-e59aa22f4a09" title="Pages Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.pages_access_level`

            Pages Access Level records access level for GitLab Pages. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-path-18c309cf4f61" title="Path" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.path`

            Path records URL-safe project path slug. It is needed to compare the returned path for individual Projects rows and select rows with a specific `path` value.

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

          <Accordion id="provider-permission-field-gitlab-projects-path-with-namespace-073fe7a03be1" title="Path With Namespace" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `projects.path_with_namespace`

            Path With Namespace records full path including group namespace (e.g., group/subgroup/project). It is needed to compare the returned path with namespace for individual Projects rows and select rows with a specific `path_with_namespace` value.

            * **Enables:** locate Projects rows whose returned path with namespace exactly matches `path_with_namespace` and retain the GitLab identifier for any cross-record match.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-permissions-841b1563f5b1" title="Permissions" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions`

            Permissions records current user permissions on this project. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-permissions-group-access-59e95c795fa5" title="Group Access" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions.group_access`

            Group Access records access inherited from group membership. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `group_access` to examine the returned group access details for the containing GitLab Permissions record.
            * **Interpretation:** GitLab reports this value on the GitLab Permissions object returned for Projects; it is one nested object per containing GitLab Permissions object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-permissions-group-access-access--4dd1179eb884" title="Access Level" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions.group_access.access_level`

            Access Level records numeric access level (10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-permissions-group-access-notific-02f34cd2b5fc" title="Notification Level" icon="megaphone" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions.group_access.notification_level`

            Notification Level records notification level setting. It is needed to compare the exact notification level configuration returned for this GitLab Access Level record.

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

          <Accordion id="provider-permission-field-gitlab-projects-permissions-project-access-f1183034db5f" title="Project Access" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions.project_access`

            Project Access records direct project-level access. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** expand `project_access` to examine the returned project access details for the containing GitLab Permissions record.
            * **Interpretation:** GitLab reports this value on the GitLab Permissions object returned for Projects; it is one nested object per containing GitLab Permissions object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-printing-merge-request-link-enab-fc5a31a5a800" title="Printing Merge Request Link Enabled" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.printing_merge_request_link_enabled`

            Printing Merge Request Link Enabled records whether the merge request link is printed after a push. It is needed to distinguish Projects rows by the exact GitLab-returned printing merge request link enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-public-jobs-12429f90238e" title="Public Jobs" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.public_jobs`

            Public Jobs records whether CI/CD job logs are public. It is needed to distinguish Projects rows by the exact GitLab-returned public jobs value.

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

          <Accordion id="provider-permission-field-gitlab-projects-readme-url-3791f4273e42" title="Readme URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.readme_url`

            Readme URL records URL to the project README file. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-releases-access-level-16a71a3f92b5" title="Releases Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.releases_access_level`

            Releases Access Level records access level for releases. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-remove-source-branch-after-merge-2b683d0d2e84" title="Remove Source Branch After Merge" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.remove_source_branch_after_merge`

            Remove Source Branch After Merge records whether source branches are removed after merge. It is needed to distinguish Projects rows by the exact GitLab-returned remove source branch after merge value.

            * **Enables:** select Projects rows where `remove_source_branch_after_merge` is true or false when comparing the condition described by Remove Source Branch After Merge.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-repository-access-level-a6d7a41709a3" title="Repository Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.repository_access_level`

            Repository Access Level records access level for the repository. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-repository-object-format-db329d359862" title="Repository Object Format" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `projects.repository_object_format`

            Repository Object Format records object format of the repository (e.g., sha1, sha256). It is needed to distinguish Projects rows by the exact GitLab-returned repository object format value.

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

          <Accordion id="provider-permission-field-gitlab-projects-request-access-enabled-1531fdab5292" title="Request Access Enabled" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `projects.request_access_enabled`

            Request Access Enabled records whether users can request access to the project. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-requirements-access-level-eb2b155d8725" title="Requirements Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.requirements_access_level`

            Requirements Access Level records access level for the requirements feature. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-resolve-outdated-diff-discussion-6e0239f43365" title="Resolve Outdated Diff Discussions" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `projects.resolve_outdated_diff_discussions`

            Resolve Outdated Diff Discussions records whether outdated diff discussions are automatically resolved. It is needed to distinguish Projects rows by the exact GitLab-returned resolve outdated diff discussions value.

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

          <Accordion id="provider-permission-field-gitlab-projects-restrict-user-defined-variables-fa48851117ea" title="Restrict User Defined Variables" icon="user-tie" iconType="sharp-duotone-solid">
            Developer identifier: `projects.restrict_user_defined_variables`

            Restrict User Defined Variables records whether user-defined CI/CD variables are restricted. It is needed to inspect the exact metadata included with this record.

            * **Enables:** inspect the exact metadata keys returned in `restrict_user_defined_variables` and associate them with the containing Projects record.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; keys and availability follow this GitLab response and may vary by object type or GitLab configuration; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-runner-token-expiration-interval-ab413f9fac98" title="Runner Token Expiration Interval" icon="microchip" iconType="sharp-duotone-solid">
            Developer identifier: `projects.runner_token_expiration_interval`

            Runner Token Expiration Interval records runner token expiration interval in seconds. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** correlate the exact `runner_token_expiration_interval` access value with the resource, account, or membership represented by the same Projects row.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; its unit or granularity is seconds; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-security-and-compliance-access-l-4db4cc43db84" title="Security And Compliance Access Level" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.security_and_compliance_access_level`

            Security And Compliance Access Level records access level for security and compliance features. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Projects rows with the exact `security_and_compliance_access_level` access-related value being investigated.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; a returned framework label or feature setting does not demonstrate that a framework requirement is satisfied; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-security-and-compliance-enabled-724b0d37cc9b" title="Security And Compliance Enabled" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.security_and_compliance_enabled`

            Security And Compliance Enabled records whether the security and compliance features are enabled. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

            * **Enables:** select Projects rows with the exact `security_and_compliance_enabled` access-related value being investigated.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; a returned framework label or feature setting does not demonstrate that a framework requirement is satisfied; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-service-desk-address-329832cee889" title="Service Desk Address" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `projects.service_desk_address`

            Service Desk Address records email address for the service desk. It is needed to preserve the GitLab-reported configured or derived address and place context for the same record.

            * **Enables:** compare the GitLab-reported configured or derived address and place context in `service_desk_address` for individual Projects rows without treating it as a verified physical location.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the `Contact.Email` scalar; the value is configured or derived address and place context; this GitLab-reported or configured context does not establish residency or verified physical presence.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-service-desk-enabled-8c65be5926a0" title="Service Desk Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.service_desk_enabled`

            Service Desk Enabled records whether the service desk is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned service desk enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-shared-runners-enabled-4bc8416ff2d7" title="Shared Runners Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_runners_enabled`

            Shared Runners Enabled records whether shared runners are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned shared runners enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-shared-with-groups-7df0d570ca66" title="Shared With Groups" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_with_groups`

            Shared With Groups records groups this project is shared with. It is needed to preserve the nested shared with groups relationship or details on the parent GitLab Project record.

            * **Enables:** expand `shared_with_groups` to connect the containing GitLab Project row to its returned shared with groups entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-shared-with-groups-expires-at-d7f0608b5d77" title="Expires At" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_with_groups.expires_at`

            Expires At records expiration date of the share. It is needed to place the record at the time or date reported for this event or state.

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

          <Accordion id="provider-permission-field-gitlab-projects-shared-with-groups-group-access--8be5b2a036da" title="Group Access Level" icon="sitemap" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_with_groups.group_access_level`

            Group Access Level records access level granted to the shared group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-shared-with-groups-group-full-pa-a3b59fe076d9" title="Group Full Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_with_groups.group_full_path`

            Group Full Path records full path of the shared group. It is needed to compare the returned group full path for individual Projects rows and select rows with a specific `group_full_path` value.

            * **Enables:** trace the group full path relationship returned in `group_full_path` from the GitLab Shared Group row to its named GitLab context.
            * **Interpretation:** GitLab reports this value on the GitLab Shared Group object returned for Projects; it is interpreted at one GitLab Shared Group record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-shared-with-groups-group-id-202a9b9da123" title="Group ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_with_groups.group_id`

            Group ID records ID of the shared group. It is needed to distinguish repeated deliveries of the same Projects row using the declared ingestion key.

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

          <Accordion id="provider-permission-field-gitlab-projects-shared-with-groups-group-name-9a36fb5d46fc" title="Group Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `projects.shared_with_groups.group_name`

            Group Name records name of the shared group. It is needed to compare the returned group name for individual Projects rows and select rows with a specific `group_name` value.

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

          <Accordion id="provider-permission-field-gitlab-projects-snippets-access-level-7599b4e4a3f1" title="Snippets Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.snippets_access_level`

            Snippets Access Level records access level for snippets. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-snippets-enabled-e2140d5139e1" title="Snippets Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.snippets_enabled`

            Snippets Enabled records whether snippets are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned snippets enabled value.

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

          <Accordion id="provider-permission-field-gitlab-projects-squash-commit-template-13a30ba99214" title="Squash Commit Template" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `projects.squash_commit_template`

            Squash Commit Template records custom template for squash commit messages. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `squash_commit_template` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is commit message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-squash-option-50ca923ded0f" title="Squash Option" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `projects.squash_option`

            Squash Option records squash option for merge requests. It is needed to distinguish Projects rows by the exact GitLab-returned squash option value.

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

          <Accordion id="provider-permission-field-gitlab-projects-ssh-url-to-repo-381566f661b9" title="SSH URL To Repo" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.ssh_url_to_repo`

            SSH URL To Repo records SSH URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Projects record.

            * **Enables:** use `ssh_url_to_repo` to locate the configured source, package, or repository when reproducing the same job or repository setup.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the returned link or template does not establish that the current credential can retrieve its target.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-star-count-ec192cc0fa71" title="Star Count" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.star_count`

            Star Count records number of stars on this project. It is needed to measure the GitLab-reported number of stars on this project at one GitLab Project record per row.

            * **Enables:** measure and compare the GitLab-reported number of stars on this project in `star_count` at one GitLab Project record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is a GitLab-reported count at one GitLab Project record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-24c9c1f2dada" title="Statistics" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics`

            Statistics records project storage and usage statistics. It is needed to preserve the nested statistics relationship or details on the parent GitLab Project record.

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

          <Accordion id="provider-permission-field-gitlab-projects-statistics-commit-count-d0730500b802" title="Commit Count" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.commit_count`

            Commit Count records total number of commits. It is needed to measure the GitLab-reported number of commits at one GitLab Project Statistics record per row.

            * **Enables:** measure and compare the GitLab-reported number of commits in `commit_count` at one GitLab Project Statistics record per row.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; it is a GitLab-reported count at one GitLab Project Statistics record per row.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-container-registry-si-286ae7bd32ca" title="Container Registry Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.container_registry_size`

            Container Registry Size records container registry size in bytes. It is needed to measure the reported container registry size for one gitlab project statistics record.

            * **Enables:** measure and compare `container_registry_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-job-artifacts-size-5b729f915446" title="Job Artifacts Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.job_artifacts_size`

            Job Artifacts Size records job artifacts size in bytes. It is needed to measure the reported job artifacts size for one gitlab project statistics record.

            * **Enables:** measure and compare `job_artifacts_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-lfs-objects-size-5166b9199516" title="Lfs Objects Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.lfs_objects_size`

            Lfs Objects Size records LFS objects size in bytes. It is needed to measure the reported lfs objects size for one gitlab project statistics record.

            * **Enables:** measure and compare `lfs_objects_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-packages-size-9baad7a4d23e" title="Packages Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.packages_size`

            Packages Size records packages size in bytes. It is needed to measure the reported packages size for one gitlab project statistics record.

            * **Enables:** measure and compare `packages_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-pipeline-artifacts-si-b717d9942b9f" title="Pipeline Artifacts Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.pipeline_artifacts_size`

            Pipeline Artifacts Size records pipeline artifacts size in bytes. It is needed to measure the reported pipeline artifacts size for one gitlab project statistics record.

            * **Enables:** measure and compare `pipeline_artifacts_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-repository-size-5d656e540d81" title="Repository Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.repository_size`

            Repository Size records repository size in bytes. It is needed to measure the reported repository size for one gitlab project statistics record.

            * **Enables:** measure and compare `repository_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-snippets-size-c43369b2593c" title="Snippets Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.snippets_size`

            Snippets Size records snippets size in bytes. It is needed to measure the reported snippets size for one gitlab project statistics record.

            * **Enables:** measure and compare `snippets_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-storage-size-eee6eb7e6b53" title="Storage Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.storage_size`

            Storage Size records total storage size in bytes. It is needed to measure the reported storage size for one gitlab project statistics record.

            * **Enables:** measure and compare `storage_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-uploads-size-4a579dbc1c4c" title="Uploads Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.uploads_size`

            Uploads Size records uploads size in bytes. It is needed to measure the reported uploads size for one gitlab project statistics record.

            * **Enables:** measure and compare `uploads_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-statistics-wiki-size-9d9dcd81f70b" title="Wiki Size" icon="calculator" iconType="sharp-duotone-solid">
            Developer identifier: `projects.statistics.wiki_size`

            Wiki Size records wiki size in bytes. It is needed to measure the reported wiki size for one gitlab project statistics record.

            * **Enables:** measure and compare `wiki_size` per GitLab Project Statistics record in bytes.
            * **Interpretation:** GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-suggestion-commit-message-36ceb264cf4a" title="Suggestion Commit Message" icon="comments" iconType="sharp-duotone-solid">
            Developer identifier: `projects.suggestion_commit_message`

            Suggestion Commit Message records custom commit message template for suggestions. It is needed to inspect the exact commit message included with this record.

            * **Enables:** inspect the commit message returned in `suggestion_commit_message` and attribute it to the same record's repository or project, owner, and update time where returned.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is commit message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-tag-list-ef7d318cab55" title="Tag List" icon="list-tree" iconType="sharp-duotone-solid">
            Developer identifier: `projects.tag_list`

            Tag List records deprecated array of topic tags (use topics instead). It is needed to preserve the nested tag list relationship or details on the parent GitLab Project record.

            * **Enables:** expand `tag_list` to connect the containing GitLab Project row to its returned tag list entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-topics-ad6346572fa0" title="Topics" icon="route" iconType="sharp-duotone-solid">
            Developer identifier: `projects.topics`

            Topics records array of topic tags assigned to the project. It is needed to preserve the nested topics relationship or details on the parent GitLab Project record.

            * **Enables:** expand `topics` to connect the containing GitLab Project row to its returned topics entries.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object.
          </Accordion>

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

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

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

          <Accordion id="provider-permission-field-gitlab-projects-visibility-12ce28a2ef35" title="Visibility" icon="sliders" iconType="sharp-duotone-solid">
            Developer identifier: `projects.visibility`

            Visibility records project visibility level. It is needed to distinguish Projects rows by the exact GitLab-returned visibility value.

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

          <Accordion id="provider-permission-field-gitlab-projects-warn-about-potentially-unwanted--2cef6f89f370" title="Warn About Potentially Unwanted Characters" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.warn_about_potentially_unwanted_characters`

            Warn About Potentially Unwanted Characters records whether warnings about potentially unwanted characters are shown. It is needed to distinguish Projects rows by the exact GitLab-returned warn about potentially unwanted characters value.

            * **Enables:** select Projects rows where `warn_about_potentially_unwanted_characters` is true or false when comparing the condition described by Warn About Potentially Unwanted Characters.
            * **Interpretation:** GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-projects-web-url-e1a58f070f91" title="Web URL" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.web_url`

            Web URL records web URL to the project in the GitLab UI. It is needed to inspect the exact link included with this record.

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

          <Accordion id="provider-permission-field-gitlab-projects-wiki-access-level-4332b2c1a5a3" title="Wiki Access Level" icon="cube" iconType="sharp-duotone-solid">
            Developer identifier: `projects.wiki_access_level`

            Wiki Access Level records access level for the wiki. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

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

          <Accordion id="provider-permission-field-gitlab-projects-wiki-enabled-2280d426b2e3" title="Wiki Enabled" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.wiki_enabled`

            Wiki Enabled records whether the wiki is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned wiki enabled value.

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

      <Accordion id="provider-permission-tap-gitlab-repos-43f1f5fe335d" title="Repository Files" icon="gitlab" iconType="sharp-duotone-solid">
        Developer identifier: `repos`

        Repository Files covers project repository file tree.

        * **Enables:** inventory returned repositories or project files and correlate each record with its owner, namespace, visibility, default branch, and update time where present.
        * **Scope:** Project repository file tree; the connector reads `/api/v4/projects/{id}/repository/tree` as a snapshot stream in full mode. The configured credential must grant the declared `read_api` access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

        <AccordionGroup>
          <Accordion id="provider-permission-field-gitlab-repos-id-bd4715c708e1" title="ID" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `repos.id`

            ID records SHA-1 hash identifier of the tree entry (blob or tree object id). It is needed to refer to the same repo tree entry across records without relying on display text.

            * **Enables:** match `id` to repo tree entry references carrying the same GitLab-issued value in related GitLab records.
            * **Interpretation:** GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is an identifier, not a measured quantity.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-repos-mode-e3e29e534f5f" title="Mode" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `repos.mode`

            Mode records unix file mode string (e.g. '100644' for a regular file, '040000' for a directory). It is needed to distinguish Repository Files rows by the exact GitLab-returned mode value.

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

          <Accordion id="provider-permission-field-gitlab-repos-name-17a71d47582c" title="Name" icon="comment" iconType="sharp-duotone-solid">
            Developer identifier: `repos.name`

            Name records file or directory name (last path segment). It is needed to compare the returned name for individual Repository Files rows and select rows with a specific `name` value.

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

          <Accordion id="provider-permission-field-gitlab-repos-path-b2fa3edf2c65" title="Path" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `repos.path`

            Path records full path of the entry from the repository root. It is needed to distinguish repeated deliveries of the same Repository Files row using the declared ingestion key.

            * **Enables:** use `path` as the declared ingestion deduplication key for Repository Files and match repeated rows carrying the same GitLab identifier.
            * **Interpretation:** GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is interpreted at one GitLab Repo Tree Entry record per row; the connector declares it as an ingestion deduplication key; the schema uses the `Asset.FilePath` scalar.
          </Accordion>

          <Accordion id="provider-permission-field-gitlab-repos-type-8134dbbf77f6" title="Type" icon="folder-open" iconType="sharp-duotone-solid">
            Developer identifier: `repos.type`

            Type records entry type: 'tree' for a directory, 'blob' for a file. It is needed to distinguish Repository Files rows by the exact GitLab-returned type value.

            * **Enables:** separate Repository Files rows by the exact GitLab-returned `type` label when comparing type.
            * **Interpretation:** GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is interpreted at one GitLab Repo Tree Entry record per row; classification values are GitLab-returned labels rather than a universal taxonomy.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    | Error              | Meaning               | Solution                                |
    | ------------------ | --------------------- | --------------------------------------- |
    | `401 Unauthorized` | Invalid token         | Verify token is correct and not expired |
    | `403 Forbidden`    | Insufficient scope    | Add required scope and regenerate       |
    | `404 Not Found`    | No access to resource | Check user has project/group membership |
    | `429 Rate Limited` | Too many requests     | Implement backoff                       |

    #### Common Issues

    #### Token expired

    GitLab PATs have expiration dates. Generate a new token with a longer expiration.

    #### Can't access group projects

    Ensure your GitLab user has at least Reporter access to the group.

    **[GitLab API](https://docs.gitlab.com/ee/api/)** — Official API documentation

    **[Token Types](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html)** — Access token guide
  </Tab>
</Tabs>