Licensing For SCIM Enabled Users
QMetry lets administrators manage license types for users provisioned through System for Cross-domain Identity Management (SCIM), either automatically or manually.
QMetry offers the following license management options:
Automatic Management: QMetry assigns and manages license types based on each user's assigned projects, roles, and available licenses.
If a user is assigned only Read-Only roles for all projects, QMetry assigns a "Read-Only" license, provided Read-Only licenses are available.
If a user has at least one project with a Non-Read-Only role, QMetry assigns a Regular license, provided Regular licenses are available.
If a user has at least one project with a non-read-only role, QMetry automatically assigns a "Regular" license, as long as Regular licenses are available.
Manual Management: The SCIM administrator assigns and manages license types using the custom attribute QMetry_User_LicenseType.
Prerequisites
You have Super Administrator access. SCIM settings are configured at the instance level and can only be managed by the Super Administrator.
You have a supported SCIM 2.0 provider, such as Okta.
Allotting and Managing User License Types (Regular or Read-Only)
To allot and manage license types for SCIM enabled users, perform the following steps:
 |
Go to System Settings.
Select SCIM.
Enable SCIM Provisioning.
Under Allot and Manage License Type (Regular or Read-Only) to Users, select one of the following options:
User license type will be intelligently auto-allotted and managed by QMetry based on user-assigned projects, roles, and license availability.
User license type will be allotted and manually managed by the SCIM administrator through the custom attribute QMetry_User_LicenseType.
Understanding Scenarios for Automatic User License Management in , QMetry
QMetry intelligently assigns and manages user licenses based on the user's assigned projects, roles, and available licenses. Below are different scenarios outlining how licenses are allotted:
Scenario | User License Action | Activation Status |
|---|---|---|
A new user is created with a Read-Only role assigned to all projects. | Read Only | User Active |
A new user is created with all Non-Read Only roles (Admin, Tester, QA Manager, etc.) assigned to projects. | Regular | User Active |
User Update (current license: Read Only) | ||
The user has all project access as Read-Only, and a new project with a Read-Only role is assigned. | Read Only | Older projects remain as assigned. The new project and role are assigned as Read-Only. |
The user has all project access as Read-Only, and a new or existing project with a Non-Read-Only role is assigned. | License type changed to Regular | Older projects remain as assigned. The new or updated project and role are assigned. |
User update (current license: regular) | ||
The user has all project access as Non-Read-Only, and a new project with a Non-Read-Only role is assigned. | Regular | Older projects remain as assigned. New or updated project or role are assigned. |
The user has all project access as Non-Read-Only, and a new project with a Read-Only role is assigned. | Regular | Older projects remain as assigned. New project or role are assigned. |
All of the user's projects are assigned or updated to a Read-Only role. | License Type Changed to Read Only | Older projects remain as assigned after the project with a Non-Read-Only role is removed. The updated project and role are assigned. |
Scenario | User License Action | Activation Status |
|---|---|---|
New User is created with Read Only role assigned to all projects | Regular License | User Active. |
New User is created with any 1 Non Read Only role (Admin, Tester, QA Manager, etc.) assigned to any projects | Regular License | User Active. |
User Update (current license: Read Only) | ||
User has All Project Access as Read Only Role and a new Project with Read Only Role is assigned | Read Only | Older projects remain as assigned. Assign the new project/role. |
User has All Project Access as Read Only Role and a new/existing Project with Non Read Only Role is assigned | License Type Changed to Regular | Older projects remain as assigned. Assign the new/updated project/role. For auto-conversion audit log should be recorded. |
User Update (Current License: Regular) | ||
User has All Project Access as Non Read Only and a new Project with Non Read Only Role is assigned | Regular | Older projects remain as assigned. Assign the new project/role. |
User has All Project Access as Non Read Only Role and a new Project with Read Only Role is assigned | Regular | Older projects remain as assigned. Assign the new project/role |
User has all projects assigned or updated as Read Only Role | License Type stays as Regular | Older projects remain as assigned, after the project with non-read only role is removed. To apply the change, the SCIM administrator must push the group on the Push Groups tab, or assign and unassign the project to the same user. |
Scenario | User License Action | Activation Status |
|---|---|---|
A new user is created with a Read-Only role assigned to all projects. | Read-Only | User is Active. |
A new user is created with any one Non-Read-Only role (Admin, Tester, QA Manager, and so on) assigned to any projects. | Error: the active Regular user limit is exceeded. Contact your QMetry administrator to increase the license limit or deactivate other users. | |
User Update (Current License: Read Only) | ||
The user has all project access as Read-Only, and a new project with a Read-Only role is assigned. | Read Only | Older projects remain as assigned. The new project and role are assigned. |
The user has all project access as Read-Only, and a new or existing project with a Non-Read-Only role is assigned. | License stays Read-Only. QMetry could not update the license type to Regular because the Regular license limit is exhausted. To resolve this, deactivate existing Regular license users or purchase additional licenses. | Older projects remain as assigned. The new or updated project and role are assigned. |
User Update (Current License: Regular) | ||
The user has all project access as Non-Read-Only, and a new project with a Non-Read-Only role is assigned. | Regular | Older projects remain as assigned. The new project and role are assigned. |
The user has all project access as Non-Read-Only, and a new project with a Read-Only role is assigned. | Regular | Older projects remain as assigned. The new project and role are assigned. |
All of the user's projects are assigned or updated to a Read-Only role. | License Type Changed to Read Only | Older projects remain as assigned after the project with a Non-Read-Only role is removed. The updated project and role are assigned. |