BeyondERP.Newsletter
Menu

Inquiry page · System administration

Segregation of duties conflicts

A list page that shows the user role assignments that were allowed even though they broke a segregation of duties rule.

Used by
Security administrator
Business process
Administer system features
Menu item
SysSecSegregationOfDutiesConflictsAll
Main table
SecuritySegregationOfDutiesConflict
Data entity
SystemSegregationOfDutiesConflictEntity
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA list page that shows the user role assignments that were allowed even though they broke a segregation of duties rule.
What you do hereUse this page to review overridden role assignments and the reasons that were recorded for them.
ExampleFor example, an auditor asks why one BEAT user holds both Accounts payable clerk and Purchasing agent; the page shows the allowed assignment with its Reason for override.
Segregation of duties conflicts page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processAdminister system features
Menu pathSystem administration › Security › Segregation of duties › Segregation of duties conflicts
Set up firstSegregation of duties unresolved conflicts Microsoft Learn
Related pagesSegregation of duties rules Microsoft Learn
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Review overridden segregation of duties conflicts

Use the page at each access review to check every override still has a valid reason.

Steps from Microsoft

  1. Go to System administration > Security > Segregation of duties > Segregation of duties conflicts.
  2. Type in the Filter box to find a conflict.
  3. Check the Rule, SOD Status, User ID, Existing role, New role, Assignment mode and Resolution columns.
  4. Select a row, then select Edit to open it.
  5. Select Deny assignment or Allow assignment on the Action Pane.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Reason for overrideWhy the conflicting role assignment was allowed.Microsoft Learn Temporary cover during month-end, approved by the finance manager
RuleThe segregation of duties rule the assignment breaks.Microsoft Learn
User IDThe user who holds both roles.Checked in Dynamics 365
Existing role / New roleThe role the user had and the role that caused the conflict.Checked in Dynamics 365

Common errors and fixes

MessageWhat to do
An expected conflict isn't listedUsers who get roles through Active Directory domain groups aren't checked; only direct assignments are. Microsoft Learn

Test checklist

  1. Allow a conflicting assignment with a reason on Segregation of duties unresolved conflicts.
  2. Open this page and find the assignment with its reason.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Review overridden segregation of duties conflictsReview the list with internal control each quarter and remove role assignments whose reason no longer appliesEvery override is a known control gap; the reason recorded here is the evidence auditors ask for.How often are overrides reviewed?Writing a vague Reason for override, such as 'needed', which doesn't stand up in an audit.Test: An override appears with its reason

Feature management and licence

Licence or add-inOn this system the page opens for Security administrator. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyShared: conflicts are logged for the whole environment. Microsoft Learn
Can it be undoneReversible: An allowed assignment can be withdrawn by removing the user from the role on Assign users to roles. Microsoft Learn
If you change it laterEvery role assignment that was allowed despite a conflict is listed here with its reason, which is what auditors review. Microsoft Learn
Technical architect

6Technical

Menu itemSysSecSegregationOfDutiesConflictsAll Checked in Dynamics 365
FormSysSecSegregationOfDutiesConflict Checked in Dynamics 365
TableSecuritySegregationOfDutiesConflictShown as “Segregation of duties conflict” in Record infoChecked in Dynamics 365
Data entitiesSystemSegregationOfDutiesConflictEntitySecurity segregation of duties conflict Checked in Dynamics 365RetailTrialSystemSecurityUserRoleAssociationEntityRetail trial user role association (the retail trial variant of the user role associations; Open in Excel offers it on this page) Checked in Dynamics 365SystemSecurityUserRoleAssociationEntitySecurity user role association (only the user role assignments behind each conflict; Open in Excel offers it on this page) Checked in Dynamics 365SystemSecurityUserRoleEntitySystem security user role organization (only the organization limits of the user roles behind each conflict; Open in Excel offers it on this page) Checked in Dynamics 365
Who can open itPrivilegesMaintain the segregation of duties rules SysSecSegregationOfDutiesMaintainDutiesMaintain security settings SysSecSecurityMaintain
1 security roleSecurity administrator SysSecSecurityAdministrator
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itSecurity administrator SysSecSecurityAdministratorGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SysSecSegregationOfDutiesConflictsAll
Integrate withSystemSegregationOfDutiesConflictEntity data entity Checked in Dynamics 365
Data migrationSystemSegregationOfDutiesConflictEntity (Security segregation of duties conflict): shared by all companies; not in Microsoft's default templates.Load order: Conflicts are logged in each environment. Move them only to keep an audit trail; load after users and roles.Load first: User information, Security user role associationChecked in Dynamics 365
Everyone

8Sources