Profile can show GDP Desktop installations attached to your account. Renaming changes the human label; permanent revoke is a security action that invalidates that device's execution identity and saved selections and is deliberately blocked while a live mutation is in flight.
Know what the device list represents
The GDP Desktop devices area represents account-linked Desktop installations rather than arbitrary computers discovered on your network.
A device card can show its display name, connection state, client version, last-seen time, and bounded workspace labels or branches.
Online, offline, or suspended describes current device state; it is separate from whether the registration has been permanently revoked.
The Profile device surface does not expose raw execution credentials or secret token internals.
Choose rename or permanent revoke deliberately
Rename changes the account-facing display name of an active device. It does not create a new installation or widen that device's authority.
Revoke is intentionally different from going offline. A successful permanent revoke marks the device revoked, invalidates its execution credentials and legacy token binding, clears saved conversation selections for that node, and requires a new trusted-device flow before it can be connected again.
Do not permanently revoke a device merely because it is temporarily offline. Use connection troubleshooting first unless you actually want to invalidate the installation.
Revoke safely around active work
Use the explicit revoke confirmation only for the exact device you intend to invalidate.
If GDP reports that the device action failed while material work is still active, first reconcile or let that in-flight mutation finish.
Refresh the device state after the operation has settled, then retry the explicit revoke if permanent invalidation is still intended.
After a successful revoke, reconnect that installation only through a new trusted-device flow rather than trying to reuse the invalidated identity.
The backend fails closed while a live runtime mutation lease exists: the revoke is not partially performed. Account ownership checks also prevent another account from revoking or probing that device through this path.
