| Severity | Customer / PC | What | Since | Last seen | Count | Notified | Acknowledged |
|---|
| Customer | Mode / address | Licence key | Branches | PC limit | Expires | Backup | Status |
|---|
| Key | Customer | PCs | Expires | Status | Cloud backup |
|---|
A copy of a customer's data is opened only with the customer's consent, on the vendor's Mac, with a ticket issued from the customer's page (Support access button). Every ticket, fetch and revocation is recorded here and in the admin actions, and the customer's own activity log records the access.
| Ticket | Customer | Status | Who / consent / reason | Issued | Expires | Fetched | Customer notified |
|---|
| Time | Level | Customer / PC | Event | Message | Ref |
|---|
| Time | Channel | Kind | Result | Subject |
|---|
| Time | Who | Action | Licence | Target | Detail |
|---|
How a release gets here: tag vX.Y.Z → GitHub builds and signs the installer → publish it to the update feed (deploy/hosted/publish-update.sh) → record it here. Each installation learns its channel, hold and required version at its next check-in or report (within about an hour), downloads in the background and installs overnight (02:00) after a backup.
| Version | Channel | Status | Required | Published | PCs on it | Notes | Files |
|---|
Test group: gets releases on the test channel first. Hold: never offered a version above the one chosen (a hold also wins over a required release above it).
| Customer | Running | Channel | Hold at |
|---|