If you want to turn a teammate's captured activity into a Scribe, how that works depends on your plan.
Pro Team: request, then approve
- In Team Activity, an admin finds a teammate's activity they'd like to turn into a Scribe.
- The admin sends a request. The teammate who captured it gets notified.
- The teammate reviews the request — in their own My Activity — and decides whether to approve or deny it.
- If approved, the Scribe is created. If denied, nothing is created, and the admin can ask again later.
Nothing is created just by requesting — the teammate who did the work always has the final say before anything is made from their activity.
Enterprise: publish directly
Enterprise admins can create and publish a Scribe from any workflow-mapped user's activity directly, without sending a request or waiting for approval. Activity is pseudonymized by default, so admins are usually working from pseudonymous activity rather than an identified person's — an org can turn this off at the super-org level if it wants activity to show real names instead.
Good to know
- On both plans, approval workflows (if your team uses them) still apply once a Scribe is created. See Approval workflows and Autocapture.
- This is a different step from the day-to-day review every captured activity goes through before publishing. See Reviewing and publishing captured activity as a Scribe or Page.