Off Limits Policies: Account
Overview
An Off Limit Account policy can be created when a recruiting company
A Company is the organization where the contact works. This can also be called the Client. signs an agreement with a new Client A Company is the organization where the contact works. This can also be called the Client. Account. All candidates A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. with current work experience linked to that account become Off Limits. The Off Limits constraint can be extended to child Accounts A business entity/company if the Org has a Parent- Child Account hierarchy set up. This article covers how to set up Off Limits Account Policies and additional information regarding this type of Off Limits policy.
The Internal Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Rule Exception is the one notable exception to this. For more details see the section The Internal Candidate Rule Exception.
Creating an Off Limits Account Policy
- Navigate to the Off Limit Policies Related List on the relevant Account record.
- Click the New button.
- The new Off Limit Policy page will open in Edit mode with Record Type field and the Account Lookup field pre-populated.
- Choose the Account policy configuration from the options below:
| Field Name | API API, or Application Programming Interface, is used by customers to create custom career portals or to take advantage of Data Mirror/DataMart. Bullhorn prefers to use REST API. Name |
Field Type | Description | Supports Updates |
|---|---|---|---|---|
| Description | TR1__Description__c | Text(255) | General description of the policy. | Yes |
| Reason | TR1__Reason__c | Text(255) |
The name / short description of this policy. The value in this field is shown in the Off Limits warning/block popup to inform users why the Contact they selected is Off Limit. This field is required at database level and must always be populated. If not, even when removed from the layout, users will not be able to save the policy. |
Yes |
| Legal Reason | TR1__Legal_Reason__c | Text(255) | Legal reason for enforcing this policy, if relevant. | Yes |
| Type | TR1__Type__c |
Picklist |
The behavior enforced at checkpoints when an Off Limits Contact is selected for some actions. The options are Block or Warning. | Yes. If the value is changed on an existing policy, the change is only propagated to Line Items created afterwards. |
| Start Date | TR1__Start_Date__c | Date | The date when the policy starts taking effect. If no value is added manually, it defaults to today. | Yes |
| End Date | TR1__End_Date__c | Date | The date when this policy ends. If no value is added manually, it is populated with today's date when the policy is disabled. The end date can be extended at any time by updating this field. | Yes |
| Active | TR1__Active__c | Checkbox | Flag that shows whether the policy is active or not. If unchecked, the policy and all related Off Limits Line Items are disabled. |
Yes |
| Excluded Contact IDs | TR1__Exclude_Contact_Ids__c | Text(255) | Users can enter a comma separated list of Contact IDs that are excluded from the Account policy being applied. This is used to exclude individual Contacts A contact (or client contact) is the person who the recruiter is working with at a Company. In Talent Rover a Contact can be either a Client Contact or a Candidate Contact. Both types of Contacts are stored in the same object (Contact). from the saved Account policy. |
Yes |
The policy is applied to the selected Account and to all Contacts that have Employment History records meeting these conditions:
- Account field: Account nominated in the policy
- Current checkbox: True
- Verified checkbox: True
The Internal Candidate Rule
One key exception to the Account limits policy is when a candidate cannot be considered due to their current employer being a client. In this case, an existing Off Limit Account Policy is already in place, and the candidate is off limits because they work for that company. However, this exception does not apply if the candidate applies for a position A job (vacancy, position, role) is an opening for which a customer's client needs a placement. with their current employer, unless the candidate is off limits due to other policies. This exception is factored in the Off Limits logic.
Example
Scenario A
In this scenario, we will see the off limits logic applied to a candidate who has an Off Limits Account Policy.
- Candidate Jamie Smith is employed by Acme.
- Candidate Jamie Smith is off limits because there is an Off Limits Account policy is in the system for the Company Acme.
Resulting Logic Behavior
- Allowed: Candidate Jamie Smith is allowed to apply to a job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. inside the Acme company. They are able to move forward in the hiring process.
- Exceptions to this are when an applicant A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. is off limits based on other constraints
- Exceptions to this are when an applicant
- Not Allowed: Candidate Jamie Smith is not allowed to apply for a job for any other Company except Acme. Hiring Process stopped.
Scenario B
In this scenario, we will see the off limits logic applied to a candidate who has any other off limit policy applied.
- Candidate Jamie Smith is employed by Acme.
- Candidate Jamie Smith is off limits because there is an any policy other than an Account policy for the Company Acme in the system.
Resulting Logic Behavior
- Not Allowed: Candidate Jamie Smith is not allowed to apply for a job inside the Acme company. Hiring Process stopped.
Additional Information
Employment History Records: Current Checkbox
The Employment History "Current" checkbox is used to mark the Employment History record related to the current position of the Candidate.
The following is used to identify the current job using Employment History:
- Excludes everything where the End Date is in the past.
- If the End Date is in the future, mark as Current.
- If the End Date is blank, mark as Current only if there is a Start Date.
- If End Date is a string like "present", mark as Current only if there is a Start Date.
Child Accounts
This functionality supports only a first level of Account Hierarchy (only child accounts of the selected parent account and no further levels in the hierarchy).
If an Org uses Salesforce’s Account Hierarchy, when the Off Limit Account policy edit page opens, users will see a Child Accounts button at the bottom of the page. Upon clicking that button, a popup allows users to select any child account (one or multiple) and apply the same Account policy to all selected child accounts.
If child accounts are selected, the list is visible at the bottom of the page before saving the record.
The data shown on the Child Accounts pop-up is configurable. For more details see Off Limits Configuration Guide.