Settings.

Each organisation gets a support address. Forward your support mailbox to it and every email becomes a ticket.

Switch it on, set business hours and targets per priority, categories, canned replies.

A named seat. Email as username sends an invitation; they set their own password.

The role menu on Settings › users. Company admin manages users and the install link. Operator only works the machines.

A new seven-day link. The previous link stops working.

Someone forgot the password. You issue a new one from their row. It is shown once, and they must change it.

Settings › account. The browser you are using stays signed in. Your other browsers are signed out.

Sessions lists each signed-in browser. Revoke signs that one out. The others stay.

Sign out on the account card or in the header. This browser only. Other browsers stay signed in.

A disabled person cannot sign in. Their sessions drop. The seat stays in the table so you can enable them again.

An API key is for scripts. It is not the password they type to sign in. A new key is shown once.

Claude, an assistant or your own automation can read the fleet and work alerts through BE Hub's MCP address, with a user's API key.

Company admins can require 2FA on one account. The QR stays on their own screen.

Clears the authenticator on someone else's account. They enrol again at the next sign-in. Their sessions are signed out.

Settings › display. Every clock on this console follows it, including BE AI's answers. This browser only.

How timestamps look, change password, authenticator, sign this browser out.