About Administration
This document discusses the different levels of administration in Katalon TestOps.
- TestOps Legacy
- TestOps
Current version
Katalon TestOps has 3 (three) management levels:
- Account
- Organization
- Project
The Account level is the highest level, followed by the Organization level, then the Project level.
The Account level is in charge of subscription and billing management functions. One Account is associated with one Organization.
At the Organization level, members can collaborate across several projects. One Organization can own one or multiple Projects.
The Project level facilitates the management of a project and its members.
Katalon TestOps organizes users into 4 (four) specific roles:
- Owner: The Owner has the highest authority that has full permissions. This is the default role for the user who creates an Account, Organization, or Project.
- Administrator: The Administrator has the next level of permissions, they are in charge of administrative functions. This role is granted by the Owner.
- Billing Manager: The Billing Manager is responsible for managing billing for Katalon Platform subscriptions. This role is granted by the Owner or Admins. A Billing Manager is under Account level and cannot be added to the Project.
- Member: Members have the lowest level of permissions. This role is automatically assigned to any person accepting the invitation to join an Organization or Project. They can view and run tests, but they do not have any added administrative functions by default. They can be assigned different roles to expand their privileges.
- For organizations created before December 20th 2023, Katalon still maintains the old structure which has 4 management levels: Account, Organization, Team, and Project. The Account level is the highest, followed by the Organization, Team, and then Project levels.
For a more specific breakdown of what each role's permissions are, refer to:
Roles and permissions at the Team level (For organizations created before December 20th, 2023)
View user roles within an Organization
You must be the Owner or Administrator of your Organization. If you would like to grant this privilege to a member, see: Change user role.
Roles and permissions at Account and Organization level
Roles and permissions at Account level
Members do not have access to administrative features by default. Assign them another role to expand their privileges. To learn how, see: Change user role.
Permissions | Roles | |||
Owner | Admin | Billing Manager | Member | |
User Management |
|
|
|
|
Subscription Management |
|
|
|
|
Payment Method |
|
|
|
|
License Management |
|
|
|
|
Organization Management |
|
|
|
|
Account Settings |
|
|
|
|
Product Utilization |
|
|
|
|
Security Settings |
|
|
|
|
Support Management |
|
|
|
|
Project Management |
|
|
|
|
User Group Management |
|
|
|
|
Roles and permissions at Organization level
Members do not have access to administrative features by default. Assign them another role to expand their privileges. To learn how, see: Change user role.
Permissions | Roles | ||
Owner | Admin | Member | |
User Management |
|
|
|
Organization Settings |
|
|
|
License Management |
|
|
|
Product Utilization |
|
|
|
Security Settings |
|
|
|
Support Management |
|
|
|
Project Management |
|
|
|
User Group Management |
|
|
|
If a member receives a checkout link generated by someone else, they can subscribe to and checkout licenses on Katalon TestOps. This is only applicable if there is no predefined payment method. See: Katalon License Subscription.
Roles and permissions at the Project level
Applicable to Organizations created from December 20th, 2023 onward.
A Project consists of a group of members working on the same projects. Only members can view and access their projects.
A Project is created by either the Owner or Admins of an Organization. To learn how to create and manage a Project, see: Create and manage a Project.
Permissions | Roles | ||
Owner | Admin | Member | |
Project Management |
|
|
|
Roles and permissions at the Team level
This documentation is only for the Organizations created before December 20th, 2023.
A Team level consists of a group of members working on the same Projects. Only members can view and access their projects.
A Team is created by either the Owner or Admins of an Organization. To learn how to create and manage a Team, see: Create and manage a Team.
Permissions | Roles | ||
Owner | Admin | Member | |
Project Management |
|
|
|
Team Management |
|
|
|
Alternate version
Katalon TestOps's administration framework is structured as a tiered system, consolidating all Account management functions and TestOps settings into a single section labeled Admin. Its hierarchy consists of three levels. In order of highest to lowest, they are:

The Account level is at the top of the hierarchy, followed by the Organization level, and then the Project level.
Account Level
At the top of the hierarchy is the Account. It serves as a control center for all universal settings and acts as a repository for Organizations, Projects, and Users.
Within this level, you can access the following functions:
- General Account information
- License Management
- License Utilization
- System Configurations
Account Admins govern this level and have all permissions needed to administrate functions outside of direct testing, like managing account information, subscriptions, license reports, and user permissions.
Learn how you can turn a user into an Account Admin here.
Each Account has its own unique ID. Within the UI, an account number is identified by looking for a prefix of AC.

In the image above you can see the Account number below the Account's name, depicted as AC-164XX.
Organization Level
In the middle of the hierarchy is the Organization. It serves as a control center to manage Organizational assets.
Within this level, you can access the following functions:
- Organization Management
- Portfolio Management
- User Management and their corresponding organizations
- It can be subdivided into any amount of sub-Organizations.
A User can only belong to one Organization, but is free to work on multiple Projects that are under different Organizations.
Each Organization has its own unique ID. Within the UI, an Organization number is identified by looking for a prefix of OG.

In the image above you can see the Organization numbers beside the Organizations' names.
Project Level
At the bottom of the hierarchy is the Project level. Its main function is to manage Users in detail and define their project configurations.
Within this level, you can access the following functions:
- General Project Information
- Project Members and their roles
- Project Configurations
Learn how you can turn a user into a Project Admin here.
Each Project has its own unique ID. Within the UI, a project number is identified by looking for a prefix of PJ.

In the image above you can see the Project numbers beside the Projects' names.
About new Users
When a person is first invited to join an Account, they are automatically assigned the User role and become affiliated with a single Organization.

- If there is no Organization chosen during the invitation phase, then the user will be affiliated directly with the Account instead.
While they possess the default User role, they do not have access to most of TestOps' features, so it's generally recommended that they be reassigned to a more appropriate role immediately. There are premade roles that an Account Admin can leverage to grant access quickly. You can:
Assign a User Account Roles: These roles are best for operational administrators who need access to features related to Account management, licensing management, User and permission management, or system configurations.
Assign a User Project Roles: These roles are best for testers who have to set up general Project settings, configurations, or integrations, or have to use features in TestOps that have to do with the actual testing process.
Upon reassignment, they are free to work between Projects or Organizations within the Account as needed.
To track a specific user's attributes and work spaces within Katalon TestOps, visit their User Detail page.