You have answered this ticket four times.
The fifth one is a link.
Spawnit Capture records the fix while you are already performing it — the clicks you make, a screenshot at each step, and the name of the control you touched wherever the application publishes one — and compiles it into numbered steps with one link at the end. Whoever opens that link needs no account, which is worth more on a service desk than anywhere else: the people asking are usually the people with no seat in your tools.
Windows 64-bit · Free plan · viewers need no account
The article takes longer to write than the fix takes to do.
So it does not get written. The fix gets performed again next week, from memory, on a call — and the queue never learns anything.
A locked account in Active Directory Users and Computers. A printer that needs the right driver adding from Printers & scanners. A drive that stopped mapping. A stale saved credential in Credential Manager. An Outlook profile that has to be rebuilt. These are the tickets, and not one of them happens in a browser tab.
Spawnit records the display you pick, so the console is recordable whether or not it is a web app. What varies from window to window is not whether it is recorded — it always is — but how much of that window Windows will describe, which is the application’s decision rather than the recorder’s.
- Start the recorder, do the fix you were doing anyway, stop.
- A screenshot at every step — nothing to crop and paste into the ticket.
- Clicks and key presses logged as you make them, not typed up afterwards.
- Silent by design: no audio, no microphone, no webcam. Nobody has to narrate.
- One link at the end. The person who asked opens it with no account.
One ticket: reset a locked-out account password.
Recorded once, while it was being done for somebody. The step the requester reads sits on top; the raw line Spawnit logged sits underneath — including the step where Windows said that field was a password, and the step where the console published no name at all.
- 1
Search for the locked-out account
key press → edit "Name"
edit · Find users
- 2
Run the search
click → button "Search"
button · Find users
- 3
Open the account from the results list
click → (516, 284)
no accessible name — coordinates and screenshot only
- 4
Choose Reset password
click → menu item "Reset password…"
menu item · account properties
- 5
Type the new passwordredacted
key press → [redacted] in edit "New password"
password field · rectangle painted black in the step screenshot
- 6
Clear the lockout
click → check box "Unlock the account"
check box · reset password dialog
- 7
Apply and close
click → button "OK"
button · reset password dialog
Windows marks that box as a password field, so the key label was stored as [redacted] and the field’s rectangle was painted solid black in the screenshot before that screenshot was used for anything. Black, not blur: deterministic, and unmistakable to whoever reviews the guide.
Best-effort is the honest word for it: the scan covers the foreground window, it is time-bounded, and it is skipped entirely on a machine auto-detected as low-memory. Continuous video is not redacted at all, which is one reason it ships off. Those limits are spelled out below rather than left for you to find.
Step 3 is the other honest one. That results row publishes no accessible name, so the log line carries coordinates rather than a label — the step still shows the screen, and Spawnit did not invent a name for it. That is the application’s decision, not the recorder’s, and it is why nothing here is a support matrix.
Nothing extra to do, and nothing to install to read it.
The reason a knowledge base decays is that writing it is a second job. This is the same job, recorded.
The technician does nothing extra
Start the recorder, perform the fix, stop. Clicks, scrolls and key presses are captured system-wide, and a screenshot is taken at each step from the same live capture stream the video uses — so nothing is cropped, pasted or written up afterwards. There is no narration to record and no audio path to record it with. Continuous video is a setting, and it ships switched off.
The requester gets numbered steps
Each step carries its screenshot, and the name of the control wherever the application published one — the difference between “click (612, 431)” and “click button Search”. Where nothing is published, the step still shows the screen and the log line carries coordinates instead of a label. It opens from a link, in a browser, with no account.
Before rolling it out to a team, run the uia-audit command against the three consoles your queue actually lives in. It reports, in plain English, what share of a window Spawnit can describe on your machine. Spawnit publishes no coverage figure for anyone’s software, because no such measurement exists — the number you plan around should come off your own screen.
The person who needs the answer usually has no seat in the tool you would write it in. A guide opens from its link, in a browser, with no account: the contractor, the shop-floor supervisor, the starter on their first morning, and — the case that settles it — the user who is locked out and therefore cannot sign in to read the article about being locked out. One link, and nobody has to be provisioned to read it.
What an IT reviewer will want in writing.
Answered from what the capture client does today. Where a protection is partial, it says so here rather than in your pilot.
Your recorder is going to capture our admin credentials.
Two mechanisms, and it matters which one is doing the work. Elevation prompts and the Windows sign-in screen run on the secure desktop, which no low-level input hook can reach — keystrokes typed there are not something Spawnit records at all. Inside an ordinary window, a field Windows marks as a password has its rectangle painted solid black in the step screenshot before that screenshot is used for anything, and the key label is stored as [redacted]. Black rather than blur is deliberate: deterministic, and unmistakable to a reviewer. That second mechanism is best-effort — the scan covers the foreground window, it is time-bounded, and it is skipped entirely on a machine auto-detected as low-memory (under 4 GB of RAM, or two or fewer cores). Continuous video is never redacted at all, and it ships off by default.
A technician sees customer data all day. What actually lands on disk?
Recordings are written to that technician's own Windows profile, under %USERPROFILE%\Videos\Spawnit, and nothing uploads unless they sign in and enable sync. By default, sessions are purged once their newest file is 14 days old, with two exceptions worth knowing: a session still being written is never purged, and if they have enabled sync, a session that has not uploaded yet is kept, because the local copy is the only copy. No audio, microphone or webcam capture exists anywhere in the app, and there is no telemetry SDK in the client. The part to say out loud: the visible label of each control clicked and the title of each window are stored as plain text in the local event log, and no automatic scan for personal data runs over them. What protects a screen here is the always-on rules, not a classifier.
Is any of it encrypted at rest?
The event log can be; by default it is not. The sealing is built properly — streaming zstd compression, then per-chunk AES-256-GCM with a per-file HKDF-SHA256 subkey, framed so a crash costs at most the last partial chunk, and the 256-bit key held in Windows Credential Manager rather than on disk. Two limits decide whether that is relevant to you: it is switched on from the command line rather than the desktop app, and it covers the event log only — step screenshots and the video file are not encrypted by it in any configuration. Separately: the client holds no cloud storage credentials of its own. When sync is on it asks the portal for a short-lived signed URL per artifact and streams to that.
How does a technician stop it recording the wrong screen?
With the tray icon, which is the control the desktop app actually has: a red dot and a Recording tooltip whenever capture is live, grey when it is not, and Pause and Resume in its menu. Two rules need no configuration at all — a window whose title marks it as private browsing is dropped whole, and any observation Spawnit cannot attribute to an application is dropped rather than kept. Excluding a named application or a window title is supported, but only from the command line: the desktop app ships both lists empty and has no setting to fill them. And one display is recorded per session, which makes a second monitor the place to put whatever is not being recorded.
Is this monitoring software?
It is built to be the opposite, and the design is checkable rather than a promise. A system-tray indicator is shown the entire time the app runs; the source calls it the deliberate anti-stalkerware signal. The installer presents a consent page itemizing what is captured — the screen, key presses and clicks, the on-screen text of UI elements — and where it is stored, and the installation aborts if it is not accepted. It installs per user, never asks for elevation, and its logon task runs at least privilege with below-normal priority. The input hook does no work in its callback: it hands events off and drops them rather than stall system input, so capture is deliberately lossy under load rather than deliberately complete. Auto-start is real and disclosed rather than hidden: the installer registers a task that launches the app shortly after sign-in.
Documenting something else?
Standardise the process on a recording, not a rewrite
A process drifts because the document describing it is always one rewrite behind reality. Record one person's real pass at the task — workarounds included — and the take you choose becomes the standard. When it changes, re-record and send the new link.
OperationsPeople & team leadsOnboard from real work, not last year's slide deck
Every step shows the real screen, and names the control wherever the application publishes one, so a new hire follows the job as it is done today. Re-record when it changes and the guide is current again.
HR, onboarding & trainingIT & operationsDocument the Windows software a browser recorder cannot see
Spawnit records at the Windows desktop, not inside a page — so ERP fat clients, terminal sessions, RDP windows and the tool nobody will rewrite are all recordable. Specific about where UI Automation stops: a custom-drawn terminal screen, like an RDP window, is captured as pixels and coordinates rather than named controls.
ERP & legacy WindowsUse casesThe other four things teams record first
The postponed SOP, new-hire onboarding, the vacation handoff and the legacy Windows tool nobody will rewrite — one link each.
Browse use casesPlansWhat this costs a service desk
Capture, per-step screenshots and share links are on every plan — up to 10 guides on the free plan, unlimited on Pro. Pro and Team pricing is being finalized.
See pricingPick the ticket you answer most
Not the demo task — the one that comes back every week. Request access and tell us which workflows you need to capture, so the next time that ticket lands you record the fix instead of performing it again.