NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm
Configuring HRP For Use With The PrismHR API
There are two parts of the PrismHR API configuration to complete before integration with ClientSpace can take place: A ClientSpace configuration that will likely be completed by PrismHR, and an HRP configuration that should be handled by you, the client with help from PrismHR if necessary. This document describes the necessary HRP Site configuration that should take place prior to going live with the PrismHR API.
HRP Site
The HRP Site must be configured with the following parameters before use of the API can commence:
- Valid User account
- Username (case sensitive)
- Password (case sensitive)
- PEO ID (case sensitive)
- HRP API URL. The endpoint of the WSDL on the server to be used.
- The Account must be Enabled
- The Account must have permission to create subscriptions (for Imports only). The following subscriptions will be automatically created on the HRP server when the process first executes:
- Employee/Person|Client|Compensation. Description is: “ClientSpace Employee Person-Client-Compensation Subscription All Clients”
- Client/Master|Location. Description is "ClientSpace Client master Subscription All Clients”
Certain Companies/Employees should not be imported into ClientSpace (e.g., the PEO itself). The HRP Configuration tool (HRPyramid) contains a Web Services Access Control interface. Those Companies that should not be imported into ClientSpace should be listed as Deny on the Company List form. To do so perform the following steps in the HRP Configuration tool:
Web Services Company ‘blacklist’.
Related articles
NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm