Managed devices: 0
New devices require approval. Verify the complete fingerprint in the local application's About panel before approving. Online means the authenticated reverse tunnel is connected and its local Web endpoint is ready. Native profile passwords and local MCP keys are not uploaded to inventory. Web administrator credentials are configured separately in Web password settings.
From another PC, sign in here and choose Open device for the approved Online installation. The device address alone does not grant access. A compatible Windows machine host offers its Windows workspace chooser inside the device page; each selected profile keeps its own password and data. This is access to Anubis on that machine, not Windows screen sharing. The standalone Web demo is a separate installation.
Copy device URL copies only the nonsecret HTTPS address, not authorization. A different browser or incognito needs its own Web sign-in. Open device does not bypass passwords. Web administrator access uses the separate per-device password configured here; User access uses a unique password owned by a protected local file on that device, not a universal default. User access stays in the separate SYSTEM Web workspace, not the ordinary Desktop user's profile. Additional Windows profiles still require explicit policy authorization and their existing app-profile password from the profile owner. This panel cannot retrieve, set or reset Windows or native app-profile passwords. No SSH/RDP/VNC address, port or password is advertised by this inventory.
Windows accounts, SIDs, sessions and workspace availability are not advertised in this inventory. On compatible Windows machine hosts, Open device starts with the separate SYSTEM profile; explicitly select an available logged-on user inside that page for that user's data. MCP stays in its administrative workspace. Neither an online tunnel nor a temporary MCP grant proves a successful application login or protocol connection.
| Device | Application / platform | Enrollment | Presence | Connection | Actions |
|---|
No managed devices enrolled yet.
An installation ID identifies an application profile, not necessarily a unique PC. A startup report is not a live presence signal. Recent reports do not prove that a machine is online or remotely accessible. Use Managed devices above for authenticated access.
| Installation ID | Application / version | Platform | Last report | Remote access | History |
|---|
No installations have reported to this server.
Treat this temporary token as a secret. It expires after at most one hour and grants access only to this device's MCP endpoint, not its browser UI. The local authenticated MCP widget must be running; its own key never leaves the device.
Grant issued does not mean MCP is running or its profile is unlocked. This panel does not probe the device or execute tools. Closing this panel discards the displayed token; it does not revoke it. Browser authorization and unused MCP grants expire naturally; device-wide Revoke is a separate action.
These are Anubis Web roles, not Windows accounts. This password is separate from the management API token and any native profile password. Setting it does not provision a Windows user or unlock DPAPI data. The device must support protected role issuance before Administrator sign-in can succeed.
The User password is generated uniquely on the device and owned by its protected local file. This panel cannot read or change it; local-file changes require the compatible local verifier. There is no shared default password.
Saving replaces only this device's Web administrator credential and invalidates its administrator browser sessions. User sessions, enrollment approval and MCP grants are unchanged. Reveal is explicit, available only to the authenticated management administrator, and never saved in browser storage.
Up to 50 latest reports for the selected installation.