Managed Permission Sets

Overview

The Unmanaged Recruiter Permission Sets (introduced during the Bullhorn for Salesforce Security Review) have been replaced with Managed Permission Sets following a Permission Set Review. The Managed Permissions Sets include most of the permissions previously available in the Unmanaged Recruiter Permission Set. This article covers using and configuring Managed Permission Sets.

Using Bullhorn for Salesforce Managed Permission Sets

Benefits of Using Permission Sets

• Each User In Salesforce terminology, this is anybody that has login access to an instance. In BH4SF instances, usually the staff of recruiting companies’s access level can be configured separately based on business needs and product features.
• Easier to apply the principle of least privilege, only granting access to data that each user needs to do their job A job (vacancy, position, role) is an opening for which a customer's client needs a placement..
• Admin users have an understanding of the purpose of each permission set.
• Enhanced security with no “superuser” access.
• Using Permission Sets aligns with Salesforce best practices. See Admin Best Practices for Use Management for more information.

Assigning Permission Sets

You can assign permission sets to your users based on the functionalities they need access to or create Permission Set Groups by adding together all the required permission sets for a specific role A job (vacancy, position, role) is an opening for which a customer's client needs a placement..

• New Customers: The process is to analyze your user's needs and assign the appropriate permission sets or permission set group accordingly.
• Existing Customers: It is advisable (if you use packaged Permission Sets) that a review is done once you upgrade to Package Version 6.78.1 or higher. If required, we can provide the following information to assist with the review:
  • Content of managed permission sets in the package version you are upgrading from vs. content of managed permission sets in the package version you are upgrading to.
  • Highlights of what has been added, removed, and changed.

Options After Upgrade

Depending on how you managed permissions prior to upgrading to 2023.06 GA Release, a few options can be considered to decide how to proceed after the upgrade:

Option 1: If you want to use BH4SF packaged permission sets.

• Assign relevant BH4SF packaged permission sets to users. This can be done by assigning all BH4SF permission sets individually or by creating a permission set group and assigning that permission set group to all users.
  • Do not clone BH4SF packaged permission sets as they are "upgradeable," and you will only get the benefit of automatically getting the upgrades with new package releases if you assign them to users as they are.
• For the permissions that cannot be packaged (more about this below in: Managed Permissions Sets and Manual Configuration ): create a new, unmanaged permission set in your Org. For example, “BH4SF unpackaged permissions” and assign it to users either individually or as part of the permission set group you created earlier.

Option 2 : If you have your own permission sets/ profiles.

• Assistance is available if you need a full list of the permissions packaged in 2023.06 GA Release plus a list of the remaining permissions that are required but cannot be packaged for the purpose of comparing to their own assigned permissions.
• Going forward, the release notes will contain a list of any updates made to the packaged permission sets for that release (any new permission set added or any change to existing permission sets; any unpackaged but required permission). You can then manually add them as required, in full or partially.

Managed Permission Sets

Below is the list of the Permission Sets available in the Bullhorn for Salesforce managed package as of 2023.06 GA Release and the list of permissions that need to be added manually to complete configuration.

	Permission Set Label	Feature
1	Account Pool A Set/Pool of automatically created Accounts that Candidates can be assigned to through an automated process v2 User	AccountPoolv2
2	Activity Filter Settings	Activity Filter Settings
3	Additional Locations User	Additional Locations Functionality
4	ATS High Volume	ATS v2 High Volume
5	ATS v1 User	ATS v1
6	ATS v2	ATS v2
7	BH4Force Basic	Basic permission set for the managed package. The permission set includes all base components that are required by all features (and not specific to any functionality covered by other permission sets).
8	Browse User	Extended Browse
9	Call Lists A Mass Mailing tool that's used to mass mail a list of candidates or clients User	Call Lists
10	Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Statistics	Candidate statistic (summary) feature
11	Consent In BH4SF , Consent is used in the context of GDPR or similar data privacy processes. Candidates or Clients are usually asked to consent to the storage or sharing of their personal data. Tool V2 User	Consent Tool V2
12	Consent ToolUser Permissions	Consent Tool V1
13	Daxtra A BH4SF partner. One of the Search and Match / Resume Parsing services providers integrated with BH4SFIntegration	Daxtra Search
14	Email Activity Configuration	2020 Email Editor Email Activity
15	2020 Email Editor User	All features of the 2020 Email Editor.
16	Email Editor Signature User	Permissions necessary for a non-admin user to add signatures to emails sent with 2020 Email Editor.
17	Email OptOut	Opt-Out Logic offered for 2020 Email Editor.
18	Email Resume Application First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) Handler	Permission Set for Email Parsing Handler.
19	GDPR General Data Protection Regulation is a set of rule enacted by the EU to further protect candidate / contact informtion and provide them control over their own information. User	Consent (GDPR)
20	GenericLookup User	Generic Lookup
21	Job Lead Name of BH4SF custom object. It stores details about a Job position not yet advertised or confirmed by a potential Client. Once the Client agrees to use the recruiter's services to fill the open position, then a Job Lead can be converted into Job record. User	Job Leads Object. Its records store details about a Job position not yet advertised or confirmed by potential Client. Once the Client confirms, the Job Lead can be converted to Job record.
22	Job Lead A record that holds a potential relationship with a person or company. Examples: candidates, contacts, companies, jobs. Billing User	Job Billing Feature
23	Job Filter User	Job Filter when launching Add to Job Application from SaM.
24	Job Parsing	Bullhorn for Salesforce Job Parsing.
25	Job Roles A job (vacancy, position, role) is an opening for which a customer's client needs a placement. User	Job Roles Functionality
26	Long List Name of a BH4SF custom object. It 'captures' Candidates that look like a good match for a Job, before the actual hiring process begins. It's like a list of potential candidates User	Long List Functionality
27	Mass Processing	Mass Parsing/Mass Sync requests
28	Message Channels Admin	Email Screen
29	Module Logger User Permissions	BHLO User Permission
30	Module Textkernel User Permissions	BHTK_User_Permissions
31	Non-CV Parsing User	Non-CV Parsing
32	Off Limit User	Off-Limits Functionality
33	Power Notes User	Power Notes
34	Power Notes Admin	Power Notes
35	Related Job User	Related Job Functionality
36	Resume Manager	Resume Manager
37	Target Account User	Target Account Functionality
38	Team Member Credits User	Team Member Credit Functionality
39	Textkernel iFrame Portal User	Textkernel iFrame / Portal
40	Textkernel Search Integrity User	Search Integrity
41	USAM User	USAM

Manual Configuration

If you are using Packaged Permission Sets, some manual configuration is required to add permissions that cannot be packaged. For more details on such limitations, please refer to Salesforce documentation: Permission Sets and Profile Settings in Packages.

This is the link for the List of Packaged Permission Sets.