Security Dependencies

[Applies to: Microsoft Dynamics CRM 4.0]

Find the latest SDK documentation: CRM 2015 SDK

Sometimes security dependencies exist because it is necessary to have more than one access right to perform a given action. For example, if you have the CREATE access right for accounts, you can create an instance of the account entity. However, unless you also have READ access for accounts, you cannot create an instance of the account entity and be the owner of that new account instance.

The following table shows the access right dependencies for the actions specified.

Action	Access rights required
To Create an instance and be the instance owner	CREATE READ
To Share an entity instance	SHARE. This right is required by the person doing the share operation. READ. This right is required by the person doing the share operation and also by the person with whom the entity instance is being shared.
To Assign an entity instance	ASSIGN WRITE READ
To Append To an entity instance	READ APPENDTO
To Append an entity instance	READ APPEND

Another type of dependency exists when objects are subordinate to another object. For example, the opportunity and contact objects cannot exist on their own. Each is always attached to an account. To create an opportunity or a contact, you must have the access right APPENDTO on accounts and the access right APPEND on opportunities or contacts.

See Also

Reference

• AccessRights Enumeration

Other Resources

• Microsoft Dynamics CRM Security Model

© 2010 Microsoft Corporation. All rights reserved.