Security Settings




 
 
NameOffline Session Expiration Limit

Key

pulsar.session.limitdays

Value

 number of days

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.

Notes/Comments




 
 
NameApp Passcode Expiration Limit  

Key

pulsar.passcode.timelimitinhours


Value

number of hours

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

This setting addresses the concern that if the user lost the device and someone else got hold of the device they might be able to access data. This setting forces the user to setup a passcode and prompts them to enter it in order get back into the app. This pin is also used to rekey the database and add an additional layer of security to protect the data.
Notes/Comments




 
 
NameApp Idle Timeout Limit

Key

pulsar.applicationIdleTimeoutLimit

Value

number of minutes

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

Note: This is targeted for a future release. This setting addresses the concern that if the user had the app open after entering the passcode and left the device unattended and someone else got hold of the device they might be able to access data. This setting will automatically lock the screen so that on the next attempt to access the app, the user will be forced to enter the passcode.
Notes/Comments




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

Key

pulsar.blockedDeviceModels


Value

iphone, ipod

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.

Notes/Comments




 
 
NameBlock Pulsar for Certain User Accounts

Key

pulsar.blockedUserNames

Value

 brad@example.com, geetha@example.com 

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments




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

Key

pulsar.appVersion.minimum

Value

2.3.17

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/CommentsDefining 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.




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

Key

pulsar.appVersion.minimum.reminderIntervalHours

Value

24

Default Value (if any)

0
Compatibility
  • iOS
  • Windows
  • Android

Description

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.

Notes/CommentsAvailable in 13.0+


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

Key

pulsar.appVersion.maximum

Value

4.3.21

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments


 
 
NamePrevent Create capabilities for objects on the Device

Key

pulsar.denyCreate.objects

Value

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

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments




 
 
NamePrevent Edit capabilities for objects on the Device

Key

pulsar.denyModify.objects

Value

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

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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




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

Key

pulsar.docs.enableDeleteLocal

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments




 
 
NameValidate Salesforce Credentials On Every Login

Key

pulsar.session.forceTokenValidation

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments




 
 
NamePrint User Info Header in Logs

Key

pulsar.logs.printUserInfoHeader

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

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
Notes/CommentsAvailable in Pulsar 9.0+




 
 
NameEnable Delete Logs

Key

pulsar.logs.enableDeleteLogs

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

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

Notes/CommentsAvailable in Pulsar 11.0+

Related pages