User Licenses

The license and user information in the Dashboard may vary according to how user licenses are configured in your license file. As a typical customer who bought Acrolinx, you'll only need to use named user licenses. However, if you build your own integrations, you might also consider using volume-based licenses.

Your Acrolinx project consultant can help you with the licensing details and is happy to explain the differences.

You can find details on your Acrolinx license file in our article on how to request, install, and review your license file.

Named User Licenses

A named user license is for a fixed number of users. This type of license is intended for customers with a fixed number of dedicated users who all access the server on a regular basis.

Named users consume a user license after they run their first check. From this moment, a named user is considered "active". An Acrolinx administrator can release a named user license from a user, which will make that user "inactive".

Named users can always connect to Acrolinx regardless of how many other users are connected.

Manage Your Users

To release a license, follow these steps:

  1. Make sure that your role has the 'Release user licenses' privilege.
  2. Navigate to Users in the Dashboard
  3. Click on a user with a License Type: (inactive)
  4. Under User Administration > License Status, click Release License.

Volume-Based Licenses

A volume-based license is for a specified number of words that can be checked within a month from a specific integration. This type of license is intended for API users and custom integrations that don’t require registration of usernames when the integration communicates with Acrolinx. However, volume-based licenses can also be applied to standard Acrolinx Integrations.

Volume-based licenses don’t limit the number of users.

When you use a standard Acrolinx Integration with a volume-based license, you register with an Acrolinx Core Platform by entering a username and password as usual. However, the integration doesn't start a user session but instead uses the volume-based licensing mechanism for checking. For this reason, volume-based limits override any other limits such as limits on named users. A user can check with an integration that has a volume-based limit even if there are no named user licenses available.