Turning off Workflow Mapping for a team stops Optimize from capturing new workflow data from that team's participants going forward. It's an org-level admin action, done per-team from the Workflow Mapping settings and it should be treated as a durable on/off, not something toggled casually.
This is different from a participant individually pausing their own Workflow Mapping; this is an admin-level, team-wide switch.
Who can do this
Only System Admins have access to the Workflow Mapping settings page where this control lives. Org Optimizers and Team Optimizers do not have access to toggle Workflow Mapping on/off — this is a System Admin–only action.
How it's done
Go to Settings → Workflow Mapping.
Click into the Team mining controls tab (this was split out from the main Workflow Mapping setup as a separate tab specifically to house the per-team toggle) to turn Workflow Mapping on for a team, you must go to the team Workflow Mapping controls tab to toggle mapping on/off.
Select the team and toggle Workflow Mapping off.
Good to know:
This is not meant to be toggled casually. Switching Workflow Mapping on/off repeatedly for a team is advised against: background capture is designed to capture large recurring patterns and is not meant for capturing a few actions and then being turned off shortly after — this could lead to data loss.
It doesn't override individual participant pauses, and vice versa.