Plugins and add-ins
Turn organization-wide add-in sign-in on or off for the Word Add-in and other plugins from Admin Settings → Integrations.
Plugins in Admin control whether users may sign in to Contracts AI from desktop add-ins (for example, the Microsoft Word add-in). This is separate from connecting cloud systems under Connected / Available integrations—those are storage and e-signature connections; Enable add-ins is specifically about plugin login for your org.
How to enable or disable add-ins (admin)
- Open Admin Settings.
- Select the Integrations tab.
- In the Plugins section, find the Enable add-ins card. The card explains: Allow users to sign in from the Word Add-in. When disabled, plugin login is blocked for this organization.
- Click Manage on that card. A side panel opens titled Enable add-ins (see settings sidebar).
- Select or clear the checkbox Enable add-ins (Word Add-in, etc.) to turn the setting on or off. The app saves the change when you toggle it (you should see a success message when it applies).
To use add-ins after they are enabled, users install or open the add-in from Word (or another supported host) and sign in with their normal Contracts AI credentials—unless this org-level setting blocks plugin login.
What this affects
- Word add-in — When enabled, users in your organization can authenticate from the Word Add-in; when disabled, plugin sign-in is blocked for everyone in the org, regardless of their other permissions.
- Other plugins — The same org setting is framed as Word Add-in, etc., so other supported plugins that use the same sign-in path follow this toggle.
Exact capabilities inside Word (clauses, gold standard, contract context) depend on your Word add-in version and org configuration.
User experience
Users open the add-in from Word’s add-ins experience, sign in once org policy allows it, and work in the document without switching to the browser for every action.
If you don’t see Plugins
The Plugins / Enable add-ins block appears on Admin Settings → Integrations when your layout and search filters show it. If your deployment doesn’t ship add-ins, the section may be absent—confirm with your implementation guide or account team.
Did this answer your question?