Understand the authorization scope and choose the project Wisesama will assess.
4 min readUpdated November 4, 2026
Start with GitLab.com
The initial integration supports GitLab.com. Self-managed GitLab hosts are outside this release. Connecting a provider is separate from signing in to Wisesama.
Understand what you authorize
GitLab’s read_api OAuth scope grants read API access under your GitLab identity. That provider grant is broader than the projects you select inside Wisesama. Project selection narrows what Wisesama processes; it does not narrow GitLab’s token permission.
Wisesama reads supported inventory files, repository metadata, and allowlisted package-manager and CI configuration for static baseline checks. Raw configuration is transient; extracted facts and paths are retained. It does not need permission to push commits or create merge requests for this assessment workflow.
Choose GitLab.com when creating a project.
Review the provider’s authorization screen and return to Wisesama.
Select a project, branch, and supported inventory path.
Review the exact versions, warnings, and repository-wide scope before saving.
Keep the connection working
GitLab OAuth credentials expire and must be refreshed. If refresh or access checks fail, reconnect from workspace integrations. The last successful snapshot remains visible; a failed refresh is not an empty or clean assessment.
GitLab synchronization uses reconciliation rather than requesting extra write access to create project webhooks automatically. Disconnect in Wisesama and revoke the application in GitLab to remove both sides of the connection.
