Configure Managed Mode

The following key and string value need to be configured in the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Grammarly\DesktopIntegrations]

"GrammarlyEnrollmentToken"="UUID"

where UUID is your Grammarly Enrollment Token with value type “REG_SZ”.

This change will switch Grammarly for Windows to Managed Mode; the Grammarly for Windows floating button will become gray, and the mode will prevent Grammarly for Windows from checking text until users sign in with the accounts provided by the organization.

If using JAMF or a similar tool, you can deploy a custom configuration profile (see instructions) with the following Preference domain: com.grammarly.ProjectLlama

The configuration profile template:

<?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>GrammarlyEnrollmentToken</key>
    <string>UUID</string>
  </dict>
</plist>

where UUID is your Grammarly Enrollment Token.

This change will switch Grammarly for Mac to Managed Mode; the Grammarly for Mac floating button will become gray, and the mode will prevent Grammarly for Mac from checking text until users sign in with the accounts provided by the organization.

The following key needs to be configured in the Windows Registry:

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\kbfnbcaeplbcioakkpcpgfkobkghlhen\policy]

The string value should include the following value:

"GrammarlyEnrollmentToken"="UUID"

Note: kbfnbcaeplbcioakkpcpgfkobkghlhen is the ID of the official Grammarly for Chrome extension, and UUID should be replaced with your Grammarly Enrollment Token with value type “REG_SZ”.

Grammarly for Chrome will switch to Managed Mode when it discovers a valid enrollment token and obtains the settings for your organization from our servers.

Once this is configured, here is what will change:

• Instead of a regular “Sign in” button, it will show a “Sign in with SSO” button that leads directly to the IdP URL.

• After login, it will display the “Managed by ...” label at the bottom of the extension’s pop-up dialog (the one that you see when clicking the G icon in Chrome’s extensions bar). Hovering over the company name would also display the enrollment token that it read from the settings.

Note: Make sure to restart the Chrome browser after modifying the registry for this change to take effect. For Windows 11, you will need to reboot or reload policies by accessing chrome://policy/ in Chrome.

This can be done by creating a .plist file in the /Library/Managed Preferences/{username} folder.

File name:

com.google.Chrome.extensions.kbfnbcaeplbcioakkpcpgfkobkghlhen.plist

File contents:

<?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>GrammarlyEnrollmentToken</key>
        <string>UUID</string>
  </dict>
</plist>

Note: Make sure to replace UUID with your Grammarly Enrollment Token.

Finally, convert the XML file to binary using the following terminal command:

plutil -convert binary1 {filename} com.google.Chrome.extensions.kbfnbcaeplbcioakkpcpgfkobkghlhen

If using JAMF or a similar tool, you can deploy a custom configuration profile (see instructions) with the following Preference domain:

com.google.Chrome.extensions.kbfnbcaeplbcioakkpcpgfkobkghlhen

You can then upload a .plist file with the file contents shown above. The file should be in XML format.

In the Google Admin panel, go to Apps & Extensions.

Navigate to the Users & browsers tab and click on Grammarly to open additional settings.

Find Policy for extensions and paste the following text, where UUID is your Grammarly Enrollment Token:

{"GrammarlyEnrollmentToken":{"Value":"UUID"}}

Then, save the changes. 

Note: Your UUID can be found on your Managed mode page when you unfold the Show configuration details section.

The following key needs to be configured in the Windows Registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\cnlefmmeadmemmdciolhbnfeacpdfbkd\policy]

The string value should include the following value:

"GrammarlyEnrollmentToken"="UUID"

Note: cnlefmmeadmemmdciolhbnfeacpdfbkd is the ID of the official Grammarly for Edge extension, and UUID should be replaced with your Grammarly Enrollment Token with value type “REG_SZ”.

Grammarly for Edge will switch to Managed Mode when it discovers a valid enrollment token and obtains the settings for your organization from our servers.

Note: Make sure to restart the Edge browser after modifying the registry for this change to take effect.

This can be done by creating a .plist file in the /Library/Managed Preferences/username folder.

File name:

com.microsoft.Edge.extensions.cnlefmmeadmemmdciolhbnfeacpdfbkd.plist

File contents:

<?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>GrammarlyEnrollmentToken</key>
      <string>UUID</string>
  </dict>
</plist>

Note: Make sure to replace the UUID with your Grammarly Enrollment Token.

The last step is to deploy your .plist file to your users’ Mac devices using your preferred MDM provider, such as Microsoft Intune. For instructions, see Deploy your plist.

For Jamf, upload the .plist file as a Custom Settings payload.

This is done by deploying Firefox Enterprise Policies. You must install and lock the extension (via ExtensionSettings) and then specify the enrollment token for the extension (via the 3rdparty policy).

