PR comments

Author: pjlast

docs/admin/access_control/service_accounts.mdx

@@ -1,21 +1,22 @@
 # Service Accounts
 
-Service accounts are specialized user accounts designed for automation, API integrations, and programmatic access to Sourcegraph, as opposed to using access tokens from regular users. Unlike regular user accounts, service accounts don't require an email address or password and cannot access the Sourcegraph UI. They are specifically intended for automated workflows, CI/CD pipelines, scripts, and other non-human access patterns. Service accounts also don't count towards the user limit and won't be part of any billing cycles.
+Service accounts are specialized user accounts designed for automation, API integrations, and programmatic access to Sourcegraph, as opposed to using access tokens from regular users. Unlike regular user accounts, service accounts don't require an email address or password, cannot access the Sourcegraph UI, don't count towards a license's user limit and won't be part of any billing cycles.
 
 ## Creating Service Accounts
 
 Service accounts are created like regular user accounts, but with a few key differences.
 
 - Go to **Site admin** → **Users & auth** → **Users**
 - Click **Create User**
-- Enter a descriptive **Username** (e.g., `ci-automation`, `api-integration`)
+- Enter a descriptive **Username** (e.g., `ci-bot-scip-uploads`, `api-search-jobs`)
 - Check the **Service account** checkbox
 - Click **Create service account**
 
 You'll be presented with some next steps you might want to take, like creating an access token, managing and assigning roles, and managing repository permissions.
 
 - Service accounts are automatically assigned the "Service Account" system role
 - They appear in the user list with "Service account" type designation
+- By default, service accounts can only access public and unrestricted repositories
 
 ## Managing Access Tokens
 
@@ -47,4 +48,4 @@ Administrators can assign additional roles to service accounts through the user
 
 Service accounts respect repository permissions and access controls. For comprehensive information about repository permissions, see the [Repository permissions](/admin/permissions) documentation.
 
-Service accounts cannot have external service accounts. If service accounts need access to private repositories, they must explicitly be granted access to those repositories. This can be done from the service account's user settings page, under the **Repo permissions** tab, or via [the GraphQL API](/admin/permissions/api#explicit-permissions-api).
+Service accounts by default can only access public and unrestricted repositories in Sourcegraph. You may explicitly grant fine-grained access to private repositories from the service account's user settings page, under the **Repo permissions** tab, or via [the GraphQL API](/admin/permissions/api#explicit-permissions-api).