While all of our extensions are publicly available, in order to use them you require a contract with Textshine. In this process you will receive a token.
It is possible for your IT department to supply a token in the managed_storage for browser extensions in your internal chrome distributions. The extension will recognize the managed token and the user will not be presented with the option of supplying a token, this also means they can’t see the token from within the extension. See the section below for a walkthrough.
Create a .plist file at /Library/Managed Preferences/com.google.Chrome.extensions.hionipacjacmkefllhlalaaofmcflkdk.plist with the following 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>managed_token</key>
<string>[the token/license key you have received from Textshine]</string>
</dict>
</plist>
chrome://policy