web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / entity ownership user/...
Microsoft Dynamics CRM (Archived)

entity ownership user/team vs organization

(0) ShareShare
ReportReport
Posted on by Community Member

ok folks thoughts

entity ownership user/team vs organization

please explain pros and cons of each, any advice 

Security is a big issue when is it best to use organization over others can anyone give practical examples

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at
    RE: entity ownership user/team vs organization

    Hi,

    Like you said, it all has to do with security. For organizational owned entities, users with a security role can either Create, read and write on organizational level etc., or not at all. This means that if a user creates a Competitor (which is organization owned OOb), another user can change the information on it, overriting the stuff that was applicable specifically for the first user's Business Unit. In other words, the organizational owned entity should be an objective entity, the same for everyone who looks at it.

    For myself, as a rule of thumb, I only put entities on organizational level if they are reference entities that are the same for everyone in the system, visible for everyone, and therefore not sensitive information. Think about things like a contacts preferred language entity or a countries entity.

    As a practical example, I also have a regions entity that ís user owned, because different business units work with different regions. Some work with EMEA, others with EIMEA. There is no need for the regions to be user owned, because it's just two in this example. However, if 4 business units all have their own way of dividing the world into different regions, the list can get very long indeed. With user owned regions, simply set the read level to business unit for the regions entity, and allocate an owner to the region from the business unit that uses that specific region - and all users will only get to see the regions that are applicable for how their business units wants to divide the world!

    Also note that there is always a workaround to hide the owner field and set it automatically, meaning you can approach organizational level security. The other way around is impossible though.

    Hope this helps!

  • Verified answer
    necsa Profile Picture
    necsa 3,455 on at
    RE: entity ownership user/team vs organization

    Hi luckylifestyledesigner,

    here is very usefull explanation about user/team ownership from Hosk's Dynamic CRM Blog,

    crmbusiness.wordpress.com/.../crm-entity-ownership-how-do-you-decide

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Aric Levin - MVP Profile Picture

Aric Levin - MVP 2 Moderator

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#3
MA-04060624-0 Profile Picture

MA-04060624-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans