Email and password, then a six-digit code from your authenticator. Tick trust this device and it stops asking on this browser for thirty days — on this browser only, and you can revoke it later from Settings without touching the others.
If somebody invited you, you did not start here: you opened their link, which named one team and offered you an account with a password of your own choosing.
A set is not a TV. It is a TV plus the camera pointed at it, and (optionally) the smart plug on its socket — because everything Screenwhere does needs both halves: the camera to see the screen and the box to press the buttons. Add one under Zařízení → Add: catalogue fields, the LAN addresses, and whether this set may be recorded at all.
Nothing reaches into your network from outside. The box on the TV's LAN dials out to the relay and keeps that connection; the cloud never opens anything inwards.
Open the set. You get the live camera view and a remote deck beside it. Only one person holds a set at a time — presence shows who, and the hand-over is explicit, so two people cannot quietly fight over the same screen. Everything meaningful you press is written to the audit log.
Record while you work. The recording keeps the video and the key track — every button you pressed, timed against the picture — so review is not guesswork: scrub the video and the presses move with it. Trim, replay onto a live TV, export. Mark one ★ and the storage sweep will leave it alone.
A scenario is that key track turned into something repeatable, and it is not tied to the TV it was recorded on. Write or record one in the editor, keep it in the library under folders and tags, and run it against any set in the project.
Hlídání runs scenarios on a schedule and tells you when a screen stops looking like itself. Běhy is the history: every execution and its verdict, kept apart from the watch settings on purpose — a run history is not a configuration.
Scenarios are versioned, and more than one line of work can exist at a time. Vydání is where those versions live; promotion is a deliberate act, because production should be somewhere you get to, not wherever somebody last saved.
Four roles. reader may look and nothing else; user works; admin manages a team; super runs the installation. Teams decide who sees which TVs, so a person's reach is the team's reach, not a global switch.
Invite by e-mail rather than creating accounts for people. The link names exactly one team; a bad or spent link gets one neutral refusal, so it cannot be used to discover what teams exist.
Projects keep one client's work genuinely apart — scenarios, recordings, builds and watches belong to a project; televisions and people do not, because a screen in the corner of the office is not a client's property. Den is the screen you can put in front of that client: one day of runs, what was found, and nothing about how it is wired.
Stav zařízení answers “is it even online” first, with last-seen per set. Audit answers “who did that”, with security events called out from ordinary ones. Instalace — for whoever runs the installation — holds the quotas, the disk reserve and the operations alerts.
Everything above has a machine-facing side: an MCP server that lets an AI agent list sets, launch apps, send keys and text, run a scenario or a whole suite, and read the results back. Same permissions as a person — an agent is not a way around the roles. See MCP.
Stuck on how any of it is wired? That is architecture. Getting our app onto a Samsung TV in the first place is cert-gen.