Microsoft Dynamics 365 Blog

A look into the world of Microsoft Dynamics.

How to Assign Security Roles in Dynamics 365

Posted by Alex Marzban on Oct 14, 2025 10:00:00 AM

Assign-Security-Roles-in-Dynamics-365

Quick Answer: Understanding and managing Dynamics 365 security roles is essential for maintaining data integrity and compliance. By defining clear Microsoft Dynamics security roles and permissions, organizations can control user access, protect sensitive data, and ensure that every team member operates with the right level of authorization.

Microsoft Dynamics 365 provides organizations with a suite of comprehensive services that help them meet the company's needs. IT administrators charged with providing access to various applications can set up Microsoft Dynamics 365 security roles designed to grant users specific data privileges. It’s possible to assign users to more than one security role depending on their position in an organization and the necessity for them to access specific information.

This approach to Dynamics 365 roles and responsibilities ensures users only see the information relevant to their duties, a crucial step toward reducing human error and improving governance across departments.

Why Is Role-Based Security Necessary?

Most business or finance applications use roles to enforce rules around how a user accesses and leverages the information. For example, administrators can create roles that provide view-only access to specific data. That may include things like customer representatives who need to validate info received from a caller, or data processing clerks needing to enter information may be placed in a role that grants permission to make data updates.   

Beyond operational efficiency, role-based security also strengthens compliance with industry regulations such as HIPAA or GDPR. With Microsoft Dynamics security roles, organizations can demonstrate granular control over who has access to what, which is critical for passing audits and protecting data privacy.

Organizations can set up security roles that allow applications to perform certain functions depending on the requestor. It’s possible to configure .NET applications to use security roles to authorize access depending on role membership or a principal’s identity.

The use of security roles helps organizations enact and reinforce security policies designed to keep confidential data from being viewed by anyone without a valid business need. Security roles also aid in the enforcement of corporate governance and compliance requirements.

In short, effective access controls in Dynamics go beyond convenience, becoming a cornerstone of digital trust and security in the modern enterprise.

Understanding Microsoft Dynamics 365 Security Role Features

Security roles define the way users access records in a company system. Assigning users to more than one role expands the perimeters of their access. All security roles consist of two forms of privileges:

  • Record-level privileges — Defines each of the tasks allowed by users assigned to a role.
  • Task-based privileges — Gives users individual permissions to perform tasks like Read, Create, Write, Assign, Share, and Delete.

Administrators can set up varying access levels for privileges granted to each security role. Understanding Dynamics 365 permissions is key for administrators. While record-level privileges determine what users can do, task-based privileges determine how they can do it. Together, they create a layered structure that allows for precision control without limiting business agility.

  • Global — Users gain access to every record in an organization.
  • Deep — Users gain access to all information in their business unit and those that fall beneath it in the company hierarchy.
  • Local — Users gain access to all data in their business unit.
  • Basic — Users gain access to information they own, or any data shared with the user or the team of which they are a member.
  • None — Users have no access to any information.

These access levels within Dynamics 365 security roles create a scalable permission hierarchy that mirrors your organization’s structure, from executives needing enterprise-wide visibility to clerks restricted to local data.

Users with specific permissions can override existing security roles for others. For example, someone who owns a record or has Share permission can make that information available to other team members or users in the organization, making this information viewable to even those who usually would not have sufficient levels of access. Once an admin grants those permissions, it’s not possible to remove them on an individual record basis. Any security role changes apply to all records of that type.

Administrators can grant permissions on a user or team basis. Individuals receive user privileges when they are directly assigned a role. They may also receive team privileges when they become a member of a given unit.

When designing Dynamics 365 integration architecture for security, admins should always document which users inherit privileges via teams or direct assignment. This not only simplifies audits but also minimizes risk in the event of staff turnover or role changes.

Assigning Security Roles in Dynamics 365

Administrators must set up an organizational structure designed to outline sensitive data protection while allowing collaboration among business units within an organization. Once that’s done, they can proceed with setting up and assigning security roles in Dynamics 365. Admins can also set up new security roles to align with business requirements or edit the permissions granted to current security roles.

Proper planning in Dynamics 365 user management can prevent excessive privilege overlap and reduce the risk of unauthorized access.

Assigning New Security Roles

Once an administrator has added new users to Dynamics 365, they can start assigning them to security roles.

  1. Go to Settings, then Security, then select Users.
  2. Look up and select the users needing to be assigned to a security role.
  3. Select More Commands (…), then Manage Roles. Admins will only see the roles available for a user’s business unit.
  4. Select the security role(s) for the user or users in the Manage User Roles dialog box, then select OK.

At this stage, it’s helpful to review each user’s assigned Microsoft Dynamics security roles to ensure consistency. For larger organizations, automated tools or scripts can streamline this process, especially when onboarding multiple new hires.

Creating a Security Role for Access Management

