Skip main navigation

New offer! Get 30% off your first 2 months of Unlimited Monthly. Start your subscription for just £29.99 £19.99. New subscribers only. T&Cs apply

Find out more

Activity Summary

Microsoft Dynamics 365 and the Power Platform
16.9
Security ensures users have access to the data they need to do their jobs. It protects sensitive information and also helps streamline the user experience, allowing them to focus on the components they need. Keeping data and user action secure is often a priority for business. In our overview of security, we talked about the security model. The security model of the app is implemented through a combination of building blocks. They work together to form that security model. These building blocks include users, access teams, owning teams, business units, security roles, field-level security, hierarchical security options, and data loss prevention policies. Many of these we expanded on throughout this unit.
61.6
For your hands-on practise, you created a few new users that you will continue to build on throughout your security lessons. Though business units are primarily used to manage access and privileges, they also provide structure for grouping users and are often used to mimic an organisation’s departmental structure. Every environment has a root business unit that cannot be deleted or removed. A hierarchy of additional child business units can be created as needed. Business units, security roles, and users are linked together in a way that conforms to the role-based security model. While you didn’t do a hands-on practise for business units just yet, you will be doing that soon enough as you add and manage teams in a later practise.
104.7
Security role privileges are cumulative. So when a user has more than one role assigned, they get the end result of the most access possible through that combination of roles. By default, we learned that our new custom entities have no access for most users. System administrators and customizers will have that access. An important task associated with creating new entities is ensuring that security rules are modified to provide access to those entities. We learned that a user must have at least one security role assigned to be able to access the application. You had a chance to listen to George and I have a conversation about different potential security roles and strategies for roles for a few different use cases as well.
149.1
In your hands-on practise, you added and edited a role for all users. You then made a manager role to layer the access for targeted users or application managers. When it comes to teams, we learned about owning teams and access teams. We learned about teams that can own records much like a user, an owning team, and access teams, teams with no ownership rights but a group of users that need specific, short-term access to specified records. In your practise here, not only were we building out teams, but we brought together the business units and more security roles to layer on for our users.
184.5
The hierarchy security model extends other common data service security by allowing managers to access the records of their subordinates or do work on their behalf. It can be used in conjunction with all other existing security models. Two security models can be used for hierarchy– the manager hierarchy and the position hierarchy. With the manager hierarchy, a manager must be within the same business unit as the subordinate or in the parent business unit of the subordinate’s business unit in order to have that access to the subordinate data. The position hierarchy allows data access across business units.

In the last few steps, we explored Configure Hierarchy Security. Now, let’s summarize what we learned in this activity regarding Security.

To control data access, you must set up an organisational structure that both protects sensitive data and enables collaboration. You do this by setting up business units, security roles, and field security profiles.

A security role defines how different users, access different types of records. To control access to data, you can modify existing security roles, create new security roles, or change which security roles are assigned to each user. Each user can have multiple security roles.

The hierarchy security model is an extension to the existing security models that use business units, security roles, sharing, and teams. It can be used in conjunction with all other existing security models. The hierarchy security offers more granular access to records for an organization and helps to bring the maintenance costs down. For example, in complex scenarios, you can start with creating several business units and then add the hierarchy security.

Join the discussion

Security ensures that users have access to the data they need to do their jobs.
It protects sensitive information and also helps streamline the user experience, allowing them to focus on the components they need. Therefore, keeping data and user action secure is often a priority for the business.
Use the discussion area below to let us know your thoughts. Try to respond to at least one other post and once you’re happy with your contribution, click the Mark as complete button to check the Step off, then you can move to the next step which is a knowledge check on Security.
This article is from the free online

Dynamics 365: Using Power Platform Applications

Created by
FutureLearn - Learning For Life

Reach your personal and professional goals

Unlock access to hundreds of expert online courses and degrees from top universities and educators to gain accredited qualifications and professional CV-building certificates.

Join over 18 million learners to launch, switch or build upon your career, all at your own pace, across a wide range of topic areas.

Start Learning now