What Record-Level Privileges the Organization-Owned Tables Lack?

Correct Answers: B and E

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

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

Each role consists of privileges: record-level and task-based.

The record-level privileges are tasks that users can apply to the table records.

There are eight privileges (tasks): Create, Read, Write, Delete, Append, Append To, Assign, and Share.

In general, standard Dataverse tables have four types of table ownership: User or Team.

Organization.

Business-owned.

None.

The Dataverse database provides only two types of ownership for the standard custom tables: 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.

All other options are incorrect.

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

In Microsoft Power Platform, record-level privileges determine what actions a user can perform on individual records within a table. These privileges are usually controlled by security roles that are assigned to users.

Organizational-owned tables are tables that are owned by the organization and are used to store important data such as accounts, contacts, and leads. These tables are created by default when the organization is set up in Power Platform.

Out of the five privileges listed in the question, the record-level privilege that organization-owned tables do not have is the "Assign" privilege. This privilege allows a user to reassign a record to another user or team.

The other privileges mentioned are available on organization-owned tables:

• Create: Allows a user to create a new record in the table.
• Write: Allows a user to update an existing record in the table.
• Append: Allows a user to associate an existing record from another table to a record in the current table.
• Share: Allows a user to share a record with another user or team.

It's worth noting that these privileges can be further refined through the use of field-level security, which allows administrators to restrict access to specific fields within a table based on a user's security role.