InsideSales.com
InsideSales.com
InsideSales.com Menu

Permission Settings

Most organizations will not need to make special accommodations in their Salesforce permissions to use the PowerDialer. Occasionally, however, an organization feels the need to highly restrict user access to data in Salesforce, and want those same restrictions applied to the PowerDialer.

If you are a sysadmin for one of these organizations, we want to support you in securely configuring your dialer package. The following settings have been detailed as the MINIMUM required permissions for the controlling user, and all other users.

Please pay particular attention to the settings for the controlling user. Without proper permissions assigned to this user the PowerDialer may fail to install, or cause errors and broken features post-installation.

General Settings for All Users

  • REQUIRED: All users must have:
    • Individual API access enabled.
    • An IS.com security token present that was generated using their current Salesforce username / password combo. This requires users be able to view the OAuth setup page, as identified in the User Profile Settings section below.
  • HIGHLY RECOMMENDED:
    • Have the Task sub-object view visible for ALL objects in their associated layouts.
    • Give all users "Read" permission for all phone fields and the account name / company name field.
    • Have at least the primary phone field visible on all object layouts.

Controlling User Profile Settings

Page Layouts

  • The assigned layouts for the controlling user's profile must include any fields which will appear in the PowerDialer. If an administrator later changes their mind and wants to restrict field access, you do not need to change the layouts in Salesforce. Instead, use the InsideSales.com field exclusions tool.

Field-Level Security

  • REQUIRED: Must not have any field accessibility restrictions for ANY objects to which PowerDialer users must have access. At the very least this includes:
    • Phone numbers
    • Account name / Company name
    • All task fields
    • Contact name
    • Lead first and last name
  • RECOMMENDED: We highly recommend that the controlling user have NO field-level visibility restrictions.
  • Read-only fields can be set as needed, but we recommend using the PowerDialer field exclusions tool instead.

Administrative Permissions

  • REQUIRED: API Enabled - Yes
  • Must have SF API access enabled, with a valid API / OAuth token. If the controlling user does not have a valid token, no communication passes between platforms.
  • Manage Package Licenses - Yes
  • Manage Public Templates - Yes
    • This is required so users can access email templates from the PowerDialer interface.
  • Edit HTML Templates - Yes
    • This also applies for using email templates in the PowerDialer.
  • Manage Billing - Yes
  • HIGHLY RECOMMENDED: View All Data - Yes
  • HIGHLY RECOMMENDED: View All Users - Yes
  • HIGHLY RECOMMENDED: View Setup and Configuration - Yes

General User Permissions

  • Convert Leads - Yes
    • This has to be enabled for the controlling user if you wish to allow agents to convert leads from the PowerDialer.
  • Download AppExchange Packages - Yes
  • REQUIRED: Edit Tasks - Yes
  • Manage Connected Apps - Yes
  • Transfer Leads - Yes
    • This is required if you ever wish to use lead "queues" as part of a dialer Seek or Domino query.
  • REQUIRED: Send Email - Yes

Standard Object Permissions

  • The controlling user MUST have the ability to view and modify ALL Salesforce objects that the dialer will ever "touch." This generally includes all standard Salesforce objects, and any custom objects for your organization.

Enabled Apex Class Access

  • REQUIRED: The controlling user MUST have access to all "qbdialer" namespace Apex classes.

Enabled Visualforce Page Access

  • The controlling user must have access to ALL dialer-related Visualforce pages. These are prefaced with the "qbdialer" namespace.

Standard Users Profile Settings

Page Layouts

  • Your users will only be able to see fields in the PowerDialer if they are 1) assigned to the object layout for their profile, and 2) are present in the controlling user's assigned layout for the appropriate object type.
  • If there are specific fields you only want certain Salesforce users to see, but multiple agents belong to the same profile, you'll need to create a permission set that overrides the profile setting.

Field-Level Security

  • RECOMMENDED: Leave all task object fields visible.
  • RECOMMENDED: Leave all email object fields visible.
  • For other standard Salesforce objects, you can make any fields you wish invisible or read-only.
  • If you wish to allow users to create their own Seek and / or Domino lists, you must leave field visibility enabled for all items related to:
    • Dialer Query
    • Dialer Query Attendee
    • Dialer Query Item
    • Seek Initiative
    • Seek Initiative Attendee
    • Seek Initiative Item

