Sync the self-hosting stack

This commit is contained in:
2026-10-12 23:14:53 +02:00
parent ef4c5597e7
commit 5f1fed1a45
+21
View File
@@ -9,6 +9,27 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
cannot be published without its entry.
## 2026-10-12 — An organization's policies on one page `api 0.142.0` `web 0.171.0`
**Policies, then sessions.** In an organization's administration, agent updates, terminal sessions
and remote desktop were three sections of their own. The three policies are now one page,
**Policies** — agent updates, terminal recording and remote desktop, one under the other — and
**Terminal sessions** holds the session log alone.
- **Remote desktop says whether the instance allows it at all**: a badge beside the organization's
own settings reads _On for the instance_ or _Off for the instance_, and leads to the instance's
setting for whoever may change it. Agent updates already showed the instance default they
inherit; terminal recording has no instance-wide setting.
- **The session log shows the recording policy in force** — _Recorded · 90 days_, or _Recording is
off_ — and leads to it; the policy leads back to the log.
- **In Settings, the Agents tab is called Machines**, and Provider is called **Quick Assist**.
- **Switching organization in the Admin Center starts the page afresh**: an edit you had not saved
is dropped rather than carried over to the next organization.
- **Old links keep working**: the former agent updates, terminal and remote desktop addresses land
on their section.
Update the API and web images. No agent update is required, and nothing in the schema changes.
## 2026-10-12 — An organization is administered in the Admin Center `web 0.170.0`
**One place to administer a customer.** Members, teams, access, agent updates, terminal sessions and