Not only do we provide extensive integration via API’s and CSV with front and back office systems, we also offer integration with other 3rd parties such as mobile app providers, agency websites, managed service systems and agency client time and attendance systems.
As RSM InTime sits between the front office CRM and back office Finance Systems, seamless data flow between systems is of course essential to achieve greater processing accuracy and efficiency. RSM InTime integrates with all main CRM recruitment systems and finance systems via CSV file import/export or web service API’s.
Web Service API Integration
Where possible we integrate via web service which can support, two- way, real-time integration. We have two-way web service integration with the following systems:
For FULL details of our Webservices API please use the following link:- Webservices API
It is possible for users to be automatically signed into RSM InTime from, for instance, your website portals for clients or candidates or for consultants via your CRM system. The web services interface allows external systems to request a token from RSM InTime. The external site adds this token onto the URL when the user clicks through to an RSM InTime link within the 3rd party system. RSM InTime will then automatically log the user in without the need for the user to enter a further username or password.
Implementing Single Sign On:
Single sign-on is achieved using the following process:
Your application requests an access token from the RSM InTime web services authenticate(java.lang.String agencyRefCode, java.lang.String username, java.lang.String password)
Your application requests a login token for a particular user getSingleSignOnToken(java.lang.String token, java.lang.String username, int timeToLiveSeconds)
It should be noted that the token has a limited life span, usually 20 minutes but with a maximum of 60 minutes. Tokens are one-use only.
IMPORTANT NOTE ON SECURITY: when single sign on capability is enabled for your site the password expiry for user accounts has to be disabled in RSM InTime. You are delegating authentication authority to your external system and must be aware of and take account of the security implications of this.
Ability to choose single sign on users
You can now choose which users are required to use single sign on. Withinsecurity settingswe have provided tick boxes that allow you to choose if groups of users must use single sign on. If not ticked users can use their username and password or single sign on. If ticked the users willonlybe able to use SSO.
You will also be able to apply mandatory SSO log in for individual users as well. Go to the user's profile and on the main tab you will see arequires SSOtick box. For all other users, the requires SSO tick box is at the bottom on the main tab page.
Please note:managers and providers cannot use OpenId/Okta/Azure SSO, but they can use web services SSO.
RSM InTime has the capability to pull in contract documents for delivery, tracking and e-signature from front office systems, such as Bullhorn and Influence.
Batch timesheet upload from VMS Systems or agency client timesheet systems
CSV import by agency admin. For quick upload and validation of timesheet data from CSV files generated by vendor managed systems and or client timesheet systems such as Fieldglass, Matrix, Comensura, Hays and De Poel. Whilst we have versions of these formats available, our experience is that these formats can differ. We therefore recommend sample files are provided for analysis.