To force-install Grammarly using Firefox’s ExtensionSettings policy and prevent users from turning off or uninstalling it, follow these steps:

1. Create a policies.json file and place it in the distribution folder inside Firefox’s installation directory (e.g., C:\Program Files\Mozilla Firefox\distribution\policies.json).
2. Insert the following content into the file:

{
 "policies": {
   "ExtensionSettings": {
     "87677a2c52b84ad3a151a4a72f5bd3c4@jetpack": {
       "installation_mode": "force_installed",
       "install_url": "https://addons.mozilla.org/firefox/downloads/latest/grammarly-1/latest.xpi"
     }
   },
   "3rdparty": {
     "Extensions": {
       "87677a2c52b84ad3a151a4a72f5bd3c4@jetpack": {
         "GrammarlyEnrollmentToken": "UUID"
       }
     }
   }
 }
}

What each part does:

• ExtensionSettings → force_installed: Automatically installs Grammarly and prevents users from turning off or uninstalling it.
• install_url: The evergreen AMO download URL. Firefox will auto-update the extension when new versions are released.
• 3rdparty → GrammarlyEnrollmentToken: Specifies the enrollment token for Managed Mode activation. Without this, Managed Mode won’t activate even if the extension is installed. Replace UUID with your Grammarly Enrollment Token.

Deploy a configuration profile (.mobileconfig) targeting org.mozilla.firefox, or place a plist at Firefox.app/Contents/Resources/distribution. 

Use this policy payload:

<dict>
 <key>Extensions</key>
 <dict>
   <key>Install</key>
   <array>
     <string>https://addons.mozilla.org/firefox/downloads/latest/grammarly-1/latest.xpi</string>
   </array>
   <key>Locked</key>
   <array>
     <string>87677a2c52b84ad3a151a4a72f5bd3c4@jetpack</string>
   </array>
 </dict>
 <key>InstallAddonsPermission</key>
 <dict>
   <key>Allow</key>
   <array>
     <string>https://addons.mozilla.org/</string>
   </array>
   <key>Default</key>
   <true />
 </dict>
 <key>3rdparty</key>
 <dict>
   <key>Extensions</key>
   <dict>
     <key>87677a2c52b84ad3a151a4a72f5bd3c4@jetpack</key>
     <dict>
       <key>GrammarlyEnrollmentToken</key>
       <string>YOUR_UUID_HERE</string>
     </dict>
   </dict>
 </dict>
 <key>EnterprisePoliciesEnabled</key>
 <true />
</dict>

What each part does:

• Extensions → Install: Tells Firefox to install Grammarly from the provided URL.
• Extensions → Locked: Prevents users from turning off or uninstalling Grammarly. The value must be the extension ID: 87677a2c52b84ad3a151a4a72f5bd3c4@jetpack
• InstallAddonsPermission: Allows Firefox add-ons from addons.mozilla.org.
• EnterprisePoliciesEnabled: Enables enterprise policy processing so Firefox applies the configuration above.
• 3rdparty → GrammarlyEnrollmentToken: Specifies the enrollment token for Managed Mode activation. Without this, Managed Mode won’t activate even if the extension is installed. Replace UUID with your Grammarly Enrollment Token.

Note: Restart Firefox after deploying the policy. You can verify whether it has been applied by navigating to about:policies in Firefox.

Managed mode on iOS is configured similarly to Grammarly for Mac, where Apple Configuration Profiles are used to manage iOS devices. Typically, IT team deploys configuration profiles to organization’s devices using centralized endpoint management software, such as Jamf.

Property List:

<dict>
  <key>GrammarlyEnrollmentToken</key>
  <string>UUID</string>
</dict>

Jamf configuration:

1. Add the Grammarly — Keyboard & Editor app to the Mobile Device Apps list.
2. Configure Distribution Method, Scope, and other settings according to your organization’s preferences.
3. Under the App Configuration tab, add PLIST and replace {UUID} with the UUID defined when enabling SSO for your organization.
4. Push the App Configuration to your organization’s devices, which will switch the Grammarly Keyboard & Editor app to Managed Mode.

Once Manage Mode is activated, users will be shown a screen prompting them to re-login with their organizational accounts. The Grammarly Keyboard & Editor app will allow sign-ins only using SSO.

The following key and string value need to be configured in the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Grammarly\OfficeAddin]

“GrammarlyEnrollmentToken”=“UUID”

where UUID is your Grammarly Enrollment Token with value type “REG_SZ”.

Grammarly for Microsoft Office will switch to Managed Mode when it discovers a valid enrollment token and obtains the settings for your organization from our servers. You can confirm this by clicking on the “About” option as seen below for Outlook.

Note: Users will need to restart Microsoft Outlook and Word after modifying the registry for this change to take effect.