DataVerse Table Permissions question

(0) Share

Report

Posted on by rprahalad

377

Hello All,

I have been creating tables in DataVerse for consumption in my Canvas app. I have read quite a bit on the "User Or team" vs "Organization" level permissions. Like, I have created two tables that have "User Or Team Level" permission set on them and CRUDing data in and out of it. I also Published it and another member of some other team also ran the app successfully as well.

I know I was the one who created the table and we are still in development. But those 2 levels of permissions seems so important when you read the MS docs on it. But I have no clue when/where/how we would see errors because of not setting permissions on the table to the org level.

Can you please enlighten me where it would affect us badly and start throwing errors for tables that have 'User Or Team' permissions? I am almost thinking of setting permissions to 'Org Level' for every table I construct within the Dataverse and then control the IN and OUTS of data through my Canvas app. Or is there anything else I need to be aware of?

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report

Hi @rprahalad,

If you set the table to Organization level, that means you will be able to provide an all or nothing access to that table for a given Security Role. This is typically not flexible enough in most cases. Usually the only time we set the table to organization owned is when the table is just a lookup list used in place of a Choice column.

In general, if you are unsure what granularity of access you will need to to secure a table at design time (you should be doing your security modelling beforehand however), then go with "User or Team Level", as you cannot change this after the table is created. To change this you would effectively need to recreate the table and then migrate your data which is a pain.

You can always dial the granularity up or down based on the security need later. The security errors that you will see will generally let you know exactly what permission is needed (the syntax/verbage is a bit cryptic at first but you get used to it), and there are plenty of resources out there to help troubleshoot a specific error. There are even tools available today to help debug security errors such as the Security Debugger from the XrmToolBox.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
rprahalad 377 on at

Like (0)

Report

Thanks so much, @ChrisPiasecki ! I so appreciate this response.

Yes, majority of my tables I have set it to User Or Team level and almost instinctively I went with Org level for those Master tables. But I was unsure how and when the users would actually see an error because of this setting.

Its my first project with PowerApps and so, it is very very helpful to hear someone opine about it!

Was this reply helpful? Yes No