Implementing a Hierarchical Security Model for Records Access in Dataverse Database | Microsoft Power Platform Functional Consultant Exam

Hierarchical Security Model Options for Record Access in Dataverse Database

Prev Question Next Question

Question

You implement a hierarchical security model for the records access in the Dataverse database.

What are the two options that you can choose from to establish the hierarchy security?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answers: A and E

Dataverse provides the following security models: business units, security roles, and hierarchical security.

Hierarchical security is based on who reports to whom.

According to this model, the user can have read and write access to the data that people who report to the user have access to.

And the reportees have access to the data of people who report to them, etc.

You need to enable the security model and select one of the options: Manager - this is based on the manager field on each user record that specifies the user's manager.

Position - this role is based on a position field that is assigned to the user.

You can access the Hierarchy Security options from the Power Platform admin center/Environments/Settings/Users + permissions menu.

[4 Save and Close Discard Hierarchy Security Configure hierarchy security, including enabling hierarchy modeling and selecting the model. You can also specify how deep the hierarchy goes, and specify the entities to exclude from a hierarchy. Turn on Hierarchy Modeling Enable Hierarchy Modeling @ Select Hierarchy Model @ Manager Hierarchy © Custom Position Hierarchy @ Configure Configure Hierarchy Depth 3 Select entities to exclude from the hierarchy Available Entities Excluded Entities Account Action Card Activity Ad Placement Add > AI Builder Dataset AI Builder Dataset File etemove AI Builder Dataset Record AI Builder Datasets Container AI Builder File

All other options are incorrect.

For more information about the Dataverse hierarchical security model, please visit the below URL:

Hierarchical security is a feature of Microsoft Dataverse that allows administrators to control access to records in a hierarchy. This feature ensures that users can only access records that are associated with their position in the organizational hierarchy.

There are two options available to establish hierarchical security in Dataverse:

  1. Position-based hierarchy: In position-based hierarchy, access to records is based on a user's position in the organizational hierarchy. The hierarchy is defined by positions, and users can access records that are associated with positions below their own. This means that a user can access records that are associated with their own position, as well as all the positions below it. For example, if a user is a manager, they can access records associated with their own position as well as all positions below them, such as team lead, supervisor, and individual contributor.

  2. Manager-based hierarchy: In manager-based hierarchy, access to records is based on a user's reporting structure. This means that a user can access records that are associated with their own position, as well as all the positions below them in their reporting structure. For example, if a user is a manager, they can access records associated with their own position, as well as all the positions below them in their reporting structure, such as team lead, supervisor, and individual contributor.

To implement hierarchical security in Dataverse, an administrator must define the organizational hierarchy and the access levels for each position or manager. This can be done using the Dataverse Security Model, which allows administrators to define roles, privileges, and access levels for different users and teams. Once the security model is defined, users can only access records that are associated with their position or reporting structure, based on the hierarchy security option chosen.

Prev Question Next Question