What gets installed?
Activity capture uses enrolled Windows computers. Supported browser interactions require the browser extension and Windows bridge. Confirm the actual environment during setup.
Deployment & trust
Know what is collected. Decide what is in scope.
A useful deployment begins with a clear purpose. Agree on the people, devices, applications, and access needed to investigate the work.
The questions to answer before enrollment.
Explain the purpose to the people doing the work. Computer activity needs context. Set expectations, provide a way to ask questions, and review findings with the team.
What can be collected?
Depending on settings: application use, active and idle time, window titles, and interactions. Full capture or work recording can include committed field values and copied text.
What is excluded?
Monitoring capture excludes screenshots, raw keystroke logging, and recognized password fields. Sensitive content in ordinary fields or clipboard actions can still be captured when enabled.
Who can see it?
Set team visibility explicitly, with team-wide activity restricted to administrators by default. Configure workspace and client access separately, and agree on who reviews recordings, procedures, and automation outputs.
Use the current security documents.
Review hosting, subprocessors, retention and deletion, identity options, and the current assurance status with your technical team. The Trust Center describes the existing controls and unfinished assurance work; the DPA contains the binding processing terms.
Read the Trust CenterSee what you could change.
Know where to start.
Watch Isaac investigate a recurring task and see the procedure your team could build from it. Then discuss where Orchard could help your business and what getting started would involve.
- See a relevant product example
- Review your workflow and setup
- Decide whether it’s a fit
No installation or data upload needed for your demo.
What to expect from your demo