While implementing Salesforce Community, identifying the record access requirements is an important steps which we all should do before procuring user licenses or setting up the communities. The reasons why I am telling this are -Sharing options in Communities depends on the type of Community User License (Customer or Partner)Even with the most open user license (Partner), there are few “gotchas” when it comes to sharing in a Community.You need to adjust internal sharing settings to make sure you are not giving unwanted record access to your community users.License TypesSalesforce has a great chart here which compares features between Customer and Partner user license. But I prefer the below picture while deciding the license types.In short, Customer licenses are designed for high-volume applications with any complex sharing requirements. Customer licenses are not having any roles. That is why sharing rules, Apex sharing and manual sharing are not available for Customer licenses.On the other hand, Partner licenses are having access to more object types. For example, if you want community users should have access to Leads, Opportunities, Campaigns, upload contents then you need Partner license. Partner licenses are having roles so sharing options are available.In addition to the above two licenses, Salesforce has Customer Plus license which is kind of middle between Customer and Partner license. So if your requirement is that you want your customers to have full access...Read More
In a big organization, a single admin can a big problem in terms of bandwidth issues. Normally admins are getting multiple requests like – creating users, updating profiles, resetting the password, running report etc. along with their daily meetings. So it will be really difficult for a single admin to handle all these requests by himself/herself. And that is the place where admins want to delegate some of their work to others (trusted colleagues). But trust me, it is a big decision. You should not give all the admin privilege to your colleagues even though he/she is a very trusted employee. Rather you should delegate few specific task to your colleagues. In Salesforce, we can do the same with DELEGATE ADMINISTRATION. So basically Delegate Administrator will allow named users to manage other users within selected roles and profiles, as well as managed selected custom objects. With Delegate Administration, you can configure named users to do the below things -Role & Subordinate: Delegate Administrator can create and edit users with specific roles and subordinates. The can’t modify the role hierarchy though.Profile: Delegate Administrator can assign users(they create or edit) to assigned profiles. They can’t modify the profile.Permission Set: Delegate Administrator can add/remove selected permission sets from users(they create or edit) to assigned profiles. They can’t modify the permission set.Public Group: Delegate Administrator can add/remove selected public groups from users(they create or edit)...Read More
- Salesforce API – New and Changed Objects
- New Video – Mastering Google Cloud Storage Part 3 – Diving Deep into Retention Policies!
- Salesforce Winter 24 Release | Sharing Related Enhancements
- How To Perform Enhanced List Sorting with Comparator Interface
- Unleashing The Power of AI: Salesforce and Tableau GPT