Licensing Model Overview
Key Licensing Concepts
| Concept | Definition |
|---|---|
| Server users | Total count of all registered user accounts on the Polarion server. This is the number Risksheet uses to validate the license. |
| Polarion license holders | Users who hold an active Polarion ALM license (Reviewer, Author, Enterprise, etc.). This count is irrelevant to Risksheet license validation. |
| Named/Active users | Users explicitly added to the nextedy_risksheet_users group. These users can edit Risksheet data. The number of named users must not exceed the licensed named user count. |
| Read-only users | All server users who are not in the nextedy_risksheet_users group. These users can view Risksheet data but cannot edit. |
| SMB discount | A pricing tier that requires the Polarion server to have 50 or fewer total registered server users. |
License Types
Named User License
A named user license grants editing access to a specific number of users. The license specifies:- Server user limit — maximum total registered users on the Polarion server
- Named user limit — maximum number of users in the
nextedy_risksheet_usersgroup who can edit
Evaluation / Trial License
Evaluation licenses provide full Risksheet functionality for a limited time period. Key characteristics:- Full editing access for all users during the evaluation period
- No named user group configuration required
- Evaluation licenses do not enable POWERSHEET integration features
Specific evaluation license duration and renewal policies should be confirmed with Nextedy sales or the license management page in your Polarion instance.
Production License
Production licenses are permanent (non-expiring) licenses tied to a server user count. They enable all Risksheet features including POWERSHEET integration when a valid POWERSHEET production license is also present.Active User Assignment
User Group Configuration
Active (editing) users are managed through a dedicated Polarion user group:| Group Name | Product | Purpose |
|---|---|---|
nextedy_risksheet_users | Risksheet | Users who can edit Risksheet data |
nextedy_powersheet_users | POWERSHEET | Users who can edit POWERSHEET data (required when POWERSHEET is installed alongside Risksheet) |
“You have read-only access only. (Reviewer License)“
Access Control Matrix
| User Status | In User Group? | License Valid? | Access Level |
|---|---|---|---|
| Registered server user | Yes | Yes | Full edit access |
| Registered server user | No | Yes | Read-only access |
| Registered server user | Yes | No (expired/exceeded) | Read-only access |
| Registered server user | No | No | Read-only access |
| Not registered | N/A | N/A | No access (Polarion login required) |
POWERSHEET Integration Licensing
Risksheet automatically detects if POWERSHEET is installed and checks its license status. The interaction between the two products affects available features:| Risksheet License | POWERSHEET License | Behavior |
|---|---|---|
| Valid production | Valid production | Risksheet operates with enhanced metadata configuration, unlocking additional features |
| Valid production | Evaluation/trial | Risksheet operates in standard mode; POWERSHEET enhancements not enabled |
| Valid production | Not installed | Risksheet operates in standard mode |
| Valid production | Expired | Risksheet operates in standard mode; POWERSHEET features automatically disabled |
License changes are detected automatically. When a POWERSHEET license status changes (activated, expired, or upgraded from evaluation to production), Risksheet features adjust accordingly. The system maintains separate license managers for Risksheet and POWERSHEET, tracking server users and configured named users for both products independently.
User Group Alignment After Upgrades
When POWERSHEET is installed alongside Risksheet (particularly after upgrading to v25.11.0 or later), named users must be present in thenextedy_powersheet_users group for license alignment to work correctly. If only the nextedy_risksheet_users group exists, the license page may show 0 named users.
License Validation Parameters
The license validation system tracks the following metrics:| Parameter | Description |
|---|---|
| Server users | Total registered users on the Polarion server |
| Configured named users | Number of users in the nextedy_risksheet_users (or nextedy_powersheet_users) group |
| Configured concurrent users | See application for concurrent user licensing details |
| License expiration | Date when the license becomes invalid (evaluation licenses only) |
| Product version | Risksheet version string including build metadata |
Configuration Properties Related to Licensing
| Property | Type | Default | Description |
|---|---|---|---|
readonly | boolean | false | When the license restricts a user to read-only access, this flag is effectively true for that user’s session |
reviewer | boolean | false | Enables reviewer mode which restricts editing. Related to but distinct from license-based read-only access |
canAdmin | boolean | false | Indicates whether the current user has administrative privileges for configuration editing. Administrative access is checked via Polarion permissions, not the Risksheet license |
The
nextedy.risksheet.disable_admin_check=true system property bypasses the admin permission requirement. This is a server-level configuration, not a license setting.License Page Information
The Risksheet license page (accessible through Polarion administration) displays:- Current license type and expiration date (if applicable)
- Total server user count
- Number of configured named users from the user group
- License validity status
- Risksheet version information (
versionandshortVersion) - POWERSHEET license status (if installed)
Common Licensing Scenarios
Scenario: More Server Users Than Licensed
A Risksheet license for 100 server users is installed on a Polarion server with 150 registered accounts. Result: the license validation fails, and all users receive read-only access regardless of user group membership. Resolution: Either clean up inactive server user accounts to bring the count below the licensed limit, or upgrade the license to cover the actual server user count.Scenario: Named Users Cannot Edit
Seven users are in thenextedy_risksheet_users group but cannot save changes. The license shows the correct named user count.
Possible causes:
- The total server user count exceeds the licensed limit
- The document is in a historical revision (forces read-only)
- The
readonlyproperty is set totruein the document configuration - The
reviewerproperty is set totrue - A Polarion service restart is needed after group changes
Scenario: Post-Upgrade License Shows Zero Named Users
After upgrading Risksheet to v26.1.0 with POWERSHEET also installed, the license page shows 0 named users despite users being in thenextedy_risksheet_users group.
Resolution: Create a nextedy_powersheet_users group and add all users from nextedy_risksheet_users to it. The license alignment requires both groups when both products are installed.
See Also
- License Validation Errors — troubleshooting license issues
- Installation — initial Risksheet setup
- Polarion Version Compatibility — supported Polarion versions
- Configuration Properties Index — all configuration properties
Sources
Sources
KB ArticlesSupport TicketsSource Code
RisksheetProjectProperties.javarisksheet.jsonGetSetUtil.javaShowConfigurationCommand.tsPolarionAppConfigManager.java