Comparison of Licenses

In aqua, you have the flexibility to assign various licenses to your users based on your specific requirements. These licenses are ordered to match your needs. It's important to understand that the permissions associated with these licenses take precedence over the permissions granted by user roles. While you can further restrict permissions using roles, you cannot extend them beyond what the license allows.

For instance, let's say you assign the "Project Administrator" role to a user with a Basic license. However, the user will still not have the privilege to create test cases because this action is restricted by the license.

Now, let's dive into the types of licenses available:

• Named License: This type is exclusive to a single user at a time. Each named license corresponds to one user.

• Floating License: Floating licenses can be assigned to multiple users. However, it's important to note that only as many users can be actively logged into aqua at the same time as there are available floating licenses.

Additionally, when you order aqua Pro or aqua ALM licenses, you'll receive one additional license for an automation agent of your choice. These agent licenses don't require manual assignment, as they are automatically applied by the respective agents when they're initiated.

In the following section, you'll find a comprehensive list detailing all the distinctions between the different aqua licenses. This will help you make informed decisions when it comes to selecting and assigning licenses to your users, ensuring your aqua setup aligns with your specific needs and constraints.

comparision table view

Other available licence types such as Jira Sync, Jira Plugin, DevOps are used for integration purposes only. This means that if you want to set up the integration with Jira or AzureDevOps, you should assign one of these licences to the technical user, which will only be used to synchronise the items between the integrated platforms.