Only individuals assigned to the role of System Administrator, System Customizer, or another role with the same permissions may set up new security roles.

  1. Select Settings, then Security, then click on Security Roles.
  2. Look for the Actions toolbar, then click New.
  3. Start setting up the privileges for each tab. Admins can change each privilege's access level by clicking on the symbol until the required one appears. They can also accomplish the same function by selecting the privilege column heading or continually clicking the record type.
  4. Click Save and Close to complete the changes.

It’s also possible for admins to create new security roles by using the Copy Role function. For organizations scaling their operations, regularly reviewing and adjusting Dynamics 365 roles and responsibilities helps maintain clarity between departments. As teams evolve, so should their access structure.

  1. Go to Settings, then Security, then click on Security Roles.
  2. Select the Security role to be copied.
  3. Click Copy Role on the Actions toolbar.
  4. Enter the name for the new Role, then check the box titled indicating that the new security role should be opened once copying is complete.
  5. Click Ok to complete the changes.
  6. Navigate to each of the tabs for the new role and set the privileges.

One problem with the Copy Role function is that product updates can change security role privileges that make that new security role function improperly. One solution is to create a custom security role capable of dynamically changing after any updates.

  1. Go to Settings, then Security.
  2. Select Security Roles, then click New.
  3. Type in the role name, then click on the Business Management tab.
  4. Scroll down until you see the Entity list.
  5. Set the security role privileges as needed.

Maximize the Benefits of Security Roles in Dynamics 365

Working with Dynamics 365 cloud security features can be challenging for many organizations. Internet eBusiness Solutions (IES) helps organizations work through the complexities of Dynamics 365 security role management and implement an infrastructure that meets the business's needs.

When properly configured, security roles not only protect sensitive information but also enable seamless Dynamics 365 integration with other systems, allowing data to flow securely between applications. This balance between security and accessibility is what keeps modern enterprises both agile and compliant.

Learn more about how IES can become a vital partner in optimizing Microsoft Dynamics 365 integrations by setting up a consultation with one of our team members.  

Dynamics Security Role FAQs

How do I assign a security role to a user in Dynamics 365?
To assign a role, navigate to Settings → Security → Users. Select the user, then choose Manage Roles. From there, check the appropriate Dynamics 365 security roles you want to apply and select OK. Administrators can also assign roles in bulk, depending on permissions and organizational setup.
Can a user have more than one security role?
Yes. A single user can hold multiple Microsoft Dynamics security roles simultaneously. When that happens, the user inherits the highest level of access from any assigned role. This layered design allows flexibility for employees who perform multiple functions; for example, a user may need both Sales and Service privileges.
What are the different access levels in a Dynamics 365 security role?
Each Dynamics 365 security role defines access scope through tiered permissions:
  • Global: Access to all records in the organization
  • Deep: Access to records within their business unit and any child units
  • Local: Access to records only within their business unit
  • Basic: Access only to records the user owns or that are shared
  • None: No access to the selected record type
What is the 'Basic User' security role and why is it often required?

The Basic User role serves as the foundation for access in Dynamics 365. Every licensed user must have at least this role to log in successfully.

It grants minimal rights, enough to use the application interface and basic system functions, while additional Dynamics 365 permissions can be layered on through other roles.

What is the best practice for creating new security roles?
Start by copying an existing role and modifying it rather than building from scratch. This ensures compatibility with system updates and standard privileges. It’s also best to regularly review roles to prevent overlap, outdated permissions, or gaps that might compromise security or limit efficiency.
What is the 'Principle of Least Privilege' (PoLP) and how does it relate to security roles?

The Principle of Least Privilege dictates that users should receive only the minimum access necessary to perform their tasks.

In Dynamics 365 user management, applying PoLP helps reduce risk by minimizing exposure of sensitive data, especially for temporary, external, or junior staff.

What happens to a user's roles if their license is removed?
When a user’s Dynamics 365 license is revoked, their security roles remain assigned but become inactive. If the license is restored later, those roles automatically reapply, preserving prior access configurations without requiring manual reassignments.
Can I assign security roles to a team rather than individual users?

Yes, Dynamics 365 allows administrators to assign roles at the team level, simplifying management for large departments.

When a user joins the team, they automatically inherit the team’s roles and privileges, reducing the burden of manual configuration for each employee.

How do I create a custom security role in Dynamics 365?
You can create a custom role through Settings → Security → Security Roles → New. Then define privileges for entities like Accounts, Contacts, or Opportunities. For best results, document each role’s intended purpose and align privileges with internal policies and compliance frameworks.
Can I bulk-assign security roles to many users at once?
Yes. Administrators can use Advanced Settings → Security → Users and select multiple records, then click Manage Roles. Alternatively, PowerShell scripts or admin tools like Power Platform Admin Center streamline bulk assignments for enterprises managing hundreds of users.
What permissions do I need to assign security roles to others?

To assign or modify Dynamics 365 security roles, a user must have one of the following privileges:

  • System Administrator: full access to manage users and roles
  • System Customizer: ability to configure and modify roles
  • Delegated Admin (in partner environments): limited role assignment capability

These permissions ensure that only trusted administrators can alter access controls in Dynamics, maintaining compliance and protecting sensitive data.

 

New Call-to-action

Topics: azure