License Validation Quick Reference
Use the following decision table to identify your specific issue and jump to the appropriate section:Server User Count Discrepancy
Problem
The license page reports a much higher server user count than the number of active Polarion license holders. For example, you have 50 Polarion ALM licenses but the Risksheet license page shows 203 server users.Cause
Risksheet counts all registered users on the Polarion server as server users, regardless of their Polarion license type. This includes:- Users with active ALM, QA, or ITAR licenses
- Users with expired or deactivated Polarion licenses
- Service accounts and integration users
- Users who were once active but no longer use the system
Resolution
You have two options: Option A: Clean up inactive server users- Navigate to Administration > User Management in Polarion
- Identify users who no longer need access to the system
- Remove or deactivate unused accounts
- Return to the Risksheet license page and verify the reduced server user count
Named Users Show as Zero
Problem
The Risksheet license page displays 0 configured named users, even though you have created thenextedy_risksheet_users group and added users to it.
Cause
This can occur for several reasons:- The user group name is misspelled (must be exactly
nextedy_risksheet_users) - Users were added by username instead of email address
- Polarion services have not been restarted since the group was created
- The group exists but contains no members
Resolution
Step 1: Verify the group name in Administration > User Management > Groups. The group name must be exactlynextedy_risksheet_users (case-sensitive, with underscores).
Step 2: Open the group and verify that user entries are present. Users should be identified by their Polarion user IDs.
Step 3: Restart Polarion services:
Reviewer License Message
Problem
Users see the error message:Cause
This message appears when:- The user is not a member of the
nextedy_risksheet_usersgroup (they receive Connect/read-only access) - The
reviewerproperty is set totruein the document’s sheet configuration - The license has expired or is in an invalid state
Resolution
If the user should have edit access:- Navigate to Administration > User Management > Groups
- Open the
nextedy_risksheet_usersgroup - Add the user’s Polarion user ID to the group
- Restart Polarion services if the change is not immediately reflected
- Ask the user to refresh the Risksheet page
reviewer property in the sheet configuration:
reviewer to false (or removing the property, as false is the default) restores standard editing capability for licensed users.
Post-Upgrade License Alignment
Problem
After upgrading Risksheet to version 25.11.0 or later, the license page shows 0 named users and all sheets are in read-only mode, even though thenextedy_risksheet_users group is correctly configured.
Cause
Starting with version 25.11.0, when Powersheet is also installed on the server, the license system requires anextedy_powersheet_users group for proper alignment. The old nextedy_risksheet_users group alone is no longer sufficient when Powersheet is present.
Resolution
Step 1: Create a new Polarion user group namednextedy_powersheet_users
Step 2: Add all users from the nextedy_risksheet_users group to the new nextedy_powersheet_users group
Step 3: Restart Polarion services
Step 4: Verify the license page now shows the correct named user count
Empty License Page
Problem
The Risksheet License page in Polarion administration appears completely empty with no content, no fields, and no status information.Cause
The Polarion plugin cache directory ([POLARION_INSTALL]/data/workspace/.config) was not deleted after installing or updating Risksheet. This cached data prevents Polarion from loading the new administration pages.
Resolution
Step 1: Stop the Polarion service Step 2: Delete the configuration cache directory:.config directory, not just its contents.
Step 3: Start the Polarion service
Step 4: Navigate to Administration > Nextedy Risksheet > License and verify the page now loads with license information
The
.config directory must be deleted every time you install or update Risksheet. This is not only a first-time installation step. Forgetting to delete the cache after an update will cause the Setup and License pages to display stale or empty content.License Not Recognizing Group Changes
Problem
After adding users to thenextedy_risksheet_users group, the Risksheet license page still shows the old named user count. Users who were just added still see read-only access.
Cause
License validation caches group membership data. Changes to user groups are not always immediately reflected without a service restart.Resolution
Step 1: Verify the group membership is correct in Administration > User Management > Groups Step 2: Restart Polarion services to force license revalidation Step 3: After restart, check the license page for updated counts Step 4: Ask affected users to clear their browser cache and reload the Risksheet pagePowersheet License Interaction
When Powersheet is installed alongside Risksheet, the licensing system manages both products through separate license managers. Key points to verify:
When a valid Powersheet production license exists, Risksheet automatically unlocks additional features. This detection is automatic and requires no manual configuration. Evaluation or trial Powersheet licenses do not enable these enhancements.
Verification
After resolving your license issue, you should now see:- The license page displaying the correct server user count and named user count
- Licensed users able to edit cells and save changes in the Risksheet grid
- The
readonlyindicator absent from the status bar for named users - Non-named users correctly receiving read-only (Connect) access