diff --git a/projects/ProvinceSystem/docs/integrations/servers.md b/projects/ProvinceSystem/docs/integrations/servers.md
index 08fc4f6..cb7a9dc 100644
--- a/projects/ProvinceSystem/docs/integrations/servers.md
+++ b/projects/ProvinceSystem/docs/integrations/servers.md
@@ -68,11 +68,13 @@ since the last startup is not detected.
 | `SERVERS_GITHUB_TOKEN` | A read-only GitHub token, falling back to `PATCHNOTES_GITHUB_TOKEN`. Each check discovers active repositories afresh, then reads current releases in groups of eight with at most six queries concurrently. Without a token, fresh REST reads remain available but can quickly reach GitHub’s unauthenticated limit. |
 | `SERVERS_GITHUB_ORG` | The organisation to read. Defaults to `TF-Minecraft`. |
 
-Main loads its token from `backend/.env`. Dev's staging Compose file loads its
-optional project-root `.env` as a backend environment file; keep only the shared
-`SERVERS_GITHUB_TOKEN` there. This works with the host's environment override.
-These secret files stay outside Git. Recreate the backend through the deployment
-workflow after changing either file.
+Main loads its token from `backend/.env`. Configure Dev's administrator-managed
+Compose override to load a token-only project-root `.env` with `env_file`, using
+the same read-only `SERVERS_GITHUB_TOKEN`. The host's `environment: !override`
+can discard entries from the base Compose file; an environment file avoids that.
+Keep secret files outside Git and recreate the backend after configuration changes.
+The deployment account's read-only Compose mounts require administrator access
+for this wiring.
 
 Mount the folders read-only in the host's `docker-compose.override.yml`: