Profiles say what a session may do
Keyboard, mouse, clipboard, file transfer, terminal, hearing the computer's sound, the technician's microphone, restart and shut down, privacy screen, blocking local input, TCP tunnels, printing and recording — each on or off.
Enforced on the remote computer
The profile travels with the session to the Silux agent, which refuses blocked input and commands whatever the viewer sends. The viewer greys the same buttons out and shows what is limited. (Recording happens in the technician's browser, so the viewer switches it off.)
A default for your whole team
Mark a profile as the default and every session your technicians start gets it — for example no file transfer for first-line support.
Passwords per computer
Add one or more unattended passwords to a computer, each with its own profile and a last-used time. Anyone with the password connects by Silux ID without a prompt — from any browser.
Frequently asked questions
Can I allow viewing but block file transfer?
Yes. Create a profile with file transfer off and use it for the password or as your default. The agent refuses file operations for those sessions.
Is it enforced, or just hidden in the app?
Enforced by the agent on the controlled computer; the viewer only mirrors it.
Related features
Connect by ID and code — the person at the computer decides
The person at the computer stays in control
Wake-on-LAN from anywhere — no MAC addresses, no port forwarding
See how this compares on the feature matrix, or find Silux Connect in your country and city.