Local-first workflow documentation for privacy-sensitive teams

Workflow documentation often touches internal tools, customer records and operational details. For privacy-sensitive teams, the safest default is local-first capture and editing.

Documentation starts with screenshots

The useful parts of a process guide are also the risky parts: real screens, real labels, real account pages and sometimes real data. Sending that material to a service by default creates a review problem before the guide is even finished.

Local-first reduces the blast radius

When capture and editing happen on the Mac, the draft can be reviewed before anything is shared. Authors can remove unnecessary steps, redact sensitive areas and decide whether the result is appropriate for export.

AI should be optional and explicit

AI can improve titles, descriptions and structure, but it should not quietly change the privacy boundary. Teams should know which endpoint is used, what content is sent and whether images are included.

StepShot's optional cloud planning uses the user's own OpenAI-compatible endpoint and API key. Text is the default; visual samples require a separate opt-in and are locally sanitized first.

Export formats matter too

A self-contained HTML guide should not load remote assets when opened. A PDF should carry the final approved screenshots. Markdown should export with predictable image files. Privacy is not only about capture; it continues through delivery.