Integrations/GitLab

Control what your AI agents do in GitLab.

Let your team build AI agents for GitLab. Bollard AI controls what each one can do, project by project.

Request early accessSee how it works →
GitLab
Triage Agent
app-backend ProjectOffReadFull use
infra ProjectOffReadFull use
payments ProjectOffReadFull use
Merge and run pipelines
What agents can do

Set what each agent can do in every project.

Each project gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the project or that it exists.
Read
Read-only
The agent can read issues, merge requests, and code in that project. It can't change anything.
Full use
Open and update
The agent can open and comment on issues and merge requests in that project.

Some actions stay off until explicitly turned on

Each one ships code, removes work for good, or runs your pipelines, so it could override the limits set on individual projects.

Merging and accepting merge requestsRunning CI/CD pipelinesDeleting projects or branches
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's GitLab a single time and chooses which projects it covers. Any project left out stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, open, and update issues and merge requests in a single project
Example

An issue triage agent.

A triage agent comments on issues in app-backend and can read infra, but it can't open the payments project or merge code.

app-backend ProjectOffReadFull use
infra ProjectOffReadFull use
payments ProjectOffReadFull use

Manage access

ALLOWEDTriage Agent commented on an issue in app-backend
ALLOWEDTriage Agent read a merge request in infra
BLOCKEDTriage Agent tried to open the payments project, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and GitLab, so they never hold your GitLab keys and never reach GitLab directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to GitLab. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every project starts off-limits, and merging code is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your GitLab keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which project or merge request, and the decision. The record is readable and can't be edited after the fact.

Questions

GitLab, answered.

Does connecting GitLab hand Bollard AI all your projects?+
Only what's connected. An admin chooses which projects Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your code. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent merge code or run pipelines?+
Not unless you turn it on. Merging merge requests and running CI/CD pipelines are held off by default, so an agent can triage and comment where you allow without ever shipping code, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our GitLab keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches GitLab, and the blocked attempt lands in the activity record with the reason.
How do we connect GitLab?+
An admin connects the company's GitLab once. Bollard AI seals the connection and builds the list of projects to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in GitLab, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →