Learn how salesforce.com makes it easy for engineers to work on what challenges and excites them. Opportunity Open Market makes it easy for anyone in the salesforce.com Technology organization move to a new team. This post explains how the program came about and how it works. Continue reading
Tag Archives: Sharing
Salesforce uses a central Group object to manage visibility related to the Role Hierarchy, Territory Hierarchy, Public Groups and Queues. When administrative changes occur in these areas a group membership lock is taken to ensure data integrity is maintained while complex sharing calculations are completed. The following activities take out group membership locks for the duration of their transaction:
- Role creation
- Role deletion
- Moving a role in the hierarchy
- Adding a user to a territory
- Removing a user from a territory
- Moving a territory in the hierarchy
- Territory deletion
- Territory creation
There appears to be a lack of clear understanding around the differences between CRUD, FLS and Sharing. Here's a high-level overview:
Think about your Force.com object as a database table.
- CRUD: is the table level permission. Does the user have access to this table? (Create records in the table, Read records in the table, Update records in the table, and Delete records in the table)
- Field Level Security (FLS): is a more granular column permission. For each column you can set permissions. Does the user have access to this column and what kind of access? Invisible, Visible Read-Only, Visible Read & Write.
- Sharing: is