Microsoft Power Platform offers Dataverse as a unique integration platform for developing data-intensive applications. In order to secure data and ensure that it is accessed only by authorised persons, Microsoft Dataverse makes use of security roles. Each security role encapsulates an array of table permissions associated with various operations like Create, Read, Update, Delete, Append, Append To, Assign, and Share. But as an app maker, you may often find the need to add new table permissions to existing security roles to accommodate new features and functionalities.

In in the context of the exam “PL-100 Microsoft Power Platform App Maker”, understanding how to add table permissions to existing Dataverse security roles will come in handy. Here’s a step-by-step guide of how you can accomplish that.

Table of Contents

Understanding Microsoft Dataverse Security Roles

Dataverse applies a role-based access control model to ensure security, where every user role encapsulates a suite of predefined table permissions. This approach aims to ensure that users assigned to a role can only access the information they need to perform their tasks.

A security role in the Dataverse contains access levels that decide the depth of data access the user can possess for each feature, which can be categorized into five levels:

  1. Global: Allows access to all records.
  2. Deep: Allows access to all records in the business unit of the user and all the child business units.
  3. Local: Allows access to records in the user’s business unit.
  4. Basic: Allows access to records owned by the user or records shared with the user.
  5. None: Denies any access.

Let’s consider an example with a fictional company which recently integrated new features to their application and wants to grant all managers global access to a new table of their products.

Adding Table Permissions to Existing Security Roles

Here’s how you can perform these steps:

  1. Go to Power Apps portal, and then navigate to ‘Advanced settings’ > ‘Users + permissions’ > ‘Security Roles’. This action will display the list of all existing security roles.
  2. Choose the security role to which you want to add the table permission – in our case, “manager”.
  3. Click on ‘Custom Entities’ and scroll down to find the table you created – for instance, products.
  4. For the ‘product’ row, click on ‘Read’. Toggle the slider to ‘Global’. This grants the Manager role global read access to the ‘product’ table.

And just like that, you have successfully added new table permissions to an existing Dataverse security role.

Conclusion

Adding table permissions to existing security roles in Dataverse ensures that the right individuals have the correct level of data access in accordance with their user roles. The process is straightforward and can be accomplished directly from the Power Apps portal. Whether these permissions pertain to global or basic levels of data access, modifying them ensures that new features and tables incorporated in the application’s data model are accounted for in the overall security model.

Remember to always verify and test the applied changes to ensure the accessibility and data security of your application. Understanding this process can help you secure good grades in PL-100 Microsoft Power Platform App Maker exam.

Practice Test

True or False: In Microsoft Power Platform, you can modify the existing Dataverse security roles to add table permissions.

  • True
  • False

Answer: True

Explanation: Dataverse uses a role-based security model which allows modification of roles by adding table permissions.

What accesses are included in the table permissions of Microsoft Dataverse?

  • A. Append
  • B. Write
  • C. Read
  • D. Create
  • E. Delete

Answer: A, B, C, D, E

Explanation: Dataverse table permissions include Create, Read, Write, Append, and Delete capabilities.

When you add a new table in Dataverse, what permission does it automatically get?

  • A. Create
  • B. Read
  • C. Write
  • D. It doesn’t automatically get any of these permissions

Answer: D. It doesn’t automatically get any of these permissions

Explanation: When you add a new table in Dataverse, no permissions are automatically granted. You need to assign them manually.

True or False: Only system administrators or system customizers can modify the existing security roles.

  • True
  • False

Answer: True

Explanation: Only system administrators or system customizers are capable of modifying the existing security roles in Microsoft Power Platform.

Can you modify the out-of-box security roles in Microsoft Power Platform?

  • Yes
  • No

Answer: No, you can’t modify out-of-box security roles, but they can be cloned.

Explanation: Out-of-box security roles provide a set of default permissions and cannot be modified, but they can be cloned to create new custom roles with modified permissions.

True or False: Table ownership in Dataverse can be defined at three levels—organization, business unit, user or team.

  • True
  • False

Answer: True

Explanation: In Microsoft’s Power Platform, table ownership in Dataverse can indeed be set at three different levels: organization, business unit, user or team.

True or False: A user can be assigned multiple security roles in Dataverse.

  • True
  • False

Answer: True

Explanation: Yes, a user can be assigned more than one security role in Dataverse to have more granular control over access.

Which security roles include general administration permissions on tables in Dataverse?

  • A. System Administrator
  • B. System Customizer
  • C. Both of the above
  • D. None of the above

