How to
Assigning Permission Sets

How Permission Sets Work

Salesforce permission sets are additive layers. A user's effective permissions are the union of their profile permissions plus every permission set assigned to them. Assigning multiple permission sets to a user stacks the permissions — no permission set overrides or restricts what another grants. If one permission set grants read on an object and another grants create, the user has both.

This means you can combine permission sets freely. For example, a user can hold both Pendula Administrator and Pendula Console Composer to manage settings and send messages.

Permission Sets at a Glance

Pendula Console Viewer and Pendula Console Composer — Choose One

While permission sets are generally additive, Pendula Console Viewer and Pendula Console Composer are designed as alternatives — assign one or the other, not both. Composer is a strict superset of Viewer: edit access on an object implies read, so every permission Viewer grants is already covered by Composer. Assigning both is harmless but redundant.

Pendula Console Viewer

Purpose: Read-only access to message history in the Pendula Console.

Assign to Salesforce users who need to see communication history but do not send messages.

Object Permissions

All fields on these objects are read-only.

Other Access

• ConsolePermissionChecker Apex class (required for the Console LWC to render)
• Event.P4E_Message__c field: read
• Tabs visible: Console Messages, Messages, Message Events, Message Recipients
• Message__c record types visible: Inbound_SMS, Outbound_Email, Outbound_SMS

Pendula Console Composer

Purpose: Full Console access — view and send messages.

Assign to Salesforce users who interact with contacts/leads via the Pendula Console.

Object Permissions

All fields on Console_Message__c, Message__c, and Message_Event__c are read and editable. Fields on Message_Recipient__c are read-only.

Template__c access is read-only — composers can use templates but not modify them.

Difference from Console Viewer

Console Composer is a strict superset of Console Viewer — use it instead of, not alongside, Console Viewer. The additions are:

• Create and edit on Console_Message__c (enables sending messages)
• Create and edit on Message__c
• Read access to Template__c (for selecting message templates when composing)
• All fields on Console_Message__c and Message__c become writable (not just readable)

Other Access

• ConsolePermissionChecker Apex class
• Event.P4E_Message__c field: read
• Tabs visible: same as Console Viewer
• Message__c record types visible: Inbound_SMS, Outbound_Email, Outbound_SMS

Pendula Administrator

Purpose: Access to the Pendula settings tab within the Pendula app.

Assign to Salesforce admins responsible for configuring the managed package behaviour - for example, which record types to match and which channels should be published as Salesforce activities.

Access Granted

• Pendula Lightning app (Pendula4E_Lightning) visibility
• Settings tab visible

This permission set grants no object or field permissions - it solely controls visibility of the Settings UI. It is typically combined with another permission set (e.g., Console Composer) for admins who also use the Console.

Pendula Template Designer

Purpose: Full management of Template__c records.

Assign to users who create and maintain message templates used by the Console.

Object Permissions

Field Permissions (read and edit)

• Template__c.Description__c
• Template__c.Related_Object_API_Name__c
• Template__c.Related_Object_Type__c
• Template__c.Template_Text__c

Other Access

• Pendula Lightning app visibility
• Templates tab visible
• Template__c record type visible: SMS

Pendula Integration User

Purpose: Allows the Pendula service to write communication records to Salesforce.

Assign only to the dedicated Salesforce integration user whose credentials are used by Pendula for OAuth 2.0 authentication. Do not assign to human end users.

For full details see Activity Sync Integration Permission Set

System Permissions

Pendula4E Object Permissions

All fields on Message__c and Message_Event__c are read and editable. Fields on Message_Recipient__c are read-only.

Recipient Matching — Standard Object Permissions

Account / Person Account permissions are not included. See Activity Sync Integration Permission Set if your org uses Person Accounts.

Recommended Assignments by Role