System Requirements

Last updated: 7 November 2026

The organization chooses, for each session, Browser Monitoring, Desktop Monitoring, or both, and whether identity verification, session recording, and a second camera are turned on. Browser Monitoring uses a supported browser on the candidate’s computer and does not install an application. Desktop Monitoring uses the Meritclaw desktop application and can observe operating-system signals that the browser cannot. A phone is used only when a second camera is turned on. No application is installed on the phone, and the phone itself is not monitored — only the camera stream the candidate shares.

Meritclaw Desktop Application — macOS

When the organization requires Desktop Monitoring, the candidate installs the Monitoring Application on their Mac before the session. Identity verification, session recording, and a second camera run only when the organization has turned that feature on for the session.

Meritclaw Desktop Application — Windows

When the organization requires Desktop Monitoring on Windows, the Monitoring Application provides the same capabilities as the macOS version. Identity verification, session recording, and a second camera run only when that feature is turned on for the session.

Dual-Camera Monitoring — Phone

When the organization has turned on a second camera, the candidate scans a QR code shown in the browser or in the desktop application and shares the phone’s camera in a supported mobile browser. No application is installed on the phone. The phone is not subject to Browser Monitoring or Desktop Monitoring.

Using Meritclaw during a video call

Candidates often start a session while they are already on Google Meet, Microsoft Teams, or Zoom. The webcam can be shared only in certain setups. This applies to Browser Monitoring and to OS Monitoring.

The reliable setup is to keep Meritclaw and the video call as tabs in the same Chrome window. That works on Windows and macOS with no extra configuration.

• macOS. The system shares the camera across apps and browsers, so no extra setup is required.
• Windows 11 (build 26200 and later). If the call is in another browser or in a desktop app, enable Multi-App Camera using the steps below.
• Windows 10, and Windows 11 before build 26200. A call in a different browser, or a desktop conferencing app alongside Browser Monitoring, can lock the camera so only one program can use it. Keep Meritclaw and the call in the same Chrome window.
• Zoom, Teams, or Meet desktop on those older Windows versions. The conferencing app can hold the camera exclusively, including when OS Monitoring is running. Briefly turn its camera off. Meritclaw usually acquires the feed within about 10 seconds, then turn the conferencing camera back on. On Windows 11 build 26200 and later, Multi-App Camera avoids this for Zoom’s desktop app.

Windows 10 builds before 1803 cannot share the camera between Meritclaw and a conferencing app. Meritclaw already requires Windows 10 version 1809 or later, so those builds are not supported.

Enable Multi-App Camera

Multi-App Camera lets Meritclaw and a video call use the webcam at the same time. It is available on Windows 11 build 26200 and later, and it is needed when Meritclaw and the call run in separate browsers or as separate desktop applications.

1. Open Settings → Bluetooth & devices → Cameras.
2. Select the camera you will use.
3. Open Advanced camera options.
4. Turn on Multi-App Camera.
5. Restart Meritclaw and the conferencing app.

Web Browser — Organization Dashboard

Organizations access Meritclaw through a web browser. No installation is required.

JavaScript must be enabled. Pop-up blockers should allow meritclaw.com. For live-session viewing, WebRTC support is required (included in all browsers above).

Network Requirements

The following domains and ports must be reachable from the candidate’s computer and phone. Corporate firewalls and VPNs may need to allowlist these.

UDP connectivity is strongly recommended for real-time media. If UDP is blocked, Meritclaw falls back to TCP (TURN), which may increase latency.

Not Currently Supported

The following platforms are not supported for taking monitored sessions:

• Chromebooks / Chrome OS
• Linux desktops
• Tablets (iPad, Android tablets) as the primary device
• Mobile browsers as the primary session device (phones are supported only as a second camera)
• Virtual machines or remote desktops (these are detected and flagged)

Questions?

If you have concerns about meeting these requirements, contact the organization that invited you. For technical support, reach us at support@verificient.com.