BeyondERP.Newsletter
Menu

Setup step on the Security configuration page · System administration

Set up Security configuration

Use this page to build or adjust security objects, for example to give a role access to a custom data entity.

Business process
Administer system features
Menu item
SysSecConfiguration
Data entity
None for this page's own settings
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page where administrators create and change security roles, duties and privileges, and then publish the changes.
What you do hereUse this page to build or adjust security objects, for example to give a role access to a custom data entity.
ExampleFor example, an administrator duplicates a role with a license filter such as Team Members, so the copy keeps only the duties and privileges that license covers.
Security configuration 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 › Security configuration
Set up firstSegregation of duties rules Microsoft Learn
Used next byAssign users to roles Microsoft Learn
Related pagesSegregation of duties rules Microsoft Learn
In this process Set up Organization workflows · Set up Server configuration
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.

Step by step, with screenshots

Set up Security configuration1 screen

Use this page to build or adjust security objects, for example to give a role access to a custom data entity.

  1. Screen 1

    Review the security objects of a role

    Go to System administration > Security > Security configuration

    1. Select a role on the Roles tab
    2. Review its AOT name and the duties, privileges and tables it references
    3. Use Create new or Duplicate when you need to build a new security object
    Review the security objects of a role (zoomed on the outlined fields)
    Show the full screenReview the security objects of a role
    page title tab to open what to set or check

Steps from Microsoft

  1. Go to System administration > Security > Security configuration.
  2. On the Privileges tab, select Create new, enter a name, and select OK.
  3. With the new privilege selected, select Entities, then Add references, and pick the entity and access level.
  4. Select Duties, then Add references, and add the privilege to the right duty.
  5. Open the Unpublished objects tab.
  6. Select Publish all.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Roles / Duties / Privileges tabsThe three levels of the security model: a role holds duties, a duty holds privileges, a privilege grants access to menu items, tables and fields.Microsoft Learn
Unpublished objectsChanges that are saved but not yet active; Publish all makes them active.Microsoft Learn
Duplicate with license filterCopies a role and keeps only what the chosen license covers.Microsoft Learn Team Members

Common errors and fixes

MessageWhat to do
A duty can't be added to a roleIt conflicts with a segregation of duties rule; roles can't hold conflicting duties. Change the role design or the rule. Microsoft Learn
A custom role is missing after a database refresh from productionExport the customizations from the source with the security metadata customization entities and import them, privileges first, then duties, then roles. Microsoft Learn

Test checklist

  1. Create or change a role and publish the change.
  2. Assign the role to a test user on Assign users to roles.
  3. Sign in as the test user and check that the entry points granted by the role's privileges open with the expected access (read, update, create, delete).
  4. If the role came from Security governance, run Synchronize on Security process role maintain and check that the change appears there.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Security configurationBuild position-based roles from duties and privileges through Security governance, and run Synchronize after any change made directly in Security configurationSecurity governance builds roles from the business process hierarchy, which helps optimize license cost and data security. Roles, duties and privileges edited directly in Security configuration no longer match Security governance until you synchronize.How are custom roles moved from test to production?Adding or removing entry points here on objects that were created in Security governance, then forgetting to synchronize, so the two views of the same role differ.Test: Custom security moves cleanly

Feature management and licence

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

Microsoft Learn

Solution architect

5Design impact

Shared or per companyShared: roles, duties and privileges are defined once for the environment. Microsoft Learn
Can it be undoneHard to reverse: The process hierarchy behind the roles can be changed later, but Learn notes that changing it takes a significant amount of work.
If you change it laterIf you edit here a role, duty or privilege that came from Security governance, it no longer matches the version on the Security governance pages. Microsoft Learn
Technical architect

6Technical

Menu itemSysSecConfiguration Checked in Dynamics 365
FormSysSecConfiguration Checked in Dynamics 365
Data entitiesSystemSecurityPrivilegeCustomizationsEntitySecurity privilege metadata customizations entity (only privileges added or changed on this page) SystemSecurityDutyCustomizationsEntitySecurity duty metadata customizations entity (only duties added or changed on this page) SystemSecurityRoleCustomizationsEntitySecurity role metadata customizations entity (only roles added or changed on this page)
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 pageSegregation of dutiesDataChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SysSecConfiguration
Data migrationSystemSecurityPrivilegeCustomizationsEntity (Security privilege metadata customizations): load first.SystemSecurityDutyCustomizationsEntity (Security duty metadata customizations): load second.SystemSecurityRoleCustomizationsEntity (Security role metadata customizations): load last.Load order: Export the three customization entities in one data package and keep the sequence privileges, then duties, then roles; import the package in the target and publish.Load first: Standard security objects shipped with the versionMicrosoft Learn
Everyone

8Sources

To cite this step: SA-SEC-020, Set up Security configuration. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-SEC-020