> For the complete documentation index, see [llms.txt](https://docs.mobb.ai/mobb-user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobb.ai/mobb-user-docs/common-troubleshooting-scenarios/scm-authorization-error.md).

# SCM Connection - Authorization error on connect

**Symptoms**

* Connecting an SCM in Mobb fails with an authorization or authentication error.
* Mobb can't list or access your repositories.

**Likely cause**

The access token Mobb is using has expired, was revoked, or is missing the required scopes/permissions.

**Resolution**

1. Regenerate the access token in your SCM with the correct scopes. For example, a GitLab token needs the `api` and `read_user` scopes; a GitLab Project Access Token needs the `api` scope and a **Developer** (or higher) role.
2. Update the token in Mobb from the **Integrations** page (select your SCM and reconnect).
3. Confirm the token has not expired and that the account it belongs to can access the repositories you expect.

For on-premises SCMs connected through the broker, follow the platform-specific guide in [Update Broker Token](/mobb-user-docs/more-info/update-broker-token.md).

{% hint style="info" %}
Still stuck? Contact <support@mobb.ai>.
{% endhint %}