Assigning Security Role Privileges for Custom Dataverse Tables

Correct Answers: B and E

Dataverse provides a flexible and robust security system.

Environment security is based on business units, security roles, and filed security profiles.

The Business unit security model is the basis for the Dataverse security.

The model controls access to the data using security roles, teams, and users.

By linking all of them together, you are getting a role-based security model.

By default, the Organization is a top-level of a business unit hierarchy.

Each business unit has a default team.

You cannot change or delete the default team.

You must assign every user to only one business unit.

The security role defines how a user accesses different types of records.

Each role has two privileges: the record-level and the task-based.

The record-level privileges are tasks that users can apply to the table and table records (Number 1)

And the task-based privilege grants users access to specific tasks, like assign a manager to the user or approve knowledge articles (Number 2)

There are eight record-level privileges (tasks): Create, Read, Write, Delete, Append, Append To, Assign, and Share (Number 4)

For the standard custom tables, the Dataverse provides two types of ownership: User or Team.

Organization.

After the table is created, you cannot change the table ownership.

Organization-owned tables do not have Assign or Share privileges because both tasks require an owner to assign to or share with.

There are no record owners for organization-owned tables.

There is a key table on the bottom of the security screen that defines the privileges' access level.

The access level can be from None - access is not allowed to the Organization - a user has access to all the organization's records (Number 3)

This type of granularity works for record-level access.

For the task-based privileges, the access has only two settings: None and Organization.

All other options are incorrect.

For more information about the Dataverse security roles, please visit the below URLs:

In Microsoft Dataverse, security roles are used to control access to the tables and data. When you create a custom Dataverse table, you need to assign a security role for the table's access.

The following are the privileges that can be assigned to a security role for a custom Dataverse table:

A. Row-level: This privilege enables the users to access only specific rows or records of a table. For example, a user can be allowed to view and edit only the records that belong to a particular department.

B. Record-level: This privilege enables the users to access only specific records of a table. For example, a user can be allowed to view and edit only the records that they have created.

C. Unit-based: This privilege enables the users to access a specific unit of a table. For example, a user can be allowed to view and edit only the records that belong to a specific location.

D. Entity-level: This privilege enables the users to access all the records of a table. For example, a user can be allowed to view and edit all the records of a table.

E. Task-based: This privilege enables the users to perform specific tasks on a table. For example, a user can be allowed to create, update or delete records of a table.

In summary, all of the privileges listed (A, B, C, D, and E) can be assigned to a security role for a custom Dataverse table. The choice of privilege(s) to assign to a security role depends on the specific access requirements of the users.