AB Tutor v9: MacOS Screen Capture MDM Configuration

ABTutor requires Screen Recording permission (TCC - Transparency, Consent, and Control) on macOS to capture screens. Starting with macOS 10.15 Catalina, users must explicitly grant this permission. For managed environments, this can be pre-approved via MDM (Mobile Device Management) using a Privacy Preferences Policy Control (PPPC) profile.

Important: macOS does not allow programmatically bypassing the TCC prompt. The only way to silently grant screen recording permission is through an MDM-deployed configuration profile.

Note: Deployment of the ABTutorInstaller.pkg will only install the ABClient (Student Agent) and the ABHelper. If you need the AB Tutor Console, we recommend manually installing that on the select machines that require it. You will still need to deploy the ScreenCapture permissions via MDM.

1. Navigate to Computers > Configuration Profiles

2. Click + New to create a new profile

3. Configure the profile:

- Name: ABTutor Screen Recording Permission

- Category: (select appropriate category)

- Distribution Method: Install Automatically

4. Click Privacy Preferences Policy Control in the sidebar

5. Click + Add and configure each application:

- Identifier: com.abtutor.client

- Identifier Type: Bundle ID

- Screen Recording: Allow

- Identifier: com.abtutor.abhelper

- Identifier Type: Bundle ID

- Screen Recording: Allow

- Identifier: com.abtutor.console

- Identifier Type: Bundle ID

- Screen Recording: Allow

6. Click Scope and target appropriate computers/groups

7. Click Save

1. Navigate to Library > Privacy

2. Click Add New > Privacy Preferences Policy Control

3. Add each application using the identifiers above

4. Assign to appropriate blueprints

1. Navigate to Management > Profiles

2. Create a new Privacy Preferences Policy Control profile

3. Add the Screen Capture entries for each application

4. Deploy to target devices

1. Ensure the profile is deployed with System scope, not User scope

2. Check that the MDM is DEP-enrolled or user-approved

3. Verify the bundle ID matches exactly (case-sensitive)

1. The application may need to be restarted after profile deployment

2. On some macOS versions, a logout/login may be required

3. Check Console.app for TCC-related messages