If your Enterprise team uses approval workflows to review documentation before it goes live, that same process applies automatically to Scribes created through Autocapture.
How it works
Autocapture-created Scribes go through the exact same approval process as those created manually. If your team has approval workflows turned on, a Scribe made from captured activity can't be published directly — it has to be submitted for approval and reviewed first, just like any other Scribe. Team and System Admins can still publish right away without submitting for approval.
What this means for you
- If you create a Scribe from your own captured activity, it goes into the same review queue as anything else you create.
- Reviewers see and approve Autocapture-created Scribes the same way they review any other submission. There's no separate process, and no way around it.
Where to learn more
For details on setting up approval workflows, choosing reviewers, and what your team sees at each stage, see Controlling what gets published with approval workflows.
Good to know
Whatever review rules your organization has already set up apply automatically to Autocapture content — you don't need to configure anything separately.