Document systems, access, and troubleshooting once, and stop answering the same ticket every week. Built to be safe to run inside an admin console.
Redaction is decided from DOM signals only, with no model call, so it behaves identically every run. A field is treated as secret when any of these hold:
type="password" on the input.autocomplete of one-time-code, cc-number, or cc-csc.This detects form fields, not text. A token rendered on the page after you generate it is not something the DOM marks sensitive, so blur it yourself in the editor. We would rather state the limit than imply a guarantee.
Capture requests access to all sites, because we cannot enumerate your internal tools in advance. What it does with that access is narrow:
Full per-permission breakdown on the security page, which also lists what we have not built.
Grant view on the specific runbook rather than making someone an editor of the workspace, and set an expiry when the access is temporary. Grants only ever widen access, so one cannot be used to lock an owner out of their own content.
SAML single sign-on, SCIM provisioning, a workspace audit log, customer-managed keys and region pinning do not exist yet. Where each sits is on the roadmap. If one is a hard requirement, say which, because that ordering is driven by who actually asks.
Password, one-time-code and card fields are blurred from DOM signals before the screenshot is stored, and you can pause capture before stepping outside the flow. Secrets rendered as plain page text are not auto-detected, so blur those manually in the editor.
No. Every listener is gated on an active capture session. Until you press record, no step is created, no screenshot is taken, and nothing leaves the browser.