Connect self-hosted GitLab
Connect your own GitLab instance by registering an OAuth application there and supplying its details in DocuWriter.
Before you start
You need permission to create a GitLab OAuth application and to read the repository. The instance must be reachable by DocuWriter's servers over valid HTTPS; being accessible only through your browser's VPN is not sufficient.
1. Create the OAuth application
In your GitLab profile settings, open Applications and create an application for DocuWriter. Set its redirect URI exactly to:
https://app.docuwriter.ai/auth/gitlab/callback
For the supported connection, configure api, read_user, read_repository, read_api and write_repository. Repository writing and webhook management require the corresponding access; review those permissions with your administrator before authorizing.
Save the application and copy its application ID and secret. Store the secret securely; do not paste it into a documentation page or support screenshot.
2. Connect the instance
In Git Connections → Connect GitLab, enable Use self-hosted GitLab instance. Enter the HTTPS instance URL, client ID and client secret, then continue through GitLab's authorization screen.
Return to DocuWriter and add the repository and branch. A successful OAuth return is only the first check: verify the expected project can be selected and imported.
Troubleshooting
| Problem | Check |
|---|---|
| Invalid redirect URI | Exact HTTPS callback, with no extra slash or whitespace. |
| Invalid or missing scope | OAuth application permissions on your own GitLab instance; update them and reconnect. |
| Instance cannot be reached | Public server reachability, firewall rules and certificate validity. |
| Repository missing | Project membership and permissions of the authorizing GitLab user. |
If your network cannot allow the connection, a one-time project ZIP can produce documentation without ongoing repository access.
Updated