How does Table/record ownership work in Dataverse?

[HamidBee]

I am trying to understand Table ownership in Dataverse tables. I read the following online:

"For user and team owned records, the access level choices for most privileges are tiered Organization, Business Unit, Business Unit and Child Business Unit or only the user’s own records. That means for read privilege on contact, I could set user owned, and the user would only see their own records."

I have the following questions:

1. Is 'User and team' the same thing? or does it mean user or team?.

2. Why is 'Team' not visible in the key above?.

3. What does each access level mean? can someone please provide examples. The following image can be used to provide examples:

Thanks in advance. 

[Akash17]

Hi @HamidBee 

Please refer this best video this will give you deep idea about your concern 
https://www.youtube.com/watch?v=l8kQ_UzcqUY&list=PLst08atUCXBoKPwxCLvTxF66zmVpQPMbe&index=12

https://www.youtube.com/watch?v=xGl8JrAu5Cs&list=PLst08atUCXBoKPwxCLvTxF66zmVpQPMbe&index=13

Thank you

[HamidBee]

HI @Akash17. Thank you for contributing. For the first point:

1.  I guess for 'User and Team' this is referring to users and teams mentioned below rather than an actual security role. 

2. What I mentioned above would answer this point.

Using the first video you shared I can say the following about the access levels:

3. 

	The can only do perform this action on their own data.
	They can perform this action on data within their business unit.
	They can perform this action on data within their business unit and all data in the parent business unit but not the child business unit.
	They can perform this action on all data within the organisation.

Is the definition provided for the 'Parent: Child Business Units' correct?. Hi @timl, @iAm_ManCat  I'm just wondering what your thoughts are on this too. 

Thanks in advance. 

[timl · Accepted solution]

Hi @HamidBee 

1. From your reply, I think you get the gist of the meaning of "User or team".

Just to clarify, "User or team" refers to the record ownership type, which you can select when you create a new table. This ownership type means that records are owned by either a user or a team.

In contrast, we would typically set the ownership type to "organisation" for reference type data that we want users in the organisation to be able to access.

2. You're correct in that the key in your screenshot relates to a "security role". Because we assign security roles to users and/or teams (possibly multiple teams), that's the reason why "team" doesn't appear in the key.

3. The definition for "Parent: Child Business Units" doesn't read correct to me. We use this to configure subordinate access to data. I think the description in the documentation describes this more clearly.

https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges