docs: shorten GitLab token scope explanations

platform/repositories/gitlab.mdx

@@ -5,14 +5,14 @@
 
 ## Choose an access level
 
 Hacktron supports two GitLab access options. Choose the service account's role
 based on who will manage webhooks and repository clone credentials.
 
 <Tip>
   **Maintainer: automatic setup (recommended)**
 
 GitLab requires Maintainer access to create project webhooks and read-only
 clone credentials. With this role, Hacktron manages both automatically for
 your selected projects.
 
 </Tip>
@@ -20,7 +20,7 @@
 <Info>
   **Developer: manual setup**
 
 Developer access lets Hacktron read merge requests and post review comments.
 A [read-only deploy token provides repository cloning access](#developer-access-setup),
 and a GitLab Maintainer or Owner configures the webhook separately. This lets
 the service account stay at Developer access while an authorized person
@@ -30,7 +30,7 @@
 
 ## Prerequisites
 
 You need to be a Hacktron organization admin to connect GitLab and manage its settings.
 
 A GitLab group Owner creates the service account. For the Developer option,
 you also need someone with permission to create deploy tokens and webhooks:
@@ -41,7 +41,7 @@
 
 <Steps>
   <Step title="Open Service Accounts page">
       In GitLab, under the group you want to connect to Hacktron, go to
       **Settings** and select **Service Accounts**.
     <img src="/images/gitlab_sa.png" alt="GitLab Service Accounts" />
   </Step>
@@ -54,7 +54,7 @@
 
   </Step>
   <Step title="Choose the service account's access level">
     Grant access to the group or projects you want Hacktron to scan.
 
     <Tabs>
       <Tab title="Maintainer (recommended)">
@@ -88,17 +88,10 @@
     <Info>
       **Why these token scopes?**
 
-      - `api` lets Hacktron post review comments. With Maintainer access, it also
-        lets Hacktron create and manage project webhooks and read-only clone
-        credentials. These write operations need more than read-only API access.
-      - `read_api` covers reading project and merge request information,
-        including the diffs Hacktron reviews.
-      - `read_user` covers reading the connected account's profile so Hacktron
-        can identify the service account during connection.
-
-      GitLab's [`api` scope](https://docs.gitlab.com/security/tokens/access_token_scopes/)
-      includes these read capabilities. Hacktron's connection form lists all
-      three scopes. Token scopes do not raise the account's GitLab project role.
+      - `api`: Post review comments and, with Maintainer access, manage webhooks
+        and clone credentials.
+      - `read_api`: Read project and merge request information, including diffs.
+      - `read_user`: Identify the connected service account.
     </Info>
 
     <Warning>
@@ -107,7 +100,7 @@
 
   </Step>
   <Step title="Connect GitLab">
     In Hacktron, go to **Integrations** and click **Connect** under **GitLab**.
     Paste the personal access token and click **Connect GitLab**.
 
     <img
@@ -117,7 +110,7 @@
 
   </Step>
   <Step title="Select projects">
     Go to **Repositories** and select the GitLab projects Hacktron can access.
 
     With Maintainer access, webhook setup is automatic. With Developer access,
     complete the setup below before starting scans.
@@ -130,7 +123,7 @@
 
 ## Developer access setup
 
 Complete these steps when the service account has Developer access. Hacktron
 shows **Needs setup** until a deploy token is saved.
 
 <Steps>
@@ -150,7 +143,7 @@
     </Note>
 
   </Step>
   <Step title="Save the deploy token in Hacktron">
     Open **Integrations** → **GitLab** → **Manage**. Under **Webhooks and deploy
     tokens**, enter **Deploy token username** and **Deploy token**, then click
     **Save**.
@@ -162,7 +155,7 @@
 
   </Step>
   <Step title="Configure the webhook in GitLab">
     In the same Hacktron panel, copy the webhook **URL** and **Secret token**.
 
     In GitLab, open **Settings** → **Webhooks** on each selected project and
     click **Add new webhook**. Paste the full URL, including its query string,
@@ -214,6 +207,6 @@
 GitLab Enterprise** and enter your instance's base URL (e.g.
 `https://gitlab.example.com`) before entering the token.
 
 - Your GitLab instance must be reachable from Hacktron over HTTPS with a valid TLS certificate.
 - GitLab installed under a URL subpath (e.g. `https://example.com/gitlab`) is not supported. Use the instance's base URL.
 - For Developer access, use the webhook URL and secret shown in Hacktron for this connection.