Introduction
Looking to get Antidote up and running for members of your organization? The references collected here are for administrators and technicians, just like you. We understand each organization has specific needs, which is why we offer many ways to deploy Antidote. The table below lists your options based on the product you purchased: an Antidote 12 per-device license, an Antidote Pro subscription or an Antidote Web subscription.
The column on the left is divided into six sections representing the different steps that can be involved in deploying the software. Each section includes various procedures, which you can quickly access by clicking the links provided. The columns in the middle indicate which Antidote product the procedures apply to. Finally, the column on the right explains the purpose of these procedures or the conditions that must be met.
Follow the procedures laid out here, and after accepting your invitation to connect, users will be able to access all of Antidote’s powerful tools—the corrector, the dictionaries and the language guides.
Options for deploying Antidote based on your organization’s product
| Antidote 12 | Antidote Pro | Antidote Web | Details | |
|---|---|---|---|---|
| Configuring single sign-on (SSO) and provisioning—optional | For organizations with an identity provider (Microsoft’s Entra ID, Google Cloud, etc.) | |||
| Configuring SSO (SAML) | Create accounts with your identity provider and use the same authenticators to access Antidote. Grant access to Antidote when users log in. |
|||
| Configuring automated provisioning (SCIM) | Synchronize users and groups with your identity provider. Grant access to Antidote based on the groups in your identity provider. Assign organization roles (administrator, technician, etc.) using your identity provider. |
|||
| Managing accounts in the Client Portal | For all organizations | |||
| Creating accounts | Create accounts manually, by using email addresses or by importing a CSV or Excel file. |
|||
| Granting access to Antidote | Manage access to Antidote. Works with synchronized accounts if you didn’t grant access when you configured provisioning. |
|||
| Assigning roles in Antidote | Authorize certain accounts to share writing standards with other users within the organization (dictionaries and custom rules for the corrector). Antidote Web only, specifically for schools: authorize certain accounts to manage group permissions (e.g., restricting access to the corrector). Works with synchronized accounts. |
|||
| Installing the software—Administrators | ||||
| Deploying Antidote 12 on multiple devices automatically | For Windows only. With the command line, GPO, RDS, Intune, etc. Can be done with the deployment manager. Connectix installation included. |
|||
| Deploying Antidote 12 from one workstation to another | Install Antidote 12, including Connectix, one device at a time. |
|||
| Deploying Connectix on multiple devices automatically | For Windows only. With the command line, GPO, RDS, Intune, etc. Can be done with the deployment manager. For Antidote Web users to benefit from integration with their other software. Optional installation; recommended for users to avoid having to copy-paste. |
|||
| Deploying Connectix from one workstation to another | For Antidote Web users to benefit from integration with their other software. Optional installation; recommended for users to avoid having to copy-paste. |
|||
| Installing the software—Users | ||||
| Authorizing users to install Antidote 12 | For users with administrator rights on their computer | Users can download the installers from the Client Portal once the corresponding setting has been enabled. The instructions on how to install the software must be provided to users. |
||
| Inviting users to install Connectix | For Antidote Web users to benefit from integration with their other software. The instructions on how to install the software must be provided to users. Optional installation; recommended for users to avoid having to copy-paste. |
|||
| Activating the license | ||||
| Activating the license during the installation | License information is required to install the software. |
|||
| Activating the license when logging in | Users must log in to confirm their access the first time they use the software. |
|||
| Sending invitations | ||||
| Sending required invitations | Check if sending users an invitation is required and if it is handled by Druide or the organization. Email templates are available to notify users that they have access. |
|||