What does Append, Append to, Assing and Share mean?

(0) Share

Report

Posted on by WebPortal

2,295

Hello,

I have a hard time understanding and configuring roles in Dataverse.

By searching the documentation, I find it just too complicated, if all you want is an app that allows users to CRUD custom tables and run instant flows from the app.

What are the following permissions supposed to mean?

Can anyone help?

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Drew Poggemann 9,287 Most Valuable Professional on at

Like (2)

Report

Hi @WebPortal ,

Append - This means the user would have the ability to add a record from this table as a relationship to another table. Example, if the user created a Contant and wanted to be able to add the Contact as a related Contact to an Account then they would need the Append permission on the Contact.

Append To - Same situation in the Account and Contact... This is the opposite side. The user would need the Append To permission on the Account to allow for the adding the Contact to the Account as it is "Appending the Contact record to the Account".

Assign - This allows the User that created the Contact to change the Owner to someone else therefore "Assigning" the record to another user.

Share - This allows the user to Share the record with another user. They can choose to share and provide the user with different levels of security but they need this permission to share to accomplish.

Was this reply helpful? Yes No
WebPortal 2,295 on at

Like (0)

Report

@dpoggemannthank you, that sure helps a lot!

This means, for a canvas app that allows users to CRUD custom tables and run instant flows from the app, I should set all the custom tables:
Create, Read, Write, Delete columns to "Business Unit", and
Append, Append to, Assign, Share to "None".

In my basic understanding of the matter, "Business Unit" means "Yes", whereas "None" means "No".

BTW: for users to be able to run flows from the app: what tables/columns should be configured?

Was this reply helpful? Yes No
Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (3)

Report

Hi @WebPortal ,

You will want to control the roles as the right level of scope... Check out my friend and MVP @AhmedSalih post: https://powerplatformplace.com/f/dataverse-role-based-record-based-security-how-to-tutorial#:~:text=Dataverse%20uses%20role%2Dbased%20security,will%20benefit%20from%20the%20role.%22

You will want to determine if you set the security for the Create, Read, Write, Delete to Business Unit because that will allow one user to modify / delete / create records for all users in the Environment (i.e. Organization level). If you want them to only work with their own records then you should utilize Basic (or User level) security.

On the Append, Append To, Share, Assign - I usually don't lock this down specifically and normally have at Business Unit level because you will have custom tables that relate to other custom tables (Append and Append To) as normal in the processing in Dataverse...

On the Share and Assign, that is really up to you to determine if you want this to None or maybe set to Basic so they can do this with records they own.

Was this reply helpful? Yes No