Introduction

Sometimes complex business requirements lead to the need to configure 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 user’s region or 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 the 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.

Opening Sharing Settings

You can find sharing settings setup for Pulsar Settings here: 

Setup >> Security >> Sharing Settings >> Manage Sharing Settings for "PulsarSetting"

1. Go to the Setup Home Tab.

2. Scroll down to SETTINGS, and expand the Security menu.

3. Click on Sharing Settings to open the Sharing Settings screen.

4. Select PulsarSetting from the Manage Sharing Settings For dropdown menu.

5. The PulsarSettings Sharing Settings screen opens.

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:

• Click "Edit" under Organization-Wide Defaults.
  

  

  For each desired item:
  

  

  • 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"

Example