Assign Dedicated Licenses to Organization

This document shows you what is dedicated license and how to assign them to organization(s).

requirements

To assign dedicated licenses:

• You must have a True Enterprise subscription.
• You must have the Account Admin role.

What is a Dedicated License?

A dedicated license is a fixed number of licenses allocated to a specific Organization, limiting how many licenses that Organization/sub-Organization can use and manage.

When you purchase Katalon licenses, they are added to your Account-level license pool by default. This pool is shared across all users in the account, making licenses accessible to everyone. To streamline license management, we recommend grouping users into Organizations or sub-Organizations. Once organizations are in place, you can:

1. Assign dedicated licenses to each Organization or sub-Organization.
2. Define limits on how many licenses each group can access and manage.

---

Examples

The following examples illustrate how dedicated licensing functions across Accounts, Organizations, and Sub-Organizations:

First example: This account has 200 Katalon True Platform licenses. They assign 20, 10, 1, and 5 licenses to four Organizations, respectively. These numbers represent the dedicated licenses each Organization can use and they cannot exceed that amount.

• Dedicated: The total number of licenses explicitly assigned to an Account, Organization, or Sub-Organization.
• Pool: The number of licenses still available after allocation to sub-levels (e.g., from Account to Organization, or Organization to Sub-Organization).
• Assigned User: The number of users who have actively claimed a license in that specific level.
• Available: The number of unclaimed licenses remaining at that level, ready to be assigned to users.

---

Second example: This Organization receives 10 dedicated licenses. It then assigns 5 licenses to a sub-Organization, reducing its remaining pool to 5 licenses.

If they later create a second sub-Organization, they can assign it up to 5 licenses, depending on what's left in the parent Organization’s pool.

---

Assign Dedicated Licenses

To assign licenses to an Organization that has not received any dedicated licenses yet:

1. Go to Account Settings > Account > License Management.
2. Click Assign Dedicated Licenses.
3. In the dialog, select an Organization or sub-Organization (OG-...) from the dropdown, enter the number of licenses to allocate, then click Assign.

You can assign dedicated licenses only after the target Organization or sub-Organization has already been created in your account structure.

---

Configure License Usage Policy

Availability: True Enterprise only.

This policy controls which Organization's license pool users can consume from and applies only to Katalon Runtime Engine (KRE) session-based licenses running outside of Platform. Seat-based licenses (KSE, TestOps) are not affected.

Configure the policy

1. Go to Account Settings > Account > License Management.
2. In the License Usage Policy panel, select a policy from the Policy dropdown.
3. (Optional) Disable Allow fallback to Account pool if you want to block access immediately when the Org pool is exhausted.
4. To revert to the original settings, click Restore Default.

Important: Policy changes take effect immediately for all subsequent license requests.

Available policies

Policy	User can consume licenses from
Unrestricted (default)	- Any eligible license pool (Account/Organization) with available dedicated licenses
Member-based	- User's assigned Organization - Any Organization where the user is a member of at least one project
Strict	- User's assigned Organization only

Assigned Organization vs. Project Membership?

A user can belong to only one Organization that they are assigned. However, they can join multiple projects across different Organizations, despite not belonging to these Organizations.

For example, the user below belongs to an Organization called Katalon on Katalon, while also joining projects named "TestCloud Daily Test" and "Cloud-based Test Execution", outside their Assigned Organization.

Fallback behavior

All three policies share the same fallback behavior. By default, Allow fallback to Account pool is enabled.

• If enabled (default), users can continue by drawing from the Account pool when the Organization pool is exhausted.
• If disabled, access is blocked as soon as the Organization pool is exhausted.