Wednesday, 29 July 2015

External Organization-Wide Defaults Overview

External Organization-Wide Defaults Overview


External organization-wide defaults provide separate organization-wide defaults for internal and external users. They simplify your sharing rules configuration and improve recalculation performance. Additionally, administrators can easily see which information is being shared to portals and other external users.
The following objects support external organization-wide defaults.
  • Accounts and their associated contracts and assets
  • Cases
  • Contacts
  • Opportunities
  • Custom Objects
  • Users
External users include:
  • Authenticated website users
  • Chatter external users
  • Community users
  • Customer Portal users
  • Guest users
  • High-volume portal users
  • Partner Portal users
  • Service Cloud Portal users


****Chatter external users have access to the User object only.

Previously, if your organization wanted Public Read Only or Public Read/Write access for internal users but Private for external users, you would have to set the default access to Private and create a sharing rule to share records with all internal users.
With separate organization-wide defaults, you can achieve similar behavior by setting the default internal access to Public Read Onlyor Public Read/Write and the default external access to Private. These settings also speed up performance for reports, list views, searches, and API queries.

No comments:

Post a Comment

Why to use Database.Stateful()?

Database Stateful is interface. It is used in batch classes to maintain the state of the class across transactions i.e. if you want to use ...