Security Settings

Offline Session Expiration Limit

pulsar.session.limitdays

 number of days

This setting addresses the concern that if the user is no longer active or in case someone else got hold of the device and the device has been in offline mode, they might be able to access data. This setting sets a time limit on how long the user can stay offline and forces the user out of the app when it expires until they re-authenticate using a network connection.

Block Pulsar on Device Model (iPad, iPhone, etc)

pulsar.blockedDeviceModels

iphone, ipod

This setting will prevent the user from logging in and syncing data to Pulsar on certain device types. Device model names can be separated by commas, semicolons, spaces, or one per line.

Block Pulsar for Certain User Accounts

pulsar.blockedUserNames

 brad@example.com, geetha@example.com 

This setting will prevent the listed usernames from logging in and syncing data to Pulsar. Usernames can be separated by commas, semicolons, spaces, or one per line. This is useful if devices are lost or stolen, or employees leave the company. If the user previously logged into the app, this setting will block the user from accessing the app, delete the user account and wipe the data from the device.

Establish a minimum version of Pulsar users across your org should be running

pulsar.appVersion.minimum

2.3.17

This setting will prevent the user from accessing anything from within the app if their current version is lower than the baseline version you have established.

Defining this setting will enforce this minimum version as mandatory, and users will not be able to login with versions lower than the minimum. If you want to make the minimum version optional, see the pulsar.appVersion.minimum.reminderIntervalHours setting.

Make the minimum version of Pulsar in your org an OPTIONAL upgrade with a reminder alert every X hours

pulsar.appVersion.minimum.reminderIntervalHours

24

0

This setting works in conjunction with pulsar.appVersion.minimum, making it an optional upgrade to the defined minimum version. The user will receive a reminder alert when they login, once every # of hours defined in the setting.

Deleting this setting, or changing its value to 0, will make pulsar.appVersion.minimum behave as a mandatory upgrade.

Available in 13.0+

Establish a maximum version of Pulsar users across your org should be running

pulsar.appVersion.maximum

4.3.21

This setting will prevent the user from accessing anything from within the app if their current version is higher than the maximum version you have established.

Prevent Create capabilities for objects on the Device

pulsar.denyCreate.objects

List of object names the admin wants to deny the user permission to create.

This setting will prevent the user from creating records on the device even if they have permission to do so on the server. Some admins prefer this because they want to avoid creating duplicates offline.

Prevent Edit capabilities for objects on the Device

pulsar.denyModify.objects

List of object names the admin wants to deny the user permission to edit.

This setting will prevent the user from editing records on the device even if they have permission to do so on the server.

Prevent User from Deleting a Content Library Document (On Device Only)

pulsar.docs.enableDeleteLocal

TRUE / FALSE

TRUE

By default, a user may swipe a row to unhide the document delete button.  When the user presses the delete button, the document is only deleted from the device and does not have any effect on the server.  After deleting a document, a user may download the document again from the Document Updates screen.  This setting can disable the delete button from displaying when set to FALSE.

Validate Salesforce Credentials On Every Login

pulsar.session.forceTokenValidation

TRUE / FALSE

FALSE

New to Pulsar 4.1. By default, when a user logs into the app, the status of the user's Salesforce credentials are not explicitly checked to expedite the login process. As an added security feature, this setting will explicitly validate the user's credentials with SFDC on every login.

Print User Info Header in Logs

pulsar.logs.printUserInfoHeader

TRUE / FALSE

TRUE

This setting allows an org to suppress the following log entries for their users.

• OS Version

• Server

• Org Id

• Current User Name

• Local database base name

Available in Pulsar 9.0+

Enable Delete Logs

pulsar.logs.enableDeleteLogs

TRUE / FALSE

TRUE

This setting allows an org to suppress the ability to delete logs for their users.

Available in Pulsar 11.0+