Answer: For Core and Teams users, once the integration is configured, you can @mention repositories directly in your prompts within the Devin web application. For Enterprise users, you delegate repositories to specific organizations and add the relevant groups or repositories with Read & write or Read only access. Status: Confirmed Entry: tool/devin/permissions-and-security/gitlab-repository-permissions Revision: 2 Digest: sha256:e68ec931b6fe38c5 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:14:54Z Last changed: 2026-11-15T12:49:44Z (Enterprise access levels: — → Read & write) Last verified: 2026-11-20T12:46:19Z Next check: 2026-11-21T12:46:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Core and Teams permission | @mention repositories directly in your prompts | [1] | 2026-11-20 Enterprise access levels | Read & write | [1] | 2026-11-20 Sources: [1] Cognition. "GitLab". https://docs.devin.ai/integrations/gitlab.md Role: primary. Accessed: 2026-11-20T12:46:19Z Quote: "Once the integration is configured, you can @mention repositories directly in your prompts within the Devin web application." (Supports: Core and Teams permission) Quote: "Add the relevant groups or repositories with **Read & write** or **Read only** access" (Supports: Enterprise access levels) Published: 2026-11-20T09:56:12Z Snapshot SHA-256: 6a0dee4caef180e05447d1ab9a5772c2bdfed371585960a208da109ea11062f0 (captured 2026-11-15T12:49:40Z) 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]. On this check the text of [1] was unchanged since 2026-11-15T12:49:44Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:46:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:46:19Z Last attempt: 2026-11-20T12:46:19Z Notes and limitations: Extracted automatically from a single official source (section "Repository Permissions"). Related: https://latestn.com/tool/devin/permissions-and-security/give-credentials How do I give Devin credentials to sign in to tools? https://latestn.com/tool/devin/permissions-and-security/how-oidc-works How does Devin's OIDC authentication work without storing static credentials? https://latestn.com/tool/devin/permissions-and-security/imessage-link-permissions What permissions do I need to link a Devin Bot to iMessage? https://latestn.com/tool/devin/permissions-and-security/disclosure-policy-safe-harbor What is Devin Desktop's coordinated disclosure policy and safe harbor? https://latestn.com/tool/devin/permissions-and-security/disconnect-or-revoke-access How do I disconnect or revoke Devin's access to my computer? https://latestn.com/tool/devin/permissions-and-security/endpoint-permissions Which permissions does each Devin Desktop API endpoint require? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T12:49:44Z | changed | Enterprise access levels: — → Read & write | [1] 2026-11-15T12:49:44Z | changed | Core and Teams permission: — → @mention repositories directly in your prompts | [1] 2026-11-15T12:49:44Z | changed | Enterprise delegation: delegate repositories to specific organizations → — | [1] 2026-11-15T12:49:44Z | changed | Enterprise permissions: Read & write → — | [1] 2026-11-15T12:49:44Z | changed | Core and Teams permissions: @mention repositories directly in your prompts → — | [1] 2026-11-13T03:14:54Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/permissions-and-security/gitlab-repository-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/devin/permissions-and-security/gitlab-repository-permissions POST: https://latestn.com/dispute/tool/devin/permissions-and-security/gitlab-repository-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/permissions-and-security/gitlab-repository-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What repository permissions does Devin need for GitLab, and how do they differ for Core, Teams, and Enterprise users? Revision 2, last verified 2026-11-20T12:46:19Z. https://latestn.com/tool/devin/permissions-and-security/gitlab-repository-permissions (accessed 2026-11-21T10:03:05Z). @misc{LatestN_tool_devin_permissions_and_security_gitlab_repository_permissions_r2, title = {What repository permissions does Devin need for GitLab, and how do they differ for Core, Teams, and Enterprise users?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/permissions-and-security/gitlab-repository-permissions}}, note = {Revision 2; digest sha256:e68ec931b6fe38c5; last verified 2026-11-20T12:46:19Z; accessed 2026-11-21T10:03:05Z} } 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/devin/permissions-and-security/gitlab-repository-permissions