Risk-to-Control OOTB create ACL passes, but reference fields fail create access
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi,
On the OOTB sn_risk_m2m_risk_control table, users with both sn_risk.manager and sn_compliance.manager cannot add an existing Risk to a Control.
The table-level create ACL passes:sn_risk_m2m_risk_control/create = true
However, the reference field checks fail:
sn_risk_m2m_risk_control.sn_compliance_control/create = false
sn_risk_m2m_risk_control.sn_risk_risk/create = false
The OOTB table-level write ACL requires the nobody role, and both fields are read-only on a new relationship record. As a result, Risk Workspace allows Risk selection, but no relationship record is created.
What is the purpose of this OOTB security behavior?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hello @serajose ,
Refer this might help :
control adding not wokring in risk record
If my response helped mark as helpful and accept the solution.
