PulseZoom and Microsoft Teams settings (for admins)
The settings for enabling automatic chat notices in Zoom and Teams.
How to apply automatic chat notices across a workspace for Zoom and Microsoft Teams meetings. On Windows machines, configuring Pulse is all that is needed. On macOS machines, you also grant accessibility permission so that Pulse can type into the meeting app's chat field. That permission can be granted in bulk through MDM or individually by each user.
Enterprise plan
You need Pulse workspace administrator rights. To grant accessibility permission in bulk on macOS machines, you also need administrator rights in your MDM (Jamf, Intune, Kandji, Mosyle, Meraki and so on). This covers the desktop versions of Zoom and Microsoft Teams on macOS and Windows.
This article is for administrators applying it across a workspace. To set it up for your own account only, see Automatic Zoom and Teams chat notices (for individuals).
1. Grant accessibility permission
Accessibility permission is needed for Pulse to type the message into the meeting app's chat field. There are two ways to grant it.
Granting in bulk through MDM: on managed machines you can grant the permission in advance, so users never see the macOS permission dialog. It is distributed as a PPPC (Privacy Preferences Policy Control) configuration profile pre-approving Pulse for the accessibility service. An example is in the next section.
Users granting it individually: without MDM, ask each user to open System Settings > Privacy & Security > Accessibility and switch Pulse on in the list. The detailed steps, the differences in screen names between macOS versions, and what to do when it does not work are collected in Automatic Zoom and Teams chat notices (for individuals), which you can share internally as-is.
Example PPPC configuration profile (macOS)
Below is an example .mobileconfig. Use it as-is, or as a starting point to adapt to your own setup.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PayloadContent</key>
<array>
<dict>
<key>PayloadDescription</key>
<string>Grants accessibility permission so the notice can be posted to meeting chat.</string>
<key>PayloadDisplayName</key>
<string>Privacy Preferences Policy Control</string>
<key>PayloadIdentifier</key>
<string>jp.example.allow-transparency-accessibility.pppc</string>
<key>PayloadOrganization</key>
<string>〔organisation name〕</string>
<key>PayloadType</key>
<string>com.apple.TCC.configuration-profile-policy</string>
<key>PayloadUUID</key>
<string>c540d023-71d6-479b-bff4-aab0c91f6860</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>Services</key>
<dict>
<key>Accessibility</key>
<array>
<dict>
<key>Allowed</key>
<integer>1</integer>
<key>CodeRequirement</key>
<string>identifier "〔bundle ID〕" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = 〔team ID〕</string>
<key>Comment</key>
<string></string>
<key>Identifier</key>
<string>〔bundle ID〕</string>
<key>IdentifierType</key>
<string>bundleID</string>
<key>StaticCode</key>
<integer>0</integer>
</dict>
</array>
</dict>
</dict>
</array>
<key>PayloadDescription</key>
<string>Grants accessibility permission so the notice can be posted to meeting chat.</string>
<key>PayloadDisplayName</key>
<string>Allow Accessibility for automatic chat notice</string>
<key>PayloadIdentifier</key>
<string>jp.example.allow-transparency-accessibility</string>
<key>PayloadOrganization</key>
<string>〔organisation name〕</string>
<key>PayloadScope</key>
<string>System</string>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>af9418ef-8494-414a-8b29-b12951efd67b</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
</plist>
Put the Pulse desktop app's bundle identifier at 〔bundle ID〕 and the Apple Developer team ID used for signing at 〔team ID〕. This article gives no real identifiers. Replace 〔organisation name〕 with your own company and the PayloadIdentifier with a reverse-domain name based on your own domain. We recommend regenerating the PayloadUUIDs with uuidgen or similar.
PPPC profiles have to be delivered to machines enrolled in MDM. If the profile is installed manually it appears under System Settings > Profiles but the permission is not granted.
2. Enable the feature for the workspace
Open workspace settings
In the Pulse desktop app, open Settings > Workspace > General > Transparency > Automatic chat notices for teams.
Run setup
“Zoom and Microsoft Teams automatic chat notice” and click “Set up”.
Apply it to all users
Follow the prompts and click “Apply to all workspace users”.
The “Automatic chat notices for teams” settings screen, with the Zoom and Microsoft Teams notice enabled.
The message is sent once transcription has started (with a participant other than the user present) and the Zoom or Microsoft Teams window is in the foreground. It is not sent on a machine where partly typed text remains in the meeting chat field.
On macOS machines, confirm Pulse is switched on in the list under System Settings > Privacy & Security > Accessibility. Where you distributed through MDM, also confirm the profile is applied under System Settings > Profiles. Then hold a test meeting with two or more participants in both Zoom and Microsoft Teams and confirm the message is posted once in the chat.
Using it alongside the meeting apps' own notices
Zoom and Microsoft Teams each have their own notice features, which can be used alongside Pulse's automatic chat notice. Those are configured in each platform's own admin console; UNCHAIN, Inc. cannot configure them for you. What appears where is set out under “The meeting apps' own notices” in About the transparency features.
Announcing it internally
Announcement templates, likely questions and answers, and the points to note as monitoring of employees are collected in Enabling the transparency features for your organisation (for admins). Where you are asking macOS users to grant permission individually, include an explanation of what the accessibility permission is for. The prompt asks whether to allow the app to control your computer, which can worry people without an explanation.
Frequently asked questions
Q. Can users disable it themselves?
A. Where an administrator has enabled it across the workspace, users cannot turn it off from their own settings. On macOS, however, a user can technically revoke the accessibility permission in System Settings. On machines where the permission is distributed through MDM, the granted state is maintained by the profile.
Q. The message is not sent on some machines
A. What an administrator can check is two things: whether macOS accessibility permission is granted (it can be dropped immediately after an app update), and whether the desktop app is on the latest version. The machine-side checks — whether the meeting app window is in the foreground, whether partly typed text remains in the chat field — are collected under “If something is not working” in Automatic Zoom and Teams chat notices (for individuals). Share that article with users.
Q. Does it support Zoom or Teams in a browser?
A. This feature covers the desktop versions of Zoom and Microsoft Teams on macOS and Windows. Where many users join meetings from a browser, consider using it together with Watermark settings (for admins).
Q. People report confetti appearing when they join a meeting
A. Where Loom is running at the same time, Loom's confetti keyboard shortcut can collide with Pulse's send action. The steps to give users are in Automatic Zoom and Teams chat notices (for individuals).
Related articles
If that does not resolve it, contact tharada@the-unchain.com.