Manager Help

English

简体中文

English

简体中文

Appearance

Back to Console ↗

Console Overview ​

The Manager console is the enterprise management UI for LCXL Remote Desk, served at /console. On top of the open-source host / signaling capabilities, it adds organizations, device authorization, fleet operations, AI governance and system settings.

Three Views: Personal / Organization / Platform Admin ​

To avoid cramming every feature into one screen, the console is organized into three independent views; the current view is determined by the URL, so a refresh or a deep link lands you in the matching view. The personal view is a product-style interface (top bar + home) for individual users; the organization and platform-admin views keep the console sidebar. Both interfaces offer a view switcher (in the top bar for personal, in the sidebar for org / admin) to move between the views you have access to.

  • Personal view — the default after login: the home device grid, connecting, My Devices, and account settings (including email change and self-service account deletion).
  • Organization view — team collaboration and fleet operations: members, org AI, user/device groups, batch diagnosis / execution.
  • Platform-admin view — visible only to platform admins: dashboard, AI governance, access control and system settings.

New here? Start with the Setup Guide to bring your first computer online.

Switching views does not change existing URLs: personal, org and platform-admin pages keep their original paths (e.g. the personal home /home, /org/members, /admin/users). Non-admin accounts do not see the "Platform Admin" option; visiting an admin path directly redirects back to the personal home. A personal user who has not joined any organization also does not see the "Organization" option or the view switcher — the console is simply a single personal view. After joining an org, the personal scope is still the product-style home; switching to the org / admin scope enters the console sidebar.

Devices always belong to an individual (bound to the device owner at registration). An organization does not "own" devices; it is granted access by the device owner — so the personal home shows both your own devices and the org-authorized ones. See Device Access Authorization.

Connect by code from the home connect box, which takes both a device code and a one-time support code (the server detects which). Connecting to a device you own or are granted by an organization gives full control; a one-time support code is for helping a stranger's machine — their local user generates it and reads it to you, you redeem it to connect, and that session is held capability-scoped by their host (with no change to device ownership). See Temporary Support.

How the Host Identifies a Remote Actor ​

When a device enables its local remote-access indicator, manager supplies an actor summary derived from server-side authentication. A normal signed-in connection shows the authenticated account name; a support code or other temporary grant is labelled as temporary access. A controller-supplied display name is never trusted for this security display. If no trustworthy name can be resolved, the host uses a generic remote-user label. Organization authorization proves that the account may access the device, but manager does not guess or claim an organization name when the source is not unique. The indicator preference belongs to the local host and cannot be disabled remotely by manager.

Authentication ​

Browser access to the console and signaling uses Actix-Session cookie auth (no token parameter). Hosts, signaling and the manager use their own distinct token mechanisms — see the open-source docs' signaling-auth section.

Next ​