Hello guys, is there any way to block users from signing into the Chrome browser on macOS devices with their personal accounts? We don’t need their accounts to be signed in within our managed Chrome browser. Can anyone help me with this?
188 Views
Replies (2)
Marked SolutionPending Review
Participant
4 months ago
Marked SolutionPending Review
Hey @tommy , I might have something that could work for you. It’s not exactly what you asked for, but you can use the configuration profile below to block users from signing in with their accounts on Chrome.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 |
<?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>BrowserSignin</key> <integer>0</integer> <key>PayloadDisplayName</key> <string>Google Chrome</string> <key>PayloadIdentifier</key> <string>com.google.Chrome.BED8C8D3-3FE2-4CD2-AF83-BCFFA21BDBD5</string> <key>PayloadType</key> <string>com.google.Chrome</string> <key>PayloadUUID</key> <string>BED8C8D3-3FE2-4CD2-AF83-BCFFA21BDBD5</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </array> <key>PayloadDisplayName</key> <string>Untitled</string> <key>PayloadIdentifier</key> <string>A2D47B8F-8845-42F1-84F5-91A34688D5EF</string> <key>PayloadType</key> <string>Configuration</string> <key>PayloadUUID</key> <string>A2D47B8F-8845-42F1-84F5-91A34688D5EF</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </plist> |
This should prevent any sign-ins on Chrome for your managed devices. Let me know if it helps!
But there is a catch with this configuration profile. It won’t allow any accounts to be signed in, including company accounts.
Marked SolutionPending Review
Participant
4 months ago
Marked SolutionPending Review
The above configuration profile works but in a different way. way. Make sure you test the configuration profile on a few devices first to confirm that it blocks sign-ins without impacting other Chrome functionalities. We had an issue where it blocked some extensions that required sign-in. Just a heads-up @tommy in case you run into something similar.
-
Expand
Save
Copy link
Scroll to top
