When you look at a captured workflow in Team Activity, Scribe checks it against your team's existing Scribes and shows any it thinks might already cover the same work. You can then use the existing Scribe, dismiss the match if it's wrong, or create a new one — nothing is created or removed automatically.
Why this happens
As your team builds up more Scribes, it gets harder to know what's already covered. This feature is designed to help you notice that before you create something new.
You’ll see it in Team Activity, when you click into a workflow, Scribe surfaces any existing Scribes it thinks may already cover that same workflow under Documents.
It allows you to
Review the suggested matches before deciding whether to create something new:
- If an existing Scribe already covers the work, you can use that instead.
- If it doesn't quite fit, you can still create a new Scribe from the captured activity.
Keep in mind this isn't automatic duplicate prevention. Scribe doesn't block you from creating a new Scribe, and it doesn't merge or delete anything on its own. It gives you the information to make that call yourself, before you commit to creating something new.
Good to know
- Every captured activity goes through a human preview first before creation.
- This works alongside the normal review step: even after you create a Scribe, it still needs to be published before your team sees it.
- For Enterprise customers, approval workflows can ensure that Scribes created from activities are reviewed and approved by an admin before they’re published. See Approval workflows and Autocapture for details.