Answer: Kiro's GitLab access is scoped by the personal access token you grant. For fine-grained tokens (recommended), grant Code (Download, Push), Merge Request (Read, Create), and Work Item (Read) under Group and project access, plus Project (Read) and User (Read) under User; legacy tokens use the scopes api, read_api, or write_repository. Status: Confirmed Entry: tool/kiro/permissions-and-security/gitlab-token-permissions Revision: 3 Digest: sha256:5d0d912ae2b27a52 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:46:06Z Last changed: 2026-11-20T13:33:39Z (Legacy token scope (code access): — → write_repository) Last verified: 2026-11-20T13:33:39Z Next check: 2026-11-21T13:33:39Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Fine-grained Group and project permissions | Code (Download, Push) · Merge Request (Read, Create) · Work Item (Read) | [1] | 2026-11-20 Fine-grained User permissions | Project (Read) · User (Read) | [1] | 2026-11-20 Legacy token scope (full access) | api | [1] | 2026-11-20 Legacy token scope (read-only) | read_api | [1] | 2026-11-20 Legacy token scope (code access) | write_repository | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "GitLab - Connect your repositories - Web - Docs - Kiro". https://kiro.dev/docs/web/gitlab/ Role: primary. Accessed: 2026-11-20T13:33:39Z Quote: "Code (Download, Push) · Merge Request (Read, Create) · Work Item (Read)" (Supports: Fine-grained Group and project permissions) Quote: "Project (Read) · User (Read)" (Supports: Fine-grained User permissions) Quote: "api — full access. Supports all of Kiro's GitLab capabilities." (Supports: Legacy token scope (full access)) Quote: "read_api — read-only access." (Supports: Legacy token scope (read-only)) Quote: "write_repository — code access without issues." (Supports: Legacy token scope (code access)) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 7b2ef1d7921d69c8db101074fd8aa5f57ba53f55e2b3c10ea54f13d2c0e44cb1 (captured 2026-11-20T13:33:36Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:33:39Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:33:39Z Last attempt: 2026-11-20T13:33:39Z Notes and limitations: Extracted automatically from a single official source (section "Permissions"). Related: https://latestn.com/tool/kiro/permissions-and-security/govcloud-model-authorization How do I get model authorization for Kiro in AWS GovCloud (US)? https://latestn.com/tool/kiro/permissions-and-security/headless-token-remote-access How do I run Kiro Crew headlessly with token-authenticated remote access? https://latestn.com/tool/kiro/permissions-and-security/iam-permissions-external-idp What IAM permissions does Kiro need for external identity provider integration? https://latestn.com/tool/kiro/permissions-and-security/enable-and-use-sandbox How do I enable and configure the Kiro local command sandbox? https://latestn.com/tool/kiro/permissions-and-security/gateway-api-authentication How do I authenticate to the Kiro Crew Gateway API? https://latestn.com/tool/kiro/permissions-and-security/github-permissions What permissions does Kiro need for GitHub access? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:33:39Z | changed | Legacy token scope (code access): — → write_repository | [1] 2026-11-20T13:33:39Z | changed | Legacy token scope (read-only): — → read_api | [1] 2026-11-20T13:33:39Z | changed | Legacy token scope (full access): — → api | [1] 2026-11-20T13:33:39Z | changed | Legacy scope write_repository: write_repository → — | [1] 2026-11-20T13:33:39Z | changed | Legacy scope read_api: read_api → — | [1] 2026-11-20T13:33:39Z | changed | Legacy scope api: api → — | [1] 2026-11-18T13:27:56Z | changed | Legacy scope write_repository: — → write_repository | [1] 2026-11-18T13:27:56Z | changed | Legacy scope read_api: — → read_api | [1] 2026-11-18T13:27:56Z | changed | Legacy scope api: — → api | [1] 2026-11-18T13:27:56Z | changed | Legacy token code-only scope: write_repository → — | [1] 2026-11-18T13:27:56Z | changed | Legacy token read-only scope: read_api → — | [1] 2026-11-18T13:27:56Z | changed | Legacy token full access scope: api → — | [1] 2026-11-13T03:46:06Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/gitlab-token-permissions/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/permissions-and-security/gitlab-token-permissions POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/gitlab-token-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/gitlab-token-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What permissions or token scopes does Kiro need for GitLab access? Revision 3, last verified 2026-11-20T13:33:39Z. https://latestn.com/tool/kiro/permissions-and-security/gitlab-token-permissions (accessed 2026-11-21T10:02:20Z). @misc{LatestN_tool_kiro_permissions_and_security_gitlab_token_permissions_r3, title = {What permissions or token scopes does Kiro need for GitLab access?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/gitlab-token-permissions}}, note = {Revision 3; digest sha256:5d0d912ae2b27a52; last verified 2026-11-20T13:33:39Z; accessed 2026-11-21T10:02:20Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/permissions-and-security/gitlab-token-permissions