- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2025 10:18 AM
After installing DPR, I found it difficult to know what Roles to assign to what Personas.
The documentation mentions Personas in https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/digital-product-rel...
- Release manager
- Release coordinator or Program manager
- Product manager
- Engineering lead
However, the documentation doesn't says what roles these personas should be assigned as per the new DPR roles created after installation:
- sn_dpr_model.product_enhancement_read - Read role for Product Enhancement table.
- sn_dpr_model.product_feature_create - Create role on Product Feature table in Digital Product Release Workspace
- sn_dpr_model.product_feature_delete - Delete Role for Product Feature table
- sn_dpr_model.product_feature_read - Read role for Product Feature table in Digital Product Release Workspace
- sn_dpr_model.product_feature_write
- sn_dpr_model.product_manager - Digital Product Manager
- sn_dpr_model.release_admin - Digital Product Release Admin
- sn_dpr_model.release_coordinator - Digital Product Release Coordinator
- sn_dpr_model.release_user Digital Product Release User
- sn_dpr_workspace.workspace_user Digital Product Release Workspace User
Can anybody provide some insights here please.
Thanks, Thomas
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2025 10:34 AM
ServiceNow leave it open as it's org dependent. Have you run through the DPR Process Workshop presentation where it calls out the decision points around roles? You want to focus on the following
- sn_dpr_model.product_manager - Manages products, scope, and features in upcoming versions. (e.g Product Manager, Product Owner)
- sn_dpr_model.release_admin - Define approval definitions, release policies, release templates. (e.g SME if following a citizen development model)
- sn_dpr_model.release_coordinator - Approves scope, provides status updates, handles communications (e.g Engagement Manager, Business Analyst)
- sn_dpr_model.release_user - Any other individual that contributes (e.g Engineers, Business Analysts, Quality Assurance)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
What is the approach for a Read Only role? I don't see any read only for DPR listed in the information above.
How do you give auditors or risk partners or others who do not run a release access to view the records details?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi @billgoodall ,
You can assign the sn_dpr_model.release_user role. This is a read-only role, so users can view releases, products, etc., but they won’t have write access and therefore cannot make any edits.