Answer: C. Both of the above

Explanation: Both the System Administrator and System Customizer roles include general administration permissions on Dataverse tables.

True or False: The more restrictive permission set becomes effective when a user is assigned multiple security roles.

  • True
  • False

Answer: True

Explanation: When a user is assigned multiple security roles in DataVerse, the more restrictive permission set among those assigned becomes effective.

What does append access imply in Dataverse table permissions?

  • A. The ability to add content to existing entries
  • B. The ability to remove content from existing entries
  • C. The ability to view content in existing entries
  • D. The ability to edit existing content

Answer: A. The ability to add content to existing entries

Explanation: Append access in Dataverse table permissions refers to the right to append (or add) content to an existing entry in the table.

True or False: You can create a new security role by cloning an existing one and then modify it.

  • True
  • False

Answer: True

Explanation: Cloning an existing security role is indeed one of the ways you can create a new custom role, which you can then modify according to your needs.

True or False: Every table in Microsoft Dataverse needs to have an owner.

  • True
  • False

Answer: True

Explanation: Every table in Microsoft Dataverse must have an owner, which can be an organization, business unit, user, or a team.

In Microsoft Dataverse, who can assign security roles to users?

  • A. System administrators
  • B. Users themselves
  • C. Both of the above
  • D. None of the above

Answer: A. System administrators

Explanation: Only system administrators are capable of assigning security roles to users in Microsoft Dataverse.

How many tables can a single security role have access to in Microsoft Dataverse?

  • A. 1
  • B. 5
  • C. 10
  • D. It can have access to any number of tables

Answer: D. It can have access to any number of tables

Explanation: A single security role in Microsoft Dataverse can have access to any number of tables depending on the permissions given.

True or False: The “Delete” permission in a Dataverse table will allow the user to delete only the entries they have created.

  • True
  • False

Answer: False

Explanation: The “Delete” permission in a Dataverse table will allow the user to delete any entries in the table, not just the ones they created, depending on the level of ownership set in the security role.

Interview Questions

What is the primary purpose of adding table permissions to existing Dataverse security roles?

The primary purpose is to control the level of access that a role has to a table and its records within the Dataverse database. It helps in maintaining data security and integrity.

What are the different levels of table permissions that can be assigned to a security role in Dataverse?

The different levels of table permissions are None, User, Business Unit, Parent: Child Business Unit, Organization, and Custom.

Which permission level allows a user to manage records owned by their business unit in Dataverse?

The “Business Unit” permission level allows a user to manage records owned by their business unit in Dataverse.

What happens when you add ‘Read’ table permission to a security role in Dataverse?

When you add ‘Read’ table permission to a security role in Dataverse, users with that role are granted the ability to view records of the assigned table.

Which permission level allows a user to manage records across the entire organization in Dataverse?

The “Organization” permission level allows a user to manage records across the entire organization in Dataverse.

Can you remove table permissions from an existing security role in Dataverse?

Yes, table permissions can be removed from an existing security role in Dataverse.

What does the ‘Write’ permission allow a user to do in a Dataverse table?

The ‘Write’ permission allows a user to make changes or updates to records in a Dataverse table.

Can you assign multiple table permissions to a single role in Dataverse?

Yes, multiple table permissions can be assigned to a single role in Dataverse.

What is the ‘Delete’ permission in Dataverse?

The ‘Delete’ permission grants a user the ability to remove records from a table in Dataverse.

What is the maximum number of security roles that a user can have assigned in Dataverse?

There isn’t a specific limit to the number of security roles that can be assigned to a user in Dataverse.

Can you edit the permissions of a system-defined security role in Dataverse?

No, you cannot edit the permissions of a system-defined security role in Dataverse. You can only create a new one or copy and edit an existing custom role.

What does the ‘Append’ permission do in a Dataverse table?

The ‘Append’ permission allows a user to attach or associate another record with the current record in a Dataverse table.

Can table permissions be assigned to a user directly in Dataverse?

No, table permissions cannot be assigned to a user directly. They are assigned through a security role which is then assigned to the user.

What permission level in a Dataverse table doesn’t give any access to a user?

The “None” permission level doesn’t give any access to a user on a Dataverse table.

What does the ‘Assign’ permission allow you to do in a Dataverse table?

The ‘Assign’ permission grants a user the ability to assign the ownership of a record to another user in a Dataverse table.

Leave a Reply

Your email address will not be published. Required fields are marked *