Revoke or Sign Out a Desktop Session

End a desktop session and distinguish account sign-out from license or membership removal.

Written By 4ALL.LIVE

Last updated 12 days ago

End a desktop session and distinguish account sign-out from license or membership removal.

Best for: Desktop users, administrators, and support staff.

Before you start

Local sign-out is account-level; releasing a license or removing membership requires separate authorized actions.

  • Stop active production safely.
  • Decide whether the need is sign-out, session revoke, license transfer, membership removal, or all.
  • Have an authorized admin for license/access changes.

Step by step

  1. Stop live work. End bridges, streams, and sessions by runbook.
  2. Use the app Sign Out command. Revoke through the supported flow.
  3. Confirm local cleanup. The app returns to unauthenticated state and hides organization data.
  4. Reopen the app. Verify it does not restore the revoked session.
  5. Release license separately. An authorized license admin transfers/releases Bridge or Encoder devices when retiring hardware.
  6. Remove organization access separately. After handoff, remove team/member access if the person is leaving.
  7. Document privileged decommissioning. Record machine, product, license, account, time, and approver.

What success looks like: The app has no authenticated session, and intended license/membership cleanup is completed separately.

Check your setup

  • Reopening requires authorization.
  • No organization/event data remains visible.
  • License inventory reflects approved changes.
  • Former access is no longer usable after removal.

Troubleshooting

Session returns

Check connectivity during revoke, sign out again, update the app, and use approved local credential cleanup.

License remains assigned

Sign-out does not release licenses; use Billing → Desktop Licenses.

Output continues

Stop the live process first and verify downstream; sign-out is not a stop command.

Security and operational notes

  • Decommission before hardware transfer.
  • Preserve logs before local cleanup.
  • License/member removal requires authorization and audit.