diff --git a/documentation-metadata.json b/documentation-metadata.json
index 891dea8..8035142 100644
--- a/documentation-metadata.json
+++ b/documentation-metadata.json
@@ -53,6 +53,66 @@
         "helm-charts": "78b680595d4beda3184124312d61d86ce0cc51e7",
         "lifecycle-opentofu": "b14865912608096379c28ef648f7ed99538b5600"
       }
+    },
+    "2026-09-14-sites-pending-release": {
+      "verifiedOn": "2026-09-14",
+      "sources": {
+        "lifecycle": "3e313fae532c4997c595e676e551a4f590dcc691",
+        "lifecycle-ui": "ab98c292aa2155ca0a08e62d6a9823507feeecd6",
+        "lifecycle-cli": "14552f966cc0eff3e4bb067a1f072f2d0b9dd57a",
+        "helm-charts": "992cfe38aa1175ea2acef517932a38f9dd974fef"
+      },
+      "notes": "These commits identify baseline checkouts only. Sites access-control behavior was reviewed in uncommitted working trees and is pending release. Replace this baseline with implementing commit revisions before publication."
+    },
+    "2026-09-21-sites-downgrade-pending-release": {
+      "verifiedOn": "2026-09-21",
+      "sources": {
+        "lifecycle": "5a95f69995272b9dec92c8a3c067458be46a65d4",
+        "lifecycle-ui": "a8d65d351d68ca7466d4368d9eb4018bd46621aa",
+        "lifecycle-cli": "6814da76083fa989ffcc967e433b931d40f1dd7f",
+        "helm-charts": "0b5a50890635c7941984aaff622cc6e4fe79d1c1"
+      },
+      "notes": "Sites V1 remains pending release. The core migration supports an intentional full downgrade that preserves Site rows and versions but publishes content through the older gateway and discards ACL metadata. An isolated PostgreSQL up/down/up test passed."
+    },
+    "2026-09-21-sites-ui-filter-pending-release": {
+      "verifiedOn": "2026-09-21",
+      "sources": {
+        "lifecycle": "4343694b08c158832f6fd269b81d848bcdaf9077",
+        "lifecycle-ui": "a8d65d351d68ca7466d4368d9eb4018bd46621aa",
+        "lifecycle-cli": "6814da76083fa989ffcc967e433b931d40f1dd7f",
+        "helm-charts": "0b5a50890635c7941984aaff622cc6e4fe79d1c1"
+      },
+      "notes": "Sites V1 behavior remains pending release. The UI offers My sites and Public list views; the API also supports view=all for other clients."
+    },
+    "2026-09-15-sites-rollout-pending-release": {
+      "verifiedOn": "2026-09-15",
+      "sources": {
+        "lifecycle": "d2af3d1f651dcfb1e38b38619ebfd89ab2760012",
+        "lifecycle-ui": "b925d650870109859deca23e218f298e349b2879",
+        "lifecycle-cli": "6814da76083fa989ffcc967e433b931d40f1dd7f",
+        "helm-charts": "4acd7917c4f19f4f0d8420af3f62e5db43438e3f"
+      },
+      "notes": "Sites access-control behavior was verified against these implementing commits and remains pending release. User JWTs authorize Site-only browser access, capped at five minutes and JWT expiry. Private reads check current Site state. Ordinary UI logout does not immediately revoke issued access. These checks do not establish a supported released version set or production rollout."
+    },
+    "2026-09-22-sites-stable-url-pending-release": {
+      "verifiedOn": "2026-09-22",
+      "sources": {
+        "lifecycle": "0af126b06788110e5db4762b9b7fe4d7491de8e1",
+        "lifecycle-ui": "eb73479ddc0543bf133a9d8146334e94641ae88e",
+        "lifecycle-cli": "8dab9f14b45673703f3244ae220919042f0805bd",
+        "helm-charts": "0b5a50890635c7941984aaff622cc6e4fe79d1c1"
+      },
+      "notes": "Sites V1 remains pending release. Verified stable Site ID and content URL on visibility changes, server owner checks, the temporary same-apex opt-in, and the intentional full downgrade. Live browser retest of private open remains pending."
+    },
+    "2026-09-22-sites-access-control-released": {
+      "verifiedOn": "2026-09-22",
+      "sources": {
+        "lifecycle": "e50c29f7659fc14dc98f061e0c8fa57b40b788c0",
+        "lifecycle-ui": "917d8a8936b6054ae9fc102571a5b9c808a0bcb7",
+        "lifecycle-cli": "a08d9c2d0abb79ab7941c12d6ead1783a70ea45f",
+        "helm-charts": "6aff91c22411e641964774bcbb09e5265ac1250c"
+      },
+      "notes": "All four Sites access-control implementing PRs merged to main and deployed to production. Live-verified end to end: owner-only private access, distinct denied-vs-missing responses on the management API, the CLI's visibility/create/list/get/update/extend/delete commands, the shared-apex opt-in, stable Site ID and content URL across visibility and content changes, and the intentional full downgrade path."
     }
   }
 }
