Quick Diagnosis
Access denied errors can occur at multiple levels:| Error Location | Likely Cause | Quick Fix |
|---|---|---|
| Risksheet widget not visible | Topic not in view | Switch to view including Risksheet topic |
| Template selection empty | No access to template project | Grant project access to user |
| Document opens but read-only | Missing active user group | Add user to nextedy_powersheet_users |
| ”Access Denied” on load | Insufficient document permissions | Check Polarion document permissions |
Check Polarion View Configuration
Risksheet visibility is controlled by Polarion view settings:- In Polarion, check your current view (top-right dropdown)
- Navigate to Administration > Topics for your project
- Select the view you’re using (e.g., “Default”, “Custom View”)
- Verify Risksheet topic is checked for that view
- If unchecked, enable the Risksheet topic and save
Verify User Group Membership
Nextedy RISKSHEET requires users to be in specific Polarion groups: For Version 26.1.0 and Later:- Navigate to Administration > Users and Groups
- Find group
nextedy_powersheet_users - Verify your user is listed as a member
- If missing, add your user to the group
- Navigate to Administration > Users and Groups
- Find group
nextedy_risksheet_users - Verify your user is listed as a member
- If missing, add your user to the group
Check Template Project Access
Template visibility requires project-level permissions:- Identify which project contains your Risksheet templates
- Navigate to that project in Polarion
- Go to Administration > Permissions
- Check that your user role has at least Read access
- If missing, request access from a project administrator
Verify Document Permissions
Document-level permissions may restrict access:- Open the Polarion document in LiveDoc (not Risksheet)
- Check the document’s Permissions tab
- Verify your user role has appropriate permissions:
- Read - View the document
- Modify - Edit work items
- Create - Add new work items
- Request permission updates from document owner if needed
Check License Status
Active user licenses affect editing capabilities:- Navigate to Administration > Nextedy RISKSHEET > License
- Check Server Users count vs. Licensed Users
- Verify Active Users count (users in active user group)
- Ensure you’re within license limits
Handle View Redirection Issues
If accessing Risksheet redirects you to the project home page:- Switch to a different Polarion view using the view dropdown
- Select a view that includes the Risksheet topic
- Try accessing the Risksheet document again
- If the issue persists, contact your administrator to add Risksheet to your default view
Resolve Post-Upgrade Access Issues
After upgrading to version 26.1.0:- Create the
nextedy_powersheet_usersgroup if it doesn’t exist - Migrate all users from
nextedy_risksheet_usersto the new group:- Go to Administration > Users and Groups
- Select
nextedy_risksheet_usersgroup - Copy the member list
- Add all members to
nextedy_powersheet_users
- Verify users can access Risksheet after migration
Handle Database Maintenance Windows
Temporary access denial during database operations:- Database reindexing can make Risksheet temporarily inaccessible
- Expected duration: 15 minutes to several hours depending on data size
- Action: Wait for maintenance to complete before contacting support
- Verification: Check Polarion system status or contact administrator
If Risksheet becomes inaccessible after working normally, check with your Polarion administrator about ongoing database maintenance operations before troubleshooting permissions.
Check Admin Permission Bypass
For development or testing environments:- Verify if
nextedy.risksheet.disable_admin_check=trueis set in Polarion configuration - This setting bypasses admin permission requirements (use only in non-production)
- For production, ensure users have proper admin rights if needed
Verification
After resolving access issues, you should see:- Risksheet topic visible in your current Polarion view
- Templates appear in document creation wizard
- Documents open without “Access Denied” errors
- Edit operations save successfully
- User appears in correct active user group
See Also
- User Roles and Permissions - Understanding permission model
- Configure Permissions - Setting up user permissions
- Understand License Types - License requirements
- Manage User Groups - Active user group setup
- Permission-Based Field Restrictions - Field-level access issues