diff --git a/docs/llm-wiki/08-auth-and-terms-flow.md b/docs/llm-wiki/08-auth-and-terms-flow.md
index 270ae2698..5a6a7d906 100644
--- a/docs/llm-wiki/08-auth-and-terms-flow.md
+++ b/docs/llm-wiki/08-auth-and-terms-flow.md
@@ -40,7 +40,7 @@ Platform UI auth and JupyterHub auth are related but separate:
8. Hub sets its own session cookie (SameSite=Lax, Secure by default). Any valid Keycloak user for the Hub client is currently allowed (`allow_all = True`).
9. Before spawn, Hub injects the Keycloak access token into the notebook pod as `MIP_TOKEN`, refreshing via stored refresh tokens when needed.
10. Running notebooks can refresh `MIP_TOKEN` through Hub `/notebook/hub/api/platform-token` via the mip client transport.
-11. Remote use (account page): shown when `GET /services/auth-config` answers (the backend has a public Keycloak client, `KEYCLOAK_CLI_CLIENT_ID`). "Create access token" runs an authorization-code sign-in with PKCE as that client (`scope=openid offline_access`, redirect back to `/account`, code exchanged by the browser, `cli-token.ts`) and shows the offline refresh token once; nothing stores it. Users paste it into `mip login --token` or `MIP_API_TOKEN`; the mip client renews access with Keycloak itself. The page also explains `mip login` (device flow). JupyterHub is not involved.
+11. Remote use (account page): shown when `GET /services/auth-config` answers (the backend has a public Keycloak client, `KEYCLOAK_CLI_CLIENT_ID`). "Create access token" runs an authorization-code sign-in with PKCE as that client (`scope=openid offline_access`, `prompt=login` so Keycloak re-asks for the password even with a live SSO session (first present on master after commit 8b17318, 2026-11-06 — use that build or newer as the minimum UI version in the M6 gate), redirect back to `/account`, code exchanged by the browser, `cli-token.ts`) and shows the offline refresh token once; nothing stores it. Users paste it into `mip login --token` or `MIP_API_TOKEN`; the mip client renews access with Keycloak itself. The page also explains `mip login` (device flow). JupyterHub is not involved.
Key files: `src/app/pages/notebook/hub-session.ts`, `hub-http.ts`, `jupyterhub-api.ts`, `nginx.conf.template`.
diff --git a/src/app/pages/account-page/account-page.component.html b/src/app/pages/account-page/account-page.component.html
index b20a6a364..48317ede1 100644
--- a/src/app/pages/account-page/account-page.component.html
+++ b/src/app/pages/account-page/account-page.component.html
@@ -64,6 +64,13 @@
Use MIP from your own computer
No browser on that machine
+
+ This token works like your password for up to 180 days. Keep it only in
+ mip login --token; never put it in notebooks, .env files,
+ repositories or chat. Lost it or your computer?
+ See and remove computers signed in to MIP.
+
{{ tokenCopyStatus() }}
- Treat it like a password: it gives your full MIP data access for up to 6 months, until
- it goes unused for 30 days, or until you run mip logout.
+ It lasts up to 180 days, or until it is unused for 30 days, or until you run
+ mip logout. Lost it or your computer?
+ See and remove computers signed in to MIP.