How does the Table Ownership setting change how data is controlled?

[MJWhite]

The Dataverse documentation in the screenshot below explains that the Table Ownership will change how data is controlled but it doesn't explain how it will change how data is controlled?

Does it mean that that the 'Contact Access' option in table permissions will be disabled for a table with 'Organisation' ownership or does it mean something else? 

Any thoughts?

[MJWhite]

A bit more digging unearthed this: Security concepts in Microsoft Dataverse - Power Platform | Microsoft Learn

The main summary: Dataverse supports two types of record ownership. Organization owned, and User or Team owned. This is a choice that happens at the time the table is created and can’t be changed. For security purposes, records that are organization owned, the only access level choices is either the user can do the operation or can’t. 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.

This also explains why when creating a table:

• If Organisation owned is selected, the table will include the column Organisation ID (see screenshot below)
• If User or Team Owned is selected, the table will include the columns Owner, Owning Business Unit, Owning Team, Owning User (see screenshot below)

Organisation owned:

User or Team Owned:

Which will I choose?  Probably the default (User or Team Owned) because:

• It is the default
• It keeps options open should I need the functionality in the future, whereas Organisation owned seems to close down options for the future

[Fubar · Accepted solution]

This more of a standard Dataverse question rather than being specific to Power Pages (as Power Pages security model is not the same and uses Table Permissions that are based on relationships) 

• Once set it cannot be changed
• If your records need to be owned by a User or Team then that you need this option. Tables that are configured as Organization cannot be owned by Users or Teams
• If you need to implement separation and segmentation of data then you need to select User or Team Owned
• The security privileges for Tables that are configured as Organization are none and organization (full)
• A Table that is configured as User or Team, the security privileges can be set to so the access to records emulate that Organization owned, but the opposite is not true.

Because you can set security privileges so that User or Team owned behaves similar to Organization, and you cannot change the setting for the Table later, User or Team is usually the better option.

[MJWhite]

Thanks Fubar

As you may have seen, I more or less got to the same conclusion with some digging around yesterday, but your answer provides a better explanation, so I've now accepted your post as the solution.