Configuring Permission Sets

The information in this section pertains to version 5.0 of OneSpan Sign Embedded Integration for Salesforce. In addition to these configurations, you must also perform the procedures described in Basic Permission Set Configurations

If you are configuring permission sets for an older version of OneSpan Sign Embedded Integration for Salesforce, you can skip this section and go directly to Basic Permission Set Configurations

The following standard objects and fields must have at least Read access granted for each OneSpan Sign Embedded Integration for Salesforce user:

• Account object

• Case object

• Contract object

• Opportunity object

• Product object

• Contact object

• Contact fields:

  • Account

  • Email

  • Title

  • MobilePhone

• Lead object

• Lead fields:

  • Email

  • Title

  • MobilePhone

While it is possible to manually configure these permissions, the following script can be used by advanced OneSpan Sign Embedded Integration for Salesforce administrators to automate the creation of this permission set. This script will create a permission set that grants Read access to the fields above.

To grant permissions using a script:

1. Log into OneSpan Sign Embedded Integration for Salesforce.

2. Click the Setup icon.

3. Click Developer Console.

4. Click Debug, and then Open Execute Anonymous Window.

5. In the Enter Apex Code window that appears copy and paste the following code:

   PermissionSet ps = new PermissionSet(Name = 'StandardFields', Label = 'Standard Fields Permissions', LicenseId = [SELECT Id FROM UserLicense WHERE Name = 'Salesforce' LIMIT 1].Id, Description='This is permission set which grants access to standard fields needed by OSS application');
   insert ps;
   
   List<ObjectPermissions> objPerms = new List<ObjectPermissions>();
   List<FieldPermissions> fieldPerms = new List<FieldPermissions>();
   
   Map<String, List<String>> objectsAndFieldsForReadAccess = new Map<String, List<String>>();
   objectsAndFieldsForReadAccess.put('Account', new List<String>());
   objectsAndFieldsForReadAccess.put('Case', new List<String>());
   objectsAndFieldsForReadAccess.put('Contact', new List<String>{'Email', 'Title', 'MobilePhone', 'Account'});
   objectsAndFieldsForReadAccess.put('Contract', new List<String>());
   objectsAndFieldsForReadAccess.put('Document', new List<String>());
   objectsAndFieldsForReadAccess.put('Lead', new List<String>{'Email', 'Title', 'MobilePhone'});
   objectsAndFieldsForReadAccess.put('Opportunity', new List<String>());
   objectsAndFieldsForReadAccess.put('Product2', new List<String>());
   
   
   for(String objectName :objectsAndFieldsForReadAccess.keySet()){
       ObjectPermissions objPermission = new ObjectPermissions();
       objPermission.ParentId = ps.Id;
       objPermission.PermissionsRead = true;
       objPermission.SobjectType = objectName;
       objPerms.add(objPermission);
       for(String fieldName :objectsAndFieldsForReadAccess.get(objectName)){
           FieldPermissions fieldPermission = new FieldPermissions();
           fieldPermission.SobjectType = objectName;
           fieldPermission.PermissionsRead = true;
           fieldPermission.ParentId = ps.Id;
           fieldPermission.Field = objectName + '.' + fieldName;
           fieldPerms.add(fieldPermission);
       }
   }
   insert objPerms;
   insert fieldPerms;

6. Click Execute.

7. Assign this permission set to your users.

Custom Fields

When a user opens a Transaction or Transaction Template, the OneSpan Sign Embedded Integration for Salesforce connector queries all fields on the transaction or transaction template object. If you are creating and adding custom fields to either of these pages you must ensure that your users have at least Read access privileges to these custom fields. If you do not, they may receive an insufficient privileges error.

If you are adding a custom field that is of a Lookup or Master-Detail type, then you must also give your users Read access to the related object of that new custom field.

If you are using Field Mappings, the custom fields that you are creating must be accessible (for insert), and editable (for writeback). As such, ensure that your users have the proper access as needed.