For self-hosted solution the minimal number of licences to acquired is 5, minimal term is 3 months.
For SaaS the minimal number licences is 1 and minimal term is 1 month.
Prices per seat are described here: https://qameta.io/#pricing
There was also ROLE_BOT described here, which was discontinued in the release 4.21.0.
Authority in cfg files | Global role in UI | Qty of consumed licenses | Description |
ROLE_ADMIN | Admin | 1 | Allows overall system administration + same rights as ROLE_USER |
ROLE_USER | User | 1 | This is a usual user who can work in projects and create projects. |
ROLE_Guest | Guest | 0 | Read-only user, not counted in the consumed licenses. This user can only view information in the projects where they are added to. No matter what, these users cannot do anything except viewing. |
Admin (user name is `admin`) user account | |||
ROLE_ADMIN | 1 | user `admin` is a special system account, cannot be deleted, cannot be altered via UI, it has all the capabilities as any Admin user and can be used to work as usual |
- Seats are the number of bought licenses, i.e. the total number of named users with roles Admin or User you are allowed to register in the system accordingly to the license agreement.
- Total paid licenses used is the current number of named users with roles Admin or User already registered in the system. In other words, it's the current consumption.
- Remaining is the number of named users with roles Admin or User you can allow to register in the system in addition to the Total paid licenses used.
admin
user account to be created and kept in the system.Admin's user name and password are defined in the configuration file, and it will be restored to the state described in the configuration to ensure you won’t lose the access to your Allure Testops instance.
You cannot delete/disable this user and you cannot remove the admin’s rights for this user – during the next start of Allure Testops, it will recreate the user again with all set of available rights, with the password defined in the configuration file.
ROLE_GUEST
Users with ROLE_GUEST have read only rights despite the project access permissions. To be able to create, manage, delete entities in Allure Testops the ROLE_USER is required.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article