Sync the self-hosting stack
This commit is contained in:
@@ -9,6 +9,39 @@ 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
|
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
|
||||||
cannot be published without its entry.
|
cannot be published without its entry.
|
||||||
|
|
||||||
|
## 2026-10-09 — Quick Assist becomes an app, in the name of the organization you work for `api 0.134.0` `web 0.164.0`
|
||||||
|
|
||||||
|
**Jarvis now has apps.** The top of the sidebar switches between the **RMM**, which works on one
|
||||||
|
customer at a time as before, and **Quick Assist**, which has its own navigation: your sessions, and
|
||||||
|
for an organization's owners and administrators, the **Team** page listing every call made in its
|
||||||
|
name this week. The command palette lists the apps too, and its **New Quick Assist session** starts a
|
||||||
|
call from any page.
|
||||||
|
|
||||||
|
**A Quick Assist call is made in the name of the organization you work for**, no longer the customer
|
||||||
|
selected in the RMM's top bar. Quick Assist's top bar shows that organization instead of the customer
|
||||||
|
picker. Your sessions stay listed whichever customer the RMM is on.
|
||||||
|
|
||||||
|
- **Your own staff work for the service provider.** Choose which organization is the provider's own
|
||||||
|
in **Settings, Platform, Provider**, or on the Quick Assist page, which asks a super-admin for it
|
||||||
|
while none is chosen. The people your staff help see its name and logo, the calls are filed in its
|
||||||
|
audit trail, and it counts towards your licence like any other organization.
|
||||||
|
- **A customer's own people work for their customer.** A customer's administrator who helps somebody
|
||||||
|
is shown as one of that customer's people, and the call is filed in that customer's trail.
|
||||||
|
- **Super-admins can change who works for whom** with **Works for…** in the user directory, choosing
|
||||||
|
the provider or a customer the account is a member of.
|
||||||
|
|
||||||
|
On upgrade, every account with no platform role and exactly one organization is attached to that
|
||||||
|
organization. Everybody else works for the provider.
|
||||||
|
|
||||||
|
**What you need to do.** Until a super-admin chooses the provider's organization, only super-admins can
|
||||||
|
use Quick Assist, and they are asked to choose it first. After that, your staff need a role in the
|
||||||
|
provider's organization that includes remote desktop (Operator or above); add them as members there.
|
||||||
|
A role in a customer's organization no longer lets somebody start a call in the provider's name.
|
||||||
|
|
||||||
|
Update the API and the web image together. No agent update is required. The API applies an additive
|
||||||
|
schema update (the provider's organization on the instance settings, and each account's home
|
||||||
|
organization), and a one-time data backfill attaches accounts to their organization.
|
||||||
|
|
||||||
## 2026-10-09 — Find the codes of your Quick Assist sessions again `api 0.133.0` `web 0.163.0`
|
## 2026-10-09 — Find the codes of your Quick Assist sessions again `api 0.133.0` `web 0.163.0`
|
||||||
|
|
||||||
Your Quick Assist page now shows the code of every session, so a reload or a trip to another page no
|
Your Quick Assist page now shows the code of every session, so a reload or a trip to another page no
|
||||||
|
|||||||
Reference in New Issue
Block a user