Permissions Reference

Custom Permissions

Seven custom permissions are defined in the package. All are prefixed CallCore_.

Permission Hierarchy

Permissions form an implication chain. Holding a higher permission automatically satisfies all checks below it. This is implemented explicitly in CallCoreSecurity — there is no platform-level inheritance.

CallCore - Listen To All Call Recordings  (CallCore_ListenToAllCallRecordings)
    └── implies CallCore - View All Call Transcripts  (CallCore_ViewAllCallTranscripts)
            └── implies CallCore - View All Call Summaries  (CallCore_ViewAllCallSummaries)
                    └── implies CallCore - View All Calls  (CallCore_ViewAllCalls)

In other words: a user who can listen to all recordings can by definition see all transcripts, summaries, and call records.

canViewAllCallTranscripts()  → canListenToAllCallRecordings() OR has CallCore_ViewAllCallTranscripts
canViewAllCallSummaries()    → canViewAllCallTranscripts()    OR has CallCore_ViewAllCallSummaries
canViewAllCalls()            → canViewAllCallSummaries()      OR has CallCore_ViewAllCalls

Own-Call Access

"Own call" means the user is the Salesforce user matched to the call's PhoneCallHandler__c. Own-call access is gated by a single permission: CallCore_ListenToHandledCallRecordings. Holding this permission grants the ability to view, see summaries, see transcripts, and listen to recordings for calls where the user is the handler.

Per-Item Permission Checks

Passing the permission gate does not mean the user can see all content on every call. Per-item checks compare the running user's ID against the handler's linked user ID:

• Summary: visible if (userIsHandler AND canViewOwnSummaries) OR canViewAllSummaries
• Transcript link: visible if transcript is Available AND (userIsHandler AND canViewOwnTranscripts) OR canViewAllTranscripts
• Recording player: visible if recording locator exists AND (userIsHandler AND canListenToOwnRecordings) OR canListenToAllRecordings

Permission Sets

Eight permission sets are shipped with the package. Admins assign these to users via Profiles or Permission Set Groups.

Permission sets are additive. A typical agent gets CallCore TX - Handled Calls Access. A supervisor might get that plus CallCore TX - View All Calls. A QA analyst gets CallCore TX - Listen To All Call Recordings (which implicitly covers everything beneath it).

Restriction Strategies

Custom permissions control what type of data a user can see. Restriction strategies control which subset of that data they can see. The two layers are independent and both must pass.

Two restriction strategies are evaluated at the start of every timeline query:

RestrictSources — returns an IdRestriction representing which Source__c records the user may access. If the default implementation is in use (or no override is configured), it returns IdRestriction.allowAll() and sources are not filtered. A subscriber org might override this to restrict users to only the phone lines relevant to their department.

RestrictCallHandlers — returns a set of allowed User__c IDs (the Salesforce users linked to handlers the running user may see). Used to filter the query to only segments handled by permitted users. Like RestrictSources, defaults to allow-all if not overridden.

The convention for restriction strategies:

Both restrictions are applied as SOQL filters inside PhoneCallQueryStore. They are evaluated once per timeline request and passed into the query, not checked per-row after the fact.