diff --git a/documentation-style-baseline.json b/documentation-style-baseline.json
index efe69eb..95c3247 100644
--- a/documentation-style-baseline.json
+++ b/documentation-style-baseline.json
@@ -1,6 +1,6 @@
 {
   "schemaVersion": 3,
-  "updatedOn": "2026-08-01",
+  "updatedOn": "2026-09-23",
   "references": {
     "canonical": "ASD-STE100 Issue 9",
     "canonicalRules": [
@@ -69,8 +69,8 @@
     "/docs/api-authentication/api-keys": {
       "file": "src/pages/docs/api-authentication/api-keys.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-07-25",
-      "sha256": "abccff28a910388f751789b3cd1ba7aba1ef81fc98e31ba66379427332eb6257"
+      "reviewedOn": "2026-09-23",
+      "sha256": "6ab98c32c5f8ebf35d609cdb62d6d67820fbaa6cc9ece818537948ab86eb4aa6"
     },
     "/docs/api-authentication/overview": {
       "file": "src/pages/docs/api-authentication/overview.mdx",
@@ -135,8 +135,8 @@
     "/docs/features/cli": {
       "file": "src/pages/docs/features/cli.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-08-01",
-      "sha256": "88a35c2ebf6bb6ac52874de2df6edd96b99dab582e6e3de3414226d12cbe5c7c"
+      "reviewedOn": "2026-09-22",
+      "sha256": "0f57d131ad05effbf05847828dd7f30d8b5641c5ecde54af181c3aec6821e15b"
     },
     "/docs/features/cli-telemetry": {
       "file": "src/pages/docs/features/cli-telemetry.mdx",
@@ -177,8 +177,8 @@
     "/docs/features/mcp-server": {
       "file": "src/pages/docs/features/mcp-server.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-08-01",
-      "sha256": "69ab72bfb6486d0189fc903d4a3d8e170c578be252d39335b7bea8e7c8b0da36"
+      "reviewedOn": "2026-09-22",
+      "sha256": "70ab60a321461fb609365c7184ad40fd7450e1ae68271748681b87be80d7e699"
     },
     "/docs/features/native-helm-deployment": {
       "file": "src/pages/docs/features/native-helm-deployment.mdx",
@@ -201,8 +201,8 @@
     "/docs/features/sites": {
       "file": "src/pages/docs/features/sites.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-07-25",
-      "sha256": "598f40560777f7d3f2074137ba9b2a102ceb4f61946fc05bc74f3a85d64d6bca"
+      "reviewedOn": "2026-09-23",
+      "sha256": "7a1bbdb4b545c7fcba428fc4f4eaa336ee6f556916ee4cb9f2371203cdfaf1e8"
     },
     "/docs/features/template-variables": {
       "file": "src/pages/docs/features/template-variables.mdx",
@@ -273,8 +273,8 @@
     "/docs/operations/configuration": {
       "file": "src/pages/docs/operations/configuration.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-08-01",
-      "sha256": "dcf78161c9d44e74638153de0f0b074361ba9ac6a8878a41338d35716860d755"
+      "reviewedOn": "2026-09-22",
+      "sha256": "fd1c2f4537187df8dfced9799dec480e5754c6ba519f548d244f65f66666717f"
     },
     "/docs/operations/day-two": {
       "file": "src/pages/docs/operations/day-two.mdx",
@@ -291,8 +291,8 @@
     "/docs/operations/security": {
       "file": "src/pages/docs/operations/security.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-07-25",
-      "sha256": "892aafebdd33b0c39b51f5c8ae6817e067679e3797d02eaaceee949b6ce13365"
+      "reviewedOn": "2026-09-23",
+      "sha256": "0d56688220d7f4a802d79f085237ae6f8b9d57ec5e7566bc3e650ac401583b4d"
     },
     "/docs/reference/statuses": {
       "file": "src/pages/docs/reference/statuses.mdx",
@@ -309,7 +309,7 @@
     "/docs/releases/compatibility": {
       "file": "src/pages/docs/releases/compatibility.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-07-25",
+      "reviewedOn": "2026-09-23",
       "sha256": "1901b9d61ca33af98a41c41382624e7c07607c6cbaffb112e71718c3e17bbb1f"
     },
     "/docs/schema/aurora-restore": {
@@ -387,7 +387,7 @@
     "/docs/setup/install-lifecycle": {
       "file": "src/pages/docs/setup/install-lifecycle.mdx",
       "profile": "asd-ste100",
-      "reviewedOn": "2026-07-25",
+      "reviewedOn": "2026-09-23",
       "sha256": "675a15ac05fef8f53b5cd2e177eb24b1fac1f745e5189ae6d8fc3133d9580a0c"
     },
     "/docs/setup/prerequisites": {
diff --git a/public/llms.txt b/public/llms.txt
index a54e48a..f8fb8f8 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -32,22 +32,22 @@ This index is generated from the human documentation. Follow the linked page for
 - [Cloud secrets](https://uselifecycle.com/docs/features/secrets.md): Reference External Secrets Operator values from Lifecycle Services and native Helm deployments. _(audience: application-developer, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Environment expiration and cleanup](https://uselifecycle.com/docs/features/environment-ttl.md): Understand how Lifecycle cleans up pull-request environments and expires API-created environments. _(audience: application-developer, platform-operator, administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [API-created Environments](https://uselifecycle.com/docs/features/api-environments.md): Create branch-based Lifecycle Environments without a pull request. Then, track, extend, redeploy, or tear them down. _(audience: api-user, application-developer; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
-- [Sites](https://uselifecycle.com/docs/features/sites.md): Upload and manage static HTML sites through Lifecycle's UI, CLI, or authenticated v2 API. _(audience: application-developer, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
+- [Sites](https://uselifecycle.com/docs/features/sites.md): Upload and manage static HTML sites through Lifecycle's UI, CLI, or authenticated v2 API. _(audience: application-developer, platform-operator; last verified: 2026-09-23; baseline: 2026-09-22-sites-access-control-released)_
 - [Lifecycle Agent](https://uselifecycle.com/docs/features/ai-agent.md): Investigate a Lifecycle Environment, examine evidence, and do approved recovery tasks from the Environment details page. _(audience: agent-user; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Configure Lifecycle Agent](https://uselifecycle.com/docs/features/ai-agent-configuration.md): Configure models, instructions, tools, approvals, and repository overrides for Lifecycle Agent from Settings. _(audience: administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Agent Sessions](https://uselifecycle.com/docs/features/agent-sessions.md): Start, examine, and continue repository work with Lifecycle Agent in an isolated workspace. _(audience: agent-user; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Agent administration](https://uselifecycle.com/docs/features/agent-administration.md): Administer Lifecycle Agent availability, models, instructions, permissions, tools, workspaces, and session audit. _(audience: administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Agent workspace backends](https://uselifecycle.com/docs/features/workspace-backends.md): Compare and safely activate the runtime backend used for new Lifecycle Agent workspaces. _(audience: administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Connect external MCP servers](https://uselifecycle.com/docs/features/mcp-integration.md): Add administrator-approved Model Context Protocol servers and complete authentication for each Lifecycle Agent user. _(audience: agent-user, administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
-- [Lifecycle MCP](https://uselifecycle.com/docs/features/mcp-server.md): Enable Lifecycle MCP, connect an OAuth client, and use Lifecycle tools with existing user permissions. _(audience: agent-user, administrator, platform-operator; last verified: 2026-08-01; baseline: 2026-08-01-lifecycle-mcp-preparation)_
-- [CLI (lfc)](https://uselifecycle.com/docs/features/cli.md): Install and use the Lifecycle CLI to examine Environments, manage Services, stream logs, and validate configuration. _(audience: application-developer, platform-operator; last verified: 2026-08-01; baseline: 2026-08-01-configuration-schema-fix)_
+- [Lifecycle MCP](https://uselifecycle.com/docs/features/mcp-server.md): Enable Lifecycle MCP, connect an OAuth client, and use Lifecycle tools with existing user permissions. _(audience: agent-user, administrator, platform-operator; last verified: 2026-09-22; baseline: 2026-09-22-sites-access-control-released)_
+- [CLI (lfc)](https://uselifecycle.com/docs/features/cli.md): Install and use the Lifecycle CLI to examine Environments, manage Services, stream logs, and validate configuration. _(audience: application-developer, platform-operator; last verified: 2026-09-22; baseline: 2026-09-22-sites-access-control-released)_
 - [Lifecycle CLI telemetry](https://uselifecycle.com/docs/features/cli-telemetry.md): Understand the pseudonymous command-usage event sent by lfc, its destination, and how to opt out. _(audience: application-developer, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Use the Lifecycle UI](https://uselifecycle.com/docs/features/lifecycle-ui.md): Use the web UI to find Environments, examine Services and logs, run actions, and examine webhooks. _(audience: application-developer, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 
 ## API authentication
 
 - [API authentication](https://uselifecycle.com/docs/api-authentication/overview.md): Select a supported authentication method for Lifecycle v2 API requests and understand typical authorization failures. _(audience: api-user, administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
-- [API keys](https://uselifecycle.com/docs/api-authentication/api-keys.md): Create, scope, use, rotate, and revoke personal or service API keys for authenticated Lifecycle v2 requests. _(audience: api-user, administrator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
+- [API keys](https://uselifecycle.com/docs/api-authentication/api-keys.md): Create, scope, use, rotate, and revoke personal or service API keys for authenticated Lifecycle v2 requests. _(audience: api-user, administrator; last verified: 2026-09-23; baseline: 2026-09-22-sites-access-control-released)_
 
 ## HTTP API
 
@@ -74,22 +74,22 @@ This index is generated from the human documentation. Follow the linked page for
 
 - [Starter infrastructure prerequisites](https://uselifecycle.com/docs/setup/prerequisites.md): Prepare cloud, DNS, domain, and command-line access for the starter OpenTofu evaluation path. _(audience: evaluator, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Set up an evaluation cluster](https://uselifecycle.com/docs/setup/setup-infra.md): Provision starter GKE or EKS infrastructure, DNS, dependencies, and Lifecycle for evaluation. _(audience: evaluator, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
-- [Install Lifecycle](https://uselifecycle.com/docs/setup/install-lifecycle.md): Select the OpenTofu-managed or standalone Helm installation path. Make sure that the API, UI, identity, and cluster are healthy. _(audience: evaluator, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
+- [Install Lifecycle](https://uselifecycle.com/docs/setup/install-lifecycle.md): Select the OpenTofu-managed or standalone Helm installation path. Make sure that the API, UI, identity, and cluster are healthy. _(audience: evaluator, platform-operator; last verified: 2026-09-23; baseline: 2026-09-22-sites-access-control-released)_
 - [Create the GitHub App](https://uselifecycle.com/docs/setup/create-github-app.md): Create and connect a private GitHub App for Lifecycle. _(audience: platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Optional configuration](https://uselifecycle.com/docs/setup/configure-lifecycle.md): Apply optional installation-wide settings safely after Lifecycle is running. _(audience: platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 
 ## Operations
 
 - [Lifecycle architecture](https://uselifecycle.com/docs/operations/architecture.md): Understand how requests become Lifecycle Environments and plan dependencies, security controls, availability, and recovery. _(audience: evaluator, platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
-- [Runtime configuration surfaces](https://uselifecycle.com/docs/operations/configuration.md): Select a supported UI, API, Helm, or repository configuration surface and verify each change. _(audience: platform-operator, administrator; last verified: 2026-08-01; baseline: 2026-08-01-lifecycle-mcp-preparation)_
-- [Security boundaries](https://uselifecycle.com/docs/operations/security.md): Understand Lifecycle authentication, network, Kubernetes, secret, and Agent boundaries before other networks can reach a deployment. _(audience: platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
+- [Runtime configuration surfaces](https://uselifecycle.com/docs/operations/configuration.md): Select a supported UI, API, Helm, or repository configuration surface and verify each change. _(audience: platform-operator, administrator; last verified: 2026-09-22; baseline: 2026-09-22-sites-access-control-released)_
+- [Security boundaries](https://uselifecycle.com/docs/operations/security.md): Understand Lifecycle authentication, network, Kubernetes, secret, and Agent boundaries before other networks can reach a deployment. _(audience: platform-operator; last verified: 2026-09-23; baseline: 2026-09-22-sites-access-control-released)_
 - [Monitor Lifecycle](https://uselifecycle.com/docs/operations/monitoring.md): Interpret health endpoints, verify end-to-end operation, and collect safe diagnostic data for stuck work. _(audience: platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 - [Day-two operations](https://uselifecycle.com/docs/operations/day-two.md): Plan Lifecycle upgrades, backups, rollback decisions, recovery validation, and uninstall. _(audience: platform-operator; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
 
 ## Releases and compatibility
 
 - [Releases](https://uselifecycle.com/docs/releases.md): Find your installed Lifecycle versions and the release information for an upgrade. _(audience: platform-operator, application-developer; last verified: 2026-08-01; baseline: 2026-08-01-adopt-lifecycle-mcp-browser-validation)_
-- [Compatibility and deprecation policy](https://uselifecycle.com/docs/releases/compatibility.md): Select compatible Lifecycle components and prepare a safe upgrade or rollback. _(audience: platform-operator, application-developer; last verified: 2026-07-24; baseline: 2026-07-24-comprehensive-audit)_
+- [Compatibility and deprecation policy](https://uselifecycle.com/docs/releases/compatibility.md): Select compatible Lifecycle components and prepare a safe upgrade or rollback. _(audience: platform-operator, application-developer; last verified: 2026-09-23; baseline: 2026-09-22-sites-access-control-released)_
 
 ## Troubleshooting
 
diff --git a/src/pages/docs/api-authentication/api-keys.mdx b/src/pages/docs/api-authentication/api-keys.mdx
index 0f0a4aa..66c9d1c 100644
--- a/src/pages/docs/api-authentication/api-keys.mdx
+++ b/src/pages/docs/api-authentication/api-keys.mdx
@@ -4,8 +4,8 @@ description: Create, scope, use, rotate, and revoke personal or service API keys
 audience:
   - api-user
   - administrator
-lastVerified: "2026-07-24"
-verificationBaseline: "2026-07-24-comprehensive-audit"
+lastVerified: "2026-09-23"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - api
@@ -54,15 +54,15 @@ creation.
 
 Lifecycle recognizes seven scopes:
 
-| Scope         | Access                                                              |
-| ------------- | ------------------------------------------------------------------- |
-| `env:read`    | Read Environments and Builds                                        |
-| `env:write`   | Create or change Environments and Builds. Also satisfies `env:read` |
-| `sites:read`  | Read sites. `sites:write` satisfies this scope.                     |
-| `sites:write` | Upload, replace, extend, or delete sites                            |
-| `repos:read`  | Read repository information. `repos:write` satisfies this scope.    |
-| `repos:write` | Change supported repository configuration                           |
-| `env:admin`   | Legacy/reserved Environment administration                          |
+| Scope         | Access                                                               |
+| ------------- | -------------------------------------------------------------------- |
+| `env:read`    | Read Environments and Builds                                         |
+| `env:write`   | Create or change Environments and Builds. Also satisfies `env:read`. |
+| `sites:read`  | Read sites. `sites:write` satisfies this scope.                      |
+| `sites:write` | Upload, replace, extend, or delete sites                             |
+| `repos:read`  | Read repository information. `repos:write` satisfies this scope.     |
+| `repos:write` | Change supported repository configuration                            |
+| `env:admin`   | Legacy/reserved Environment administration                           |
 
 New keys can request only the first six scopes. A legacy service key can keep
 `env:admin`. You cannot grant this scope to a new key.
@@ -76,6 +76,28 @@ grant `sites:read`.
   repositories.
 </Callout>
 
+## Sites access with API keys
+
+`sites:read` permits public reads and reads of sites owned by the caller.
+`sites:write` also permits creation and changes to owned sites, including visibility changes.
+Scopes do not grant access to another user's private site.
+Administrator status does not override ownership.
+
+A personal key uses its user's ownership and defaults to private uploads.
+An older personal key without an identity binding cannot access Sites.
+Create a replacement personal key through your signed-in account.
+
+Service keys create public sites only.
+Each service key owns only the sites created with that exact key.
+A replacement service key does not inherit site ownership.
+Before you retire a service key that owns sites, contact your platform operator.
+Revoked or expired keys cannot manage their sites.
+For sites with retired keys, see [Sites troubleshooting](/docs/features/sites#troubleshooting).
+
+Keep API keys in authorization headers.
+Do not put API keys in site content or URLs.
+For request details, see [Sites](/docs/features/sites#api-access).
+
 ## Select an expiration
 
 The personal-key policy defaults to a 168-hour (7-day) selection and caps finite
diff --git a/src/pages/docs/features/cli.mdx b/src/pages/docs/features/cli.mdx
index 40a6f38..1def2b0 100644
--- a/src/pages/docs/features/cli.mdx
+++ b/src/pages/docs/features/cli.mdx
@@ -4,8 +4,8 @@ description: Install and use the Lifecycle CLI to examine Environments, manage S
 audience:
   - application-developer
   - platform-operator
-lastVerified: "2026-08-01"
-verificationBaseline: "2026-08-01-configuration-schema-fix"
+lastVerified: "2026-09-22"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - cli
@@ -222,15 +222,27 @@ each field. Exit code `3` means that the CLI did not find a configuration file.
 
 ### Static sites
 
+User uploads default to private.
+Public uploads require confirmation when you specify `--visibility public`.
+Only the owner can change a site.
+`--mine` selects ownership, and `--public` selects public sites.
+These filters cannot be combined.
+
 ```sh
-lfc sites create <file-or-dir> [--name <label>]   # returns a stable URL
-lfc sites list [--mine]
+lfc sites create <file-or-dir> [--name <label>] [--visibility private|public] [--yes]
+lfc sites list [--mine | --public] [--search <text>]
 lfc sites get <id>
 lfc sites update <id> <file-or-dir>
-lfc sites extend <id>                             # push out the expiry
+lfc sites visibility <id> private|public [--yes]
+lfc sites extend <id>                             # extend expiration
 lfc sites delete <id> --yes
 ```
 
+The CLI prints the site's `openUrl`.
+Changing visibility keeps the Site ID and content URL.
+If a change returns `409`, fetch the site again before you retry.
+See [Sites](/docs/features/sites) for access rules and API details.
+
 ### Diagnostics & agent instructions
 
 ```sh
diff --git a/src/pages/docs/features/mcp-server.mdx b/src/pages/docs/features/mcp-server.mdx
index d2bb352..faa15bd 100644
--- a/src/pages/docs/features/mcp-server.mdx
+++ b/src/pages/docs/features/mcp-server.mdx
@@ -5,8 +5,8 @@ audience:
   - agent-user
   - administrator
   - platform-operator
-lastVerified: "2026-08-01"
-verificationBaseline: "2026-08-01-lifecycle-mcp-preparation"
+lastVerified: "2026-09-22"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - mcp
@@ -90,6 +90,16 @@ When Sites is enabled, these tools are available:
 | `list_sites` | Lists visible Sites   |
 | `get_site`   | Gets one visible Site |
 
+<Callout type="info">
+  These tools return the user's private sites and public sites. `mineOnly`
+  selects ownership rather than creator or updater email. Sites tools provide
+  read access only.
+</Callout>
+
+Results include visibility and `openUrl`.
+A private site's URL does not grant access to another user.
+The tools do not publish sites or send email invitations.
+
 An administrator can turn off all change tools. When change tools are off,
 clients do not discover them, and Lifecycle rejects their invocation.
 
diff --git a/src/pages/docs/features/sites.mdx b/src/pages/docs/features/sites.mdx
index 3bc89b6..49ada49 100644
--- a/src/pages/docs/features/sites.mdx
+++ b/src/pages/docs/features/sites.mdx
@@ -4,8 +4,8 @@ description: Upload and manage static HTML sites through Lifecycle's UI, CLI, or
 audience:
   - application-developer
   - platform-operator
-lastVerified: "2026-07-24"
-verificationBaseline: "2026-07-24-comprehensive-audit"
+lastVerified: "2026-09-23"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - sites
@@ -16,101 +16,178 @@ tags:
 
 import { Callout } from "nextra/components";
 
-Sites publishes a static HTML file or ZIP archive at a stable Lifecycle URL. It
-is useful for generated reports, prototypes, and documentation previews. A
-server-side application is not necessary.
+Sites hosts static HTML files and ZIP archives for reports, prototypes, and documentation previews.
+A server-side application is not necessary.
 
 <Callout type="warning">
-  Sites requires storage, gateway, DNS, and authentication configuration. If
-  **Sites** is not available, contact your deployment owner.
+  Sites requires storage, gateway, DNS, TLS, and authentication configuration.
+  If **Sites** is unavailable, contact your platform operator.
 </Callout>
 
+## Choose who can access a site
+
+New sites from your user account are private by default.
+Administrator access does not give ownership rights.
+
+| Visibility        | Who can view it                         | Who can change it |
+| ----------------- | --------------------------------------- | ----------------- |
+| Private (default) | Only the owner                          | Only the owner    |
+| Public            | Anyone with the URL, without signing in | Only the owner    |
+
+The owner can replace content, extend expiration, delete the site, or change visibility.
+Public content can contain copies that remain outside Lifecycle after you make the site private.
+Sites has no email invitations or viewer or editor roles.
+
 ## Upload from the UI
 
 1. Open **Sites**.
 2. Select **Add site**.
-3. Select one HTML file or a ZIP archive with the entry point that your
-   deployment's upload policy requires.
+3. Select an HTML file or ZIP archive with the required entry file.
 4. Add an optional display name.
-5. Examine the file.
-6. Upload the file.
-7. Open the returned URL.
-8. Make sure that its content is correct.
-
-Use search plus **All sites** or **My sites** to find an upload. From a site's
-actions menu you can replace its content or delete it.
-
-<Callout type="info">
-  **My sites** is a convenience filter based on creator or updater identity. It
-  does not make a site private. A caller with `sites:read` can list active
-  sites.
-</Callout>
+5. Select **Private** or **Public**.
+6. Examine the visibility and file.
+7. Select **Upload private site** or **Publish site**.
+8. Open the returned URL.
+9. Make sure that the content and assets are correct.
+
+**My sites** shows sites that you own.
+**Public** shows public sites.
+Search matches the site name or ID.
+Search and pagination do not expose other users' private sites.
+
+From an owned site's actions menu, you can replace content, change visibility, or delete it.
+The visibility dialog requires confirmation before publication.
+When you change visibility, the site ID and content URL stay the same.
+New requests to a private site require owner access.
 
 ## Upload a directory with the CLI
 
-The CLI can upload a ZIP, one HTML file, or a directory:
+The CLI accepts a ZIP, HTML file, or directory:
 
 ```bash
 lfc sites create ./dist --name "performance report"
+lfc sites create ./dist --visibility public --yes
 lfc sites list --mine
+lfc sites list --public --search report
 lfc sites get a1b2c3d4e5
 lfc sites update a1b2c3d4e5 ./dist
+lfc sites visibility a1b2c3d4e5 private --yes
 lfc sites extend a1b2c3d4e5
 lfc sites delete a1b2c3d4e5 --yes
 ```
 
-For a directory, `lfc` builds the ZIP locally. It applies built-in ignores such
-as `.git`, `node_modules`, cache directories, and coverage output. Add an
-`.lfcsiteignore` file for patterns in the repository.
+Omitting `--visibility` uses the server's default for your credentials.
+With user sign-in, that default is private.
+An explicit public upload requires confirmation or `--yes`.
+The CLI uses user sign-in and has no dedicated API-key input.
 
-Before creating or updating a site, the CLI fetches the deployment's upload
-policy and checks allowed extensions, file count, extracted size, and upload
-size.
+For a directory, `lfc` creates a ZIP locally.
+It excludes `.git`, `node_modules`, cache directories, and coverage output.
+Use `.lfcsiteignore` for additional exclusion patterns.
+Before an upload, the CLI checks the deployment's upload policy and allowed visibility.
 
-## Prepare static content
+## Prepare and replace content
 
-- Build the site locally. Lifecycle does not run a server-side build command.
-- When the site generator supports relative asset URLs, use them.
-- Include the entry file that your deployment's Sites policy specifies.
-- Remove source maps, credentials, and internal data. Remove output that is not
-  necessary.
-- Open the published URL.
-- Before you share the URL, check its navigation and assets.
+- Build the site locally.
+- When your site generator supports relative asset URLs, use them.
+- Include the entry file that the upload policy requires.
+- Remove credentials, internal data, source maps, and unnecessary output.
+- Before publication, check navigation and assets.
 
-When you replace content, the site keeps its URL. When you delete a site, its
-URL stops working. You cannot undo the deletion.
+A content replacement or visibility change preserves the current content URL.
+The API's `openUrl` opens the current site through Lifecycle.
+The `contentUrl` identifies the current content host.
+Neither URL grants access to a private site.
 
-## Expiration
+Deletion or expiration stops new content requests.
+Deletion cannot be undone.
+Content already downloaded or displayed can remain on a user's device.
+
+## Private access and logout
+
+Sign in as the owner to open a private site.
+Browser access expires within five minutes and no later than the authorizing JWT.
+If content stops loading after access expires, reopen the stable Site link.
+A valid user session can obtain access again after an ownership check.
 
-When the operator enables Sites TTL, a new site receives the deployment's
-configured expiration. **Extend** pushes the expiry out by the configured
-increment. When the operator disables TTL, a site can have no expiry.
+Ordinary UI logout does not immediately revoke issued access.
+There is no guaranteed fixed cutoff measured from logout.
+An unrelated signed-in user cannot open your private site.
 
-Use the expiry displayed by the UI or CLI. Do not use a fixed number of days.
-Get cleanup and previous-version retention information from the deployment
-owner.
+## Private content compatibility
+
+Private sites block Web Workers, SharedWorkers, and new service workers.
+Features that require these workers, including some offline features, do not work.
+Use a site build that works without browser workers.
+Private sites also block display inside an iframe.
+If a site was public, a service worker installed in a visitor's browser can remain after you make it private.
+For sensitive content, upload a new private site instead of changing the public site's visibility.
+
+## Expiration
+
+When the operator enables Sites TTL, new sites receive the configured expiration.
+The owner can extend expiration through the CLI or API.
+When TTL is disabled, a site can have no expiration.
+Use the displayed expiration instead of assuming a fixed number of days.
 
 ## API access
 
-Sites uses authenticated v2 routes:
+Management routes require authentication and the applicable scope.
+A scope permits an operation only when the caller also has the required ownership.
+
+| Task              | Route                                 | Scope         |
+| ----------------- | ------------------------------------- | ------------- |
+| Read capabilities | `GET /api/v2/sites/capabilities`      | `sites:read`  |
+| List sites        | `GET /api/v2/sites`                   | `sites:read`  |
+| Create a site     | `POST /api/v2/sites`                  | `sites:write` |
+| Get a site        | `GET /api/v2/sites/{siteId}`          | `sites:read`  |
+| Delete a site     | `DELETE /api/v2/sites/{siteId}`       | `sites:write` |
+| Replace content   | `PUT /api/v2/sites/{siteId}/content`  | `sites:write` |
+| Extend expiration | `POST /api/v2/sites/{siteId}/extend`  | `sites:write` |
+| Change visibility | `PATCH /api/v2/sites/{siteId}/access` | `sites:write` |
+
+Capabilities contain `enabled`, `upload`, `defaultVisibility`, `allowedVisibilities`, and `canCreate`.
+Capabilities do not expose administrator configuration or storage credentials.
+List requests accept `view=mine|public|all`, `q`, `page`, and `limit`.
+Results use the pagination fields `items`, `total`, `current`, and `limit`.
+
+Create and content-replacement requests use `multipart/form-data`.
+Creation accepts optional `visibility`.
+A personal API key defaults to private sites.
+A service API key can create only public sites and defaults to public.
+The service key owns its sites through that exact key identity.
+
+Use an existing API key with `sites:write` in `LIFECYCLE_API_KEY`.
+Set `LIFECYCLE_URL` to your Lifecycle API origin.
+To upload an HTML file with the key's default visibility, run:
+
+```bash
+curl --fail --silent --show-error \
+  --header "Authorization: Bearer ${LIFECYCLE_API_KEY}" \
+  --form "file=@./report.html" \
+  "${LIFECYCLE_URL}/api/v2/sites"
+```
+
+Visibility changes require JSON fields `visibility` and `expectedAccessRevision`.
+For replacement, send `expectedAccessRevision` and `expectedContentRevision` as multipart fields.
+Delete and extend requests accept `expectedAccessRevision` as a query parameter.
+Older replacement clients can also receive `409` after a concurrent change.
 
-| Task            | Route                                    | Scope                         |
-| --------------- | ---------------------------------------- | ----------------------------- |
-| List or create  | `GET` or `POST /api/v2/sites`            | `sites:read` or `sites:write` |
-| Get or delete   | `GET` or `DELETE /api/v2/sites/{siteId}` | `sites:read` or `sites:write` |
-| Replace content | `PUT /api/v2/sites/{siteId}/content`     | `sites:write`                 |
-| Extend expiry   | `POST /api/v2/sites/{siteId}/extend`     | `sites:write`                 |
+For `409`, fetch the site again before you decide whether to retry.
+Do not automatically overwrite another change.
+Use `permissions` to show available actions and `currentRole` to identify ownership.
+Public results hide unrelated creator and updater identities.
 
-Uploads use `multipart/form-data`. Use the deployment-local generated API
-reference for the current limits and schema. See [API
-overview](/docs/api/overview) and [API
-keys](/docs/api-authentication/api-keys).
+See [API overview](/docs/api/overview) and [API keys](/docs/api-authentication/api-keys).
 
 ## Troubleshooting
 
-- **Sites is disabled or missing:** contact the deployment owner.
-- **The upload is rejected:** compare the file type, entry point, count, and
-  sizes with the policy returned by the deployment.
-- **Assets return 404:** rebuild with relative paths or the published base URL.
-- **A URL stopped working:** Lifecycle can expire a site, or a user can delete
-  it. Before you upload a replacement, examine the Sites list.
+| Symptom                       | Action                                                                                        |
+| ----------------------------- | --------------------------------------------------------------------------------------------- |
+| Private upload is unavailable | Ask the operator to check private Sites readiness.                                            |
+| Upload is rejected            | Compare the entry file, extensions, counts, and sizes with the returned upload policy.        |
+| A private URL does not open   | Sign in as the owner through the site's opening URL.                                          |
+| A site returns 404            | Check its current URL, visibility, and expiration through an authorized account.              |
+| A site has no assigned owner  | Contact your platform operator. Lifecycle has no self-service ownership transfer or recovery. |
+| Assets return 404             | Rebuild with relative paths or the current content base URL.                                  |
+| A change returns 409          | Fetch current site details before you retry the intended change.                              |
diff --git a/src/pages/docs/operations/configuration.mdx b/src/pages/docs/operations/configuration.mdx
index af46b1f..62fdb55 100644
--- a/src/pages/docs/operations/configuration.mdx
+++ b/src/pages/docs/operations/configuration.mdx
@@ -4,8 +4,8 @@ description: Select a supported UI, API, Helm, or repository configuration surfa
 audience:
   - platform-operator
   - administrator
-lastVerified: "2026-08-01"
-verificationBaseline: "2026-08-01-lifecycle-mcp-preparation"
+lastVerified: "2026-09-22"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - operator
@@ -49,6 +49,80 @@ For a supported change:
 Do not restart all components unless the applicable procedure tells you to do
 so.
 
+## Sites configuration
+
+Private Sites requires additional operator configuration.
+
+Administrators manage upload limits through `GET /api/v2/config/sites` and `PUT /api/v2/config/sites`.
+Ordinary Sites clients use `GET /api/v2/sites/capabilities` for upload limits and allowed visibility.
+The legacy configuration-cache endpoint requires administrator authentication and is not a Sites client interface.
+
+Sites uses its existing `enabled` setting in core configuration.
+No additional private-Sites feature flag is required.
+The chart supplies `LIFECYCLE_UI_URL` from `ui.config.appUrl` or the configured global UI domain.
+For a separately installed UI, set the core chart's existing `ui.config.appUrl` value.
+Private Sites requires HTTPS for the UI and content hosts.
+
+When possible, use a separate registrable content domain.
+If an internal deployment uses a shared registrable domain, set `SITES_ALLOW_SHARED_APEX=true` on both web and gateway.
+The chart supports this through each component's `deployment.extraEnv` list.
+
+The UI uses its existing application URL, API URL, and sign-in configuration.
+No additional UI Sites flag or shared bridge Secret is required.
+
+The gateway component must remain enabled.
+Disabling Sites stops all Sites uploads and content access, including public sites.
+It does not make private sites public.
+
+Private viewer access depends on Redis.
+Missing or corrupt authorization records prevent private access.
+Each browser access grant expires within five minutes and no later than its authorizing JWT.
+After expiry, reopen the stable Site link to obtain access with a valid user session.
+An existing Site cookie cannot renew itself.
+If Redis is unavailable, restore it before retrying private access.
+
+## Sites identity configuration
+
+Sites reuses the existing read-only identity client configured under `keycloak.clients.lifecycleApiPrincipalSync`.
+The chart supplies that client to worker and web workloads.
+The gateway does not receive this credential.
+Its existing client ID and Secret-reference overrides remain applicable.
+
+Human Sites management requires identity checks for public and private sites.
+New browser access grants also require identity checks.
+Do not substitute the identity management credential.
+
+Before replacing workloads, verify that the configured client can read user status, effective roles, and group roles.
+Verify that it can introspect incoming user access tokens.
+Use separate disposable users for direct roles, group-derived roles, missing roles, and disabled status.
+Keep credentials and token values out of logs and reports.
+
+In an isolated deployment, verify these results:
+
+1. An eligible user's current token permits Sites management.
+2. A group-derived Lifecycle role permits the same access.
+3. A disabled user cannot manage Sites or obtain a new private browser grant.
+   A user without the required role has the same restriction.
+4. A revoked online token cannot obtain a new grant.
+5. A revoked CLI or MCP offline grant cannot authorize new Sites operations.
+6. An unrelated user cannot obtain a private owner's Site content.
+7. An existing private browser grant expires within five minutes and no later than its authorizing JWT.
+
+Offline grants can remain valid after identity-provider SSO logout.
+Revoke the offline grant to terminate that client's offline access.
+
+Existing Site browser grants remain valid until their own expiry, subject to current Site ownership, access state, and availability.
+Ordinary UI logout does not immediately revoke issued JWTs or Site browser grants.
+A valid authenticated session can obtain another grant after fresh authorization.
+There is no guaranteed fixed cutoff measured from logout.
+
+Private asset requests use the Site grant and current Site state.
+They do not contact Keycloak for each asset.
+If identity checks are unavailable, new protected Sites operations fail closed.
+Existing browser grants can continue until their expiry while Redis and Site state remain available.
+
+If a required identity check fails, keep production unchanged and correct the existing read-only client configuration.
+
 ## Secret handling
 
 Keep credentials in Kubernetes Secrets, an external secret provider, or the
diff --git a/src/pages/docs/operations/security.mdx b/src/pages/docs/operations/security.mdx
index 429ed0f..7f1f1e4 100644
--- a/src/pages/docs/operations/security.mdx
+++ b/src/pages/docs/operations/security.mdx
@@ -3,8 +3,8 @@ title: Security boundaries
 description: Understand Lifecycle authentication, network, Kubernetes, secret, and Agent boundaries before other networks can reach a deployment.
 audience:
   - platform-operator
-lastVerified: "2026-07-24"
-verificationBaseline: "2026-07-24-comprehensive-audit"
+lastVerified: "2026-09-23"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - operator
@@ -49,6 +49,58 @@ and user synchronization.
 | Agents and MCP  | Tool permissions, approvals, external connections, workspace egress, and session review expand the trust boundary. |
 | Backups         | Recovery must include database, key material, and object storage together.                                         |
 
+## Private Sites
+
+Sites management requires authentication even on an authentication-disabled deployment.
+Disabling authentication does not expose private site content.
+Public site content remains readable without signing in.
+
+### Content domain
+
+Use HTTPS for both the Lifecycle UI and Sites content.
+A separate registrable content domain gives stronger isolation from the UI.
+For example, `ui.example.com` and `report.example.net` use separate domains.
+Internal deployments can use sibling hosts by setting `SITES_ALLOW_SHARED_APEX=true` on both web and gateway.
+This opt-in keeps the two hosts on the same browser site and does not provide separate-domain isolation.
+
+### Storage and routing
+
+Keep object storage private and inaccessible through public bucket URLs.
+Route every content request through the authorization-capable gateway.
+Do not cache private content or serve it through an older gateway.
+A private site's content requires its owner and a valid browser session.
+
+None of these grant access on their own:
+
+- A copied URL
+- An administrator role
+- An unrelated API key
+
+### How access grants work
+
+Core verifies the user's JWT, identity status, and Site ownership before issuing browser access.
+The browser receives Site-only access that expires within five minutes and no later than the authorizing JWT.
+Each private content request checks that grant and the current Site owner, access state, and availability.
+Content cookies contain no reusable OAuth access token or refresh token.
+Private asset requests do not contact Keycloak for each file.
+
+Protect Redis access.
+Missing authorization records prevent private access.
+See [Sites configuration](/docs/operations/configuration#sites-configuration) for dependency requirements.
+
+### Browser compatibility
+
+Private content blocks the following:
+
+- Web Workers
+- SharedWorkers
+- New service workers
+- Display inside an iframe
+
+Applications that require these features need a compatible site build.
+An existing service worker from a public version of the same site can remain in a visitor's browser.
+For sensitive content, create a new private site instead of making that public site private.
+
 ## Vulnerability reporting
 
 No private vulnerability-reporting channel is published. Do not post suspected
diff --git a/src/pages/docs/releases/compatibility.mdx b/src/pages/docs/releases/compatibility.mdx
index 282ae1d..6ca197f 100644
--- a/src/pages/docs/releases/compatibility.mdx
+++ b/src/pages/docs/releases/compatibility.mdx
@@ -4,8 +4,8 @@ description: Select compatible Lifecycle components and prepare a safe upgrade o
 audience:
   - platform-operator
   - application-developer
-lastVerified: "2026-07-24"
-verificationBaseline: "2026-07-24-comprehensive-audit"
+lastVerified: "2026-09-23"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - release
diff --git a/src/pages/docs/setup/install-lifecycle.mdx b/src/pages/docs/setup/install-lifecycle.mdx
index 8bcf744..5bfae18 100644
--- a/src/pages/docs/setup/install-lifecycle.mdx
+++ b/src/pages/docs/setup/install-lifecycle.mdx
@@ -4,8 +4,8 @@ description: Select the OpenTofu-managed or standalone Helm installation path. M
 audience:
   - evaluator
   - platform-operator
-lastVerified: "2026-07-24"
-verificationBaseline: "2026-07-24-comprehensive-audit"
+lastVerified: "2026-09-23"
+verificationBaseline: "2026-09-22-sites-access-control-released"
 contentProfile: asd-ste100
 tags:
   - lifecycle