Module 1 - Configure Customer Applications and ATS Integrations (Customer Onboarding )


Customers who elect to enable RSC must be able to sync all historical candidates, applications, and jobs during the onboarding process. If additional filters, variations, or modifications from this expectation are built into the application, partners must obtain approval via writing from their LinkedIn's Business Development Representative.

Rule Execution Steps Expected Result
RSC-101 Demonstrate a new customer implementing RSC for the first time. The test admin will see the appropriately named integration in Recruiter and will be able to enable it.
RSC-102 Demonstrate that a customer should be able to configure the job availability type as PUBLIC or PRIVATE for the jobs synced. Ensure that the ATS provides an option for the customer to choose the job availability type (PUBLIC or PRIVATE). If a partner cannot provide this choice, they should post jobs of type PRIVATE_TO_ATS_INTEGRATION only.
RSC-103 Multiple Recruiter contracts onboarding.
    For partners utilizing provisioning, demonstrate each customer has a unique developer application, and each developer application maps to 1 customer instance. Complete the onboarding experience in two unique instances.
    Customers can enable RSC for multiple recruiter contracts simultaneously. Developer applications are created for instances using a unique foreign ID of the instance and are used on behalf of a single instance. Activation for each instance and API traffic corresponds to the API credentials created for that instance.
    RSC-104 atsIntegration configuration settings are properly stored. Demonstrate that the atsIntegration configuration setting for callback_url is set. JOB_POSTING_VIEWER, APPLICATIOIN_VIEWER is set to “ALL_PRODUCT_USERS“ if there’s no ACL setting.
    RSC-105 Set the JS SDK domain for the provisioned application. Demonstrate in developer portal or in a provisioning API call response that the JS SDK domain is correctly set for to a domain hosting your solution for the customer's developer application.
    RSC-106 Demonstrate access token generation, validation checking. Demonstrate ability to periodically verify that an access token is valid.
      Demonstrate ability to detect access token expiry.
        Demonstrate ability to retrigger OAuth 2.0 Client Credentials flow in case token has expired or been invalidated.
        RSC-107 Partner agrees to participate in a recorded demo with LinkedIn where they demonstrate all core feature functionality of their ATS. If partner was flagged for a TOS violation that they agreed to remediate as a condition of the partnership, they must demonstrate that the violation has been remediated.
        RSC-108 Support for version API. Demonstrate or explain what changes will need to take place to facilitate migration to versioned endpoints. Versioning migration path clearly understood by LinkedIn. Switching consumption to versioned endpoints requires minimal development support.

        Relevant Documentation: Customer Configuration