Security and data handling
Autodocs security: secrets out, drafts first, every workflow yours
Autessa Autodocs keeps passwords and other typed secrets out of every guide and every visible step, encrypts saved workflow steps, keeps workflows personal to whoever recorded them, and publishes nothing until a person does.
Visit the Autessa Trust Center ↗Controls
How does Autodocs handle data, access and audit?
| Area | How Autodocs handles it |
|---|---|
| Who can use Autodocs | People whose role can use agents. It is turned on per company like any Autessa built-in app. |
| Workflow ownership | Workflows belong to the person who recorded them. Only they see the full steps, rename, run or delete them. |
| Typed secrets | Never shown in the steps people see, never written into guides. Saved workflow steps are encrypted before storage. |
| Passwords and codes at run time | A run can ask for a password or one-time code; what you type goes straight into the field and is never stored or logged. |
| The recorder’s browser | One per person, run by Autessa in the cloud. Nothing else drives it while you record. |
| Live view requests | Each frame, click and keystroke is sent with a single-use signed request. |
| Where docs live | Folders in the company Autodocs Drive. Autodocs only reads and writes folders under Drafts and Knowledge base. |
| Publishing | Every doc is a draft until a person publishes it, including docs written from Autobot work. |
| Pictures | Shown through short-lived links when a doc is opened. |
| Deleting | Docs move to the Drive trash. Deleting a workflow keeps any doc written from it. |
| Scheduled runs | Can use a fresh browser per run that starts signed out of every site, and only take actions you have always allowed. |
| Usage limits | Browser time and steps count against your company’s agent browser limits. |
Nothing silent
Every AI action is labeled
When the browser’s AI steps in during a replay, the step is marked healed, and steps it did that the page may not bear out carry a warning. Run summaries never include typed values.
FAQ
Security questions
Does Autodocs record my passwords into the guide?
No. Guides are written never to include passwords or other secrets, and typed secrets never appear in the steps people see.
Who can see my recorded workflows?
Workflows are personal: they belong to the person who recorded them. The guides written from them live in the company Autodocs Drive, where Drive access applies.
Where can I find Autessa’s compliance reports?
In the Autessa Trust Center at trust.autessa.com.
Can an Autobot publish docs on its own?
No. Documents an Autobot writes arrive in Autodocs as drafts, and a person decides what is published.
Record with confidence.
Secrets stay out of your docs. Nothing is published until you say so.
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