Devices
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
Devices (/admin/devices) lists every client that has registered with this server, for every user. It is the operator’s view of the pairing model described in End-to-end encryption: a device holds key material, so removing one is a security action, not housekeeping.
Devices belonging to soft-deleted users are hidden.
Status
Section titled “Status”| Status | Means |
|---|---|
| Pending | Registered but not yet approved by an existing device. It cannot decrypt anything, and it disappears on its own if it is not approved in time |
| Active | Approved, holding a wrapped copy of the user’s master key |
| Revoked | Cut off — the sessions tied to it signed out, its wrapped key and pairing sessions removed |
The cards along the top count each status plus the number of distinct users with at least one device.
A user can have at most five devices waiting for approval; a sixth registration is refused until one of them is approved, revoked, deleted or expired. A Pending device that has not registered again within PendingDevices:RetentionDays (7 days by default, at most 30; see the configuration reference) is deleted together with its wrapped key at the next sweep, which runs at startup and every six hours.
Columns
Section titled “Columns”| Column | Reads |
|---|---|
| User | Owner’s email |
| Device | Name the client reported at registration |
| Device ID | The client-generated id used in pairing and in sync cursors |
| OS / App | Versions the client reports when it registers and when it renews its sign-in — useful for spotting a client that never updated. The server accepts only a version number for App, but neither value is verified |
| Created | When the device registered |
| Activated | When an existing device approved it; blank while pending |
| Last Seen | Last request from this device |
Search matches the user, the device name, or the device id. The Refresh control above the grid re-reads both this table and the sync cursors below it, and can be put on a 30-second or 5-minute interval.
Revoke vs delete
Section titled “Revoke vs delete”Revoke marks the device revoked, stamps the time, and ends its access. The sessions tied to the device are deleted, so it cannot renew its sign-in. Sync requests that name it are refused straight away, and so are its attempts to approve or revoke devices, store a wrapped key, or use the recovery copy. It can still read the device list, which is how the desktop app notices that it has been revoked. Anything else it is signed in for stops at the latest when its access token expires, within 15 minutes. Its wrapped master key and any pairing sessions are removed, so it can no longer fetch the key or finish pairing. The row stays, so the history of the machine is still visible. This is the action for a lost or stolen laptop.
A session is tied to a device once the device has registered or fetched its key with it, which the desktop app does right after it signs in. A session the device has used for neither is not tied to it, and revoking leaves it signed in. To be sure a lost machine is signed out, also use Revoke all sessions on the user’s account; the user then signs in again on their other devices.
Revoking does not rotate the user’s master key. Data the device already holds, and the master key stored on it, stay readable on that machine; revoking only stops it from getting more.
Delete deletes the sessions tied to the device, its wrapped key and its pairing sessions as revoke does, then removes the device row and its sync cursor. Nothing is left behind — including the record that the device ever existed — so nothing refuses its sync or its other requests straight away either: an access token it already holds keeps working until it expires, within 15 minutes.
Both ask for confirmation and are written to the server log with the acting administrator’s address.
Sync cursors
Section titled “Sync cursors”Below the devices, one row per (user, device) that has pushed a change: the device id and the timestamp of its last push. The table only appears once at least one cursor exists.
A cursor is server-side bookkeeping — the resume point for incremental pulls. Delete discards it; the device’s next pull simply starts from the beginning and re-reads everything it is entitled to. Nothing the user owns is touched. It is the safe first thing to try when one device is stuck on stale data.
Deleting a device takes its cursor with it, because the cursor has no foreign key to the device and would otherwise survive as a resume point for a machine that no longer exists. A revoked device’s cursor goes at the next sweep (every six hours), and any cursor 180 days after its last push (SyncCursors:RetentionDays).