Tab Settings

  • RECOMMENDED: Tab Setting for InsideSales set to "Default On."

Record Type Settings

  • The PowerDialer automatically accounts for lead record types if used by your organization.

Administrative Permissions

  • API Enabled - Yes
  • Create and Customize List Views - Yes  (For building Domino lists this is necessary)
  • For Email:
    • Edit HTML Templates - Yes (For creating 1-click email content)
    • Manage Public Templates - Yes

General User Permissions

  • REQUIRED: Edit Tasks - Yes
  • RECOMMENDED: Manage Leads - Yes
    • If you want users modifying records, changing ownership, or creating new leads while making calls in the PowerDialer, this is required.
  • REQUIRED: Send Email - Yes
  • RECOMMENDED: Convert Leads - Yes

Standard Object Permissions

  • REQUIRED: Dialer agents MUST be allowed to read and edit any objects you want them to have the ability to  dial. We highly recommend at the very least that you have lead, account, and contact permissions for "read" and "edit" enabled.
  • Data Administration Settings - The PowerDialer purposefully has the ability to respect or ignore the Data Administration (View All or Modify All) settings on a per-list level. Set these up how you see fit; we'll discuss the dialer list controls when looking at how to set up Seek or Domino lists.

Custom Object Permissions

  • REQUIRED: Dialer Queries - "Read"
    • This must be enabled for users to view Domino lists.
  • RECOMMENDED: We recommend allowing read, create, edit, and delete permissions for Dialer Queries, giving users more control over Domino lists they build for themselves.

Enabled Apex Class Access

  • REQUIRED: Users must have access to:
    • qbdialer.QueryBuilder
    • qbdialer.QueryPreview
    • qbdialer.SeekInitiative

Enabled Visualforce Page Access

  • REQUIRED: Users MUST have access to:
    • qbdialer.Query_Builder_List_View
    • qbdialer.Seek_Initiative_List_View
    • qbdialer.is_links
    • qbdialer.InsideSales_OAuth_Setup
  • RECOMMENDED: Enable all "qbdialer" namespace pages.

Permission Set Options

If your organization uses permission sets to modify security profiles, refer to the following settings.

Object Settings >> Users

  • REQUIRED: ALL permission sets must include:
    • InsideSales Authorization Token - "Read"

Object Settings >> Tasks

  • Create and modify Tasks MUST be enabled.

Visualforce Page Access

  • qbdialer.Seek_Initiative_View
  • qbdialer.is_links
  • qbdialer.is_close
  • qbdialer.InsideSales_OAuth_Setup
  • qbdialer.InsideSales_Setup

Dialer Queries Object

Object Permissions

  • Read

Dialer Query Attendees Object

Object Permissions

  • Read

Dialer Query Items Object

Object Permissions

  • Read

Field Permissions

  • "Read" and "Edit" permissions for any objects you wish users to dial.

Domino Lists Object

Object Permissions

  • Available
  • Visible

Seek Initiative Object

Object Permissions

  • Read
  • View All

Field Permissions

  • Email Folders - Read
  • Attendees - Read.
    • This applies ONLY if you plan on allowing users call names owned by other users.

Seek Initiative Items Object

Object Permissions

  • Read

Field Permissions

  • "Read" and "Edit" permissions for any object types with which users will interact in the dialer interface.

Release Notes

Find our most recent release notes.

Forum

Our InsideSales.com community forum is coming soon.

Advanced Training Guides

Advanced training for the PowerDialer for Salesforce.

Have questions?

We're happy to help. An InsideSales.com expert is just a phone call away.

(866) 593-2807

Mon-Fri 6-7 MST

Back To Top

© 2004–2014 InsideSales.com, Inc. all rights reserved. Use of the InsideSales.com service and this Web site constitutes acceptance of our Terms of Use and Privacy Policy. InsideSales.com technology is protected by the following United States Patents: 8078605, 8325738, 8352389, 8510382, 8566419.