Prerequisites
Before overriding template configuration:- Ensure you have project administrator permissions (or
nextedy.risksheet.disable_admin_check=trueis set) - Open the RISKSHEET document you want to customize
- Verify the document currently uses a template (visible in the Configuration Editor header)
Switch to Document-Specific Configuration
Using the Configuration Editor (Recommended)
- Open your RISKSHEET document
- Navigate to Menu > Configuration > Edit Risksheet Configuration
- In the configuration editor (opens in new tab since v25.5.0), look for the Override Template button in the toolbar
- Click Override Template to switch to document-specific configuration mode
- Verify the editor header now shows “Document Configuration” instead of “Template: [template-name]”
- Make your customizations in the editor
- Click Save to apply changes
Manual Override via Attachment
Alternatively, attach arisksheet.json file directly to the document:
- Open the document in Polarion LiveDoc editor
- Add a new attachment named exactly
risksheet.json - Upload your custom configuration file
- Save the document
- Refresh the RISKSHEET view
risksheet.json attachment automatically overrides template configuration.
Configuration Loading Priority
risksheet.json exists as a document attachment, the system stops searching and uses that configuration exclusively.
Revert to Template Configuration
To restore template synchronization:- Open the Configuration Editor for your document
- Click Revert to Template (or similar option depending on version)
- Confirm the action
- Open the document in Polarion LiveDoc
- Delete the
risksheet.jsonattachment - Save the document
- Refresh the RISKSHEET view
Common Use Cases
Exclude Specific Documents from Template Updates
Scenario: You have 10 RISKSHEET documents using a global template, but one document needs project-specific risk matrices that shouldn’t change when the template is updated. Solution: Override the template for that single document. The other 9 documents continue to inherit template changes.Test Configuration Changes Before Template Rollout
Scenario: You want to test new column configurations before deploying to all documents. Solution:- Override template on a test document
- Test your configuration changes
- Once validated, apply changes to the global template
- Optionally revert the test document back to template mode
Multi-Project Environments with Project-Specific Customization
Scenario: You have a central template but need project-specific customizations (e.g., different task types, link roles, or workflows). Solution: Use template override for documents requiring project-specific settings. See Configure Multi-Project Setup for advanced patterns.Verification
After overriding template configuration, verify the change:- Open the Configuration Editor
- Check the header shows “Document Configuration” (not “Template: …”)
- The
templateNamefield in the editor should be empty or show only the document name - Make a small configuration change (e.g., adjust a column width) and save
- Refresh the RISKSHEET view — your changes should appear immediately
- Verify changes to the global template do not affect this document
Check Configuration Source in DevTools
Check Configuration Source in DevTools
You can verify configuration source by checking
window.risksheet.fromTemplate in browser DevTools console:true= loaded from templatefalse= loaded from document attachment
See Also
- Find Configuration Files — Understand the configuration hierarchy
- Set Up Global Templates — Create shared templates across projects
- Configure Template Paths — Use templates from other projects
- Use the Configuration Editor — Edit configuration through the UI
- Configuration Hierarchy — Understand how configuration inheritance works
Sources
Sources
KB ArticlesSupport TicketsSource Code
DocumentConfigProvider.javaAppConfig.tsRisksheetViewServlet.javaOpenHelpCommand.tsPdfExportConfigurationService.java