Before you roll out

How a flowscope engagement works

All docs

You are rolling flowscope out at your company. This page is the shape of the whole thing: what an engagement is, the pieces involved, who does what, and the order it runs in. The guides beside it cover each step.

What a Discovery engagement is

A flowscope Discovery engagement is a time-boxed exercise, generally four weeks, in which a small, opted-in group of employees runs the capture software on their work machines. flowscope maps how work flows through the tools they use day to day and surfaces the strongest automation candidates. The cohort, the period, and the goal are agreed in advance; capture stays inside a scope the customer controls and stops when the engagement ends.

How personal data is minimized and how names are masked by default is in Your privacy and controls.

The pieces

  • The desktop application, a native Windows app IT pushes to each participant's machine through Intune. It observes workflow activity.
  • The browser extension, force-installed in Edge or Chrome by browser policy, for work inside the browser.
  • The flowscope dashboard, where the engagement admin manages the roster, marks deployment done, and watches devices come online.

Who does what

The rollout, in order

  1. flowscope sets up your organization and gives the admin dashboard access.
  2. IT deploys the desktop application (Intune) and the extension (browser policy) to the cohort's machines.
  3. The admin marks both deployed in the dashboard.
  4. The admin adds the cohort by email, and each person is emailed their pairing link as they are added, pointing at the flowscope app already on their machine.
  5. Each participant signs in with their work account, accepts the agreement, and pairs their device.
  6. A paired device does not start capturing yet. It stays idle, online but capturing nothing, until flowscope begins capture, so nothing is recorded while people are still being set up.
  7. flowscope begins capture. This is the moment capture starts: every paired device begins capturing within a few minutes, only inside the agreed allowlist and never the organization's denylist.
  8. The engagement runs for its window, then winds down: capture stops and participants remove the software. See Ending the engagement.