Using Autocapture

Currently available as a private beta to select customers.

Autocapture automatically surfaces the workflows your team runs, including the ones no one thought to document. It runs quietly in the background across your team's approved apps, giving you a complete picture of how work actually happens, where gaps exist, and click-to-publish guides your teams and AI agents can act on.


How it works

  1. Autocapture discovers workflows from team members who have the Scribe extension installed.
  2. You're notified when your team’s workflows and their documentations are ready for review.
  3. Review your team’s workflows and turn them into sharable SOPs in just a few clicks.

Coming soon: Autocapture will notify you when a captured process has changed from what was mapped, so you can keep your library up-to-date automatically.


Roles

Autocapture has two roles during the beta:

  • Admins can turn Autocapture on, enroll team members, view the team's workflows, create and edit SOPs and Scribes, and share them with the team.
  • Creators can view the team's workflows, create and edit SOPs and Scribes, and share them with the team.

Creating a Scribe based on a specific team member's workflow requires that person's approval.


Plans

Available to Pro Team and Enterprise customers during beta.


FAQs

Can other teammates look at my individual activity?

No. SOPs are generated from aggregated activity. Your inidvidual activity stays anonymous unless you choose to create a Scribe yourself.

What measures are in place to ensure Scribe collects only relevant user workflows?

Scribe collects data only from 150 top business apps and apps your org has already created a public scribes for. No data is collected from other applications.

Scribe also mutes keystroke detection on fields tagged as secure, like credential fields and credit card entry fields, to prevent incidental collection of sensitive data.

What activity does Autocapture record?

Screenshots, clicks, and text entered by users, only from the applications that Scribe has permission to capture. The data is transferred via HTTPS connections to Scribe’s cloud environment. All data is encrypted at rest and in transit throughout the data flow, and Scribe sits behind a web application firewall.

How does Scribe handle sensitive data in screenshots?

Scribe automatically mutes keystroke detection on credential and payment fields. Enterprise admins can also configure Smart Privacy Screen (SPS), which automatically redacts sensitive data categories — including PII, personal health information, and payment card data — from all screenshots captured by Scribe. End users cannot disable or override this setting.

What happens after Autocapture records a workflow? Scribe surfaces it for your review in the workflow view. You can see where documentation exists and where gaps remain, then review, edit, and publish guides, or discard them. Nothing is permanently saved ,or shared, without your express approval.

Who can access my data? Access is strictly limited to a small number of Scribe software engineers and support personnel, only when needed to troubleshoot or resolve issues, under a least-permissions access control policy. No other Scribe employees can view or use your data unless you have explicitly shared a Scribe.

Details regarding Scribe's security and privacy controls are available in the Trust Center.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

Compare Scribe Plans
Find the right plan for you and your team.