Recording
Passwords stay out of docs
Autodocs keeps passwords out of guides and visible steps, and a replay that reaches a sign-in asks you for the password or one-time code instead of reading it from the doc.
THE PROBLEM
Screen recorders capture everything, passwords included
A how-to that shows a password, or a script with a password in it, is a security incident waiting to happen. Autodocs is built so the guide and the steps people see never carry a typed secret.
Passwords and typed secrets never appear in the steps people see or in the guide, and a replay asks for a password or one-time code at the moment it needs one.
How it works
How does passwords stay out of docs work in Autodocs?
- 1
Sign in while you record, as normal
Type your email and password into the site’s own fields.
- 2
The steps list hides it
The recording’s visible steps and the saved workflow’s summary never show a typed secret.
- 3
The guide leaves it out
The model writing the guide is told never to include a password or other secret, so the step reads “Type your password in Password.”
- 4
A replay asks you when it needs one
When a run reaches a password or one-time code field, it can pause and ask you. What you type goes straight into the field; it is never stored and never logged.
Options and settings
Every option, in one table
| Where | What happens to typed secrets |
|---|---|
| Steps shown while recording | Never shown. |
| Saved workflow steps | Stored encrypted; the steps people see have typed secrets blank. |
| The guide | Never includes a password or other secret. |
| A run that needs a password or code | Asks you, then types what you send directly into the field. Not stored, not logged. |
| Saved sign-ins | An Autobot’s browser can keep your sign-ins for its sites, so scheduled runs need not ask. |
Who can do what
Permissions
| Who | Can |
|---|---|
| The person who recorded a workflow | Sees its steps, renames it, replays it and deletes it. Workflows are personal. |
| The person running it | Answers a password or one-time code prompt when a run asks. |
AI assist
Where AI helps
AI is used where it saves you work and is always visible: it writes the guide from your recording, and it finds elements that moved during a replay, marking those steps healed. You stay in charge of what gets published.
Connects to
How it fits with the rest of Autodocs and Autessa
FAQ
Passwords stay out of docs: questions
Will my password show up in the how-to guide?
No. The guide is written never to include passwords or other secrets, and the steps shown to people have typed secrets blank.
What about one-time codes?
A run that reaches a one-time code field asks you for the code, then types it straight into the field without storing or logging it.
Can scheduled runs sign in on their own?
They can use the sign-ins saved in an Autobot’s browser. If you turn on a fresh browser for each scheduled run, those runs start signed out of every site.
Try passwords stay out of docs on a task you do every week.
Record it once in Autodocs. You get the guide for your team and the workflow for next time.
No extension to install · nothing is published until you publish it
100% customizable, code and all
Make Autessa Autodocs fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours