Delete an access completely

What it is for

When the work with a customer ends, their data must go. "Delete completely" removes an access together with everything that belongs to it: devices with certificates and inventory, sessions, script and workflow runs, start buttons, seats, tickets with attachments, feedback, recordings and its rows in the audit log. The deletion itself remains provable in the log.

What you need

• Your own relay from version 20261011.9.
• A console account as system administrator of the relay. Administrators of an access, supervisors and technicians do not see the menu item.
• The exact ID of the access (upper and lower case count).

How to do it

1. In the console open Fleet › Tenants. The console calls the access "tenant".
2. In the access's row open the ⋮ menu → Delete completely …. (Also in the device tree by right-clicking the access.)
3. The dialog Delete access completely? lists what will disappear. Read it, then Continue ….
4. In the dialog Type the ID to confirm enter the ID exactly into ID of the access.
5. Delete for good.

How you know it worked

• The console reports "Access “…” deleted completely: … devices, … data rows, … audit log rows."
• The access is no longer in the list.
• The audit log contains a closing entry for the deletion with ID, count and period, and Verify chain still reports the chain as intact (G17).

What the other side sees

Devices of the access that are connected right now are disconnected at once. Running sessions end. A device on which BrowserDesk is still installed keeps trying to sign in and is silently rejected.

Good to know

• Final. There is no recycle bin. The only way back is a backup of the relay.
• What remains: orders, licences, payments and invoices (statutory retention); the ID itself is never assigned again; in the audit log the numbers, checksums and counts of the deleted sections together with the closing entry — but no contents.
• Backups and server logs still contain the access until they rotate out after their own period (backups: the last 14, logs: 14 days).
• "Delete" is not "Delete completely": the menu item Delete only removes the access with its members and some settings — devices, sessions, tickets and log stay. For deletion at the end of a contract always use Delete completely …. If an access was previously only deleted, it is no longer in the list; there is no dedicated way in the console to clean it up yet — write to info@browserdesk.de.
• Console accounts bound only to this access are deleted; accounts with several accesses only lose the binding. API tokens only for this access disappear as well.
• The access "default" cannot be deleted completely.
• Clean up the devices: uninstall BrowserDesk on the devices, otherwise they keep knocking (C8).
• Deadlines — the data processing agreement promises deletion within 30 days after the end of the contract. The console does not delete automatically after a deadline; you start the deletion by hand.
• Cloud: for accesses on browserdesk.de there is no dedicated way for this yet — write to info@browserdesk.de. A full export of the data before deletion does not exist yet either.
• Deletion has not yet been measured on a real relay with connected devices.

If it does not work