Permission Set Assignments

Overview

Permission Sets control access to PhoneTools features. Two packaged Permission Sets ship with the package, one for the people who use PhoneTools and one for the people who administer it.

Neither is assigned for you, and neither is quite sufficient on its own. The packaged user Permission Set grants read access to the three functional fields but not edit access, and the administration sections of the PhoneTools Administration tab need a permission that a Permission Set cannot grant at all. This page covers all three pieces.

About Permission Sets

Permission Set	Assign To	Purpose
PhoneTools	All users	Lets a user see screening results and use the Lightning Component
PhoneTools_AdminUser	Admin users only	Makes the PhoneTools Administration tab visible

Note: The admin Permission Set should only be assigned to users who need to manage PhoneTools configuration.

Step 1: Assign the Permission Sets

1. Navigate to Setup > Permission Sets.
2. For each Permission Set you are assigning:
   • Select the Permission Set name.
   • Select Manage Assignments.
   • Select Add Assignments.
   • Select the users who need this permission.
   • Select Assign.

Step 2: Grant Edit Access to the Functional Fields

This step is what most PhoneTools permission problems come down to, so do not skip it.

Screening writes its result back onto the record as the user who triggered it. That is true of the Screen button on the record page and of a Flow that queues a screen when a record is saved. The packaged PhoneTools Permission Set grants read access to the three functional fields and no edit access, so a user who has only that Permission Set can see results that somebody else produced but cannot produce one themselves.

A user who screens records needs all of the following:

• read access to the phone fields being screened, such as Account.Phone,
• read access to the object's Phone Status Field, Next Screen Due Field and Screening Results Field,
• edit access to those same three fields, and to the object itself.

Grant the edit access with your own Permission Set:

1. Navigate to Setup > Permission Sets, then select New.
2. Enter a Label, such as PhoneTools Screening Access, and let the API Name default.
3. Select Save.
4. Open the object settings for each object you screen, and grant edit access to its Phone Status Field, Next Screen Due Field and Screening Results Field.
5. Assign the new Permission Set to the users who screen records, as in Step 1.

Note: You cannot add edit access to the packaged PhoneTools Permission Set, because packaged Permission Sets cannot be edited in a subscriber org. A Permission Set of your own, or field-level security on the profile, is the way to do it.

Step 3: Grant Modify All Data to Your Administrators

Four sections of the PhoneTools Administration tab are only shown to a user whose profile, rather than any Permission Set, has the Modify All Data permission:

• Global Screening Settings
• Scheduled Screening
• Screening Count
• Batch Screening

Phone-Field Configuration and Screening Credits are not restricted, so a user with PhoneTools_AdminUser and nothing else can configure phone fields and read the credit balance, but cannot choose registers, run a batch, or enable the daily job.

This particular check reads the permission from the profile, so assigning Modify All Data through a Permission Set will not satisfy it. In practice this means the sections above are available to System Administrators, and to users on a custom profile that grants Modify All Data.

Assignment Guide

• PhoneTools → Assign to all users who need to see screening results.
• PhoneTools_AdminUser → Assign to admin users only.
• Your own edit-access Permission Set → Assign to everyone who needs to press Screen, and to anyone whose record saves fire a screening Flow.
• Modify All Data on the profile → Required for the four administration sections listed above.