Introduction
Sometimes complex business requirements lead to the need of configuring Pulsar to behave differently for different groups of users. This is a common case in global orgs where use cases can vary based on the region of the user or their role. For example, let us consider the scenario of a particular group of users needing Objects A, B, and C for offline access, and a different group needing Objects X, Y, and Z for offline access. Admins should be able to configure Pulsar differently for each group of users within their org to accommodate this. You could create multiple pulsar.sync.objects settings and assign the appropriate settings to each user group. And you could use existing Sharing Settings functionality within Salesforce to achieve this. You may already have used this functionality for other similar permission or visibility related use cases.
You can find sharing settings setup for Pulsar Settings under:
Setup >> Security Controls >> Sharing Settings >> Manage Sharing Settings for "PulsarSetting"
Priority Value on PulsarSetting
Assign a Priority value on every Pulsar Setting record based on the business requirement.
Add Priority = 100 for all Pulsar Settings used by all Roles/Groups
Add Priority = 101 for Pulsar Settings for specific Roles/Groups
Add Priority = 102 for Pulsar Settings for a different set of Roles/Groups
Setup
Below are the steps for Setting Up Sharing Settings for Pulsar:
"Edit", Organization-Wide Defaults
Update Default Internal Access to "Private"
Update Default External Access to "Private"
"Select", Grant Access using Hierarchies
Create New PulsarSettings Sharing Rules using PulsarSetting Priority Values
Provide the Rule Name
Select "Based On Criteria"
Update Filter Logic Based on Business Requirements
Assign the Rule to Specific Roles/Groups
Keep the access Level as "Read Only"
For some profiles like System Administrator, we have View All permissions for the PulsarSettings Object. Sharing settings will not work for users with these profiles.