Integration · GitLab
GitLab integration: compliance tasks as issues and code evidence on the AI system
Many AI obligations are met in code. SimpleAct’s GitLab integration creates issues in a project for governance blockers, evidence requests, runtime signals, changes and CAPA actions, and reads linked merge requests, commits and releases as evidence.
Runtime signal escalated
Service chatbot "Lia"
Evidence approval requested
DPIA report
Governance approval blocked
Marketing copy generator
Change register updated
Model update, application screening
SimpleAct
Event routing
GitLab
Issues
What the integration does
Compliance work where developers work
The direction is SimpleAct → GitLab: SimpleAct creates issues and updates title and body. Changes in the issue do not flow back.
- Issues from compliance cases
- Governance blockers, evidence requests, escalated runtime signals, change register entries and CAPA actions are created as issues. When the case changes, the issue is updated rather than duplicated.
- Verify code evidence
- If you link a merge request, commit or release from the connected project as governance evidence, SimpleAct reads its details through the GitLab API and records them with the evidence.
- Self-managed too
- The API address is configurable (default https://gitlab.com/api/v4), so self-managed GitLab instances work too. Default branch, issue creation for governance and use as an evidence source can be switched separately.
How it works
Setting up GitLab
Set-up happens under Enterprise options → Integrations.
Create a token
Create a token in GitLab that may write issues in the target project. For evidence checks it also needs read access to merge requests, commits and releases.
Connect the project
Enter the project path (e.g. group/project) and the token. A connection test checks that the project is reachable. There is exactly one connected project per organisation.
Cases come in
New governance blockers, evidence requests and other cases appear as issues. If a delivery fails, SimpleAct shows a warning; the case itself stays saved.
What the GitLab integration does and does not do
For teams that want to see compliance tasks in their code workflow.
- Issues for governance blockers, evidence requests, runtime signals, changes and CAPA
- Update instead of duplicate when the case changes
- Pull requests, commits and releases as verified evidence links
- One project per organisation
- One-way: status or comment changes in GitLab are not pulled back
- Enterprise feature
Frequently asked questions about GitLab
Which permissions does the token need?
Write access to issues in the connected project. For checking evidence links, also read access to merge requests, commits and releases.
Can we connect several projects?
No, one project is connected per organisation. All issues go there.
Is a closed issue mirrored in SimpleAct?
No. The integration only writes from SimpleAct to GitLab. You maintain the status of the case in SimpleAct.
Make compliance tasks visible in the project
With the GitLab integration, your development team sees compliance tasks as issues, and code evidence is attached to the AI system after a check.