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 why flowscope cannot tie captured activity back to a named person once setup is complete, is in the Discovery trust addendum.
The pieces
- The desktop capture agent, a native 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
- flowscope sets up your organization in the dashboard, provides the software and the deployment values, and runs the analysis once data is flowing.
- The engagement admin, on the customer side, runs the rollout from the dashboard: marking the agent and extension deployed, adding the cohort, and beginning capture. See Running the engagement from the dashboard.
- IT pushes the agent and the extension to the fleet. See Deploying the desktop agent with Microsoft Intune and Rolling out the browser extension.
- Each participant accepts the end-user agreement and pairs their device once. See the Employee guide.
The rollout, in order
- flowscope sets up your organization and gives the admin dashboard access.
- IT deploys the agent (Intune) and the extension (browser policy) to the cohort's machines.
- The admin marks both deployed in the dashboard, the readiness flags that gate beginning capture.
- 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.
- Each participant signs in with their work account, accepts the agreement, and pairs their device.
- A paired device does not start capturing yet. It stays idle, online but capturing nothing, until the admin begins capture, so nothing is recorded while people are still being set up.
- The admin clicks Begin capture once everyone is paired. This is the moment capture starts: every paired device begins capturing within a few minutes, only inside the agreed allowlist and never the permanent denylist. It also reveals a recovery key the admin must save, because flowscope wipes its own copy at this point, which is what makes captured activity something flowscope can no longer tie back to a named person.
- The engagement runs for its window, then winds down: capture stops, participants remove the software, and data follows the retention terms. See Ending the engagement.