Rippling helps businesses manage every employee system — Payroll, Benefits, Computers, Apps and more — all in one, modern platform. By connecting every system across the company to one employee system of record, businesses can automate all the manual work they normally have to do, to make employee changes. Take onboarding, for example. With Rippling, you can set up a new employees’ payroll, health insurance, laptop, and apps like Gmail & Slack — all in just 90 seconds.
Note
Only Rippling administrators can set up this integration. Only 15Five account admins can generate an API token.
What you’ll find in this article:
- How to set up the Rippling integration
- Using the integration
- How to disconnect
- FAQs
What's included in this integration?
- User & Role Provisioning:
- API based provisioning of new users in your application.
- When an employer hires (or terminates) an employee, Rippling will add them to (or remove them from) the 15Five app and configure settings based on their role.
- SSO/SAML:
- Users can access the 15Five app in a single click via Rippling SSO (SAML).
Note
The 15Five + Rippling integration is created and maintained via API token—not a SCIM token.
Prerequisites + Set up
Before you configure provisioning in Rippling... start in 15Five.
1. Click on your Settings menu at the top right of your 15Five account and then click 'Features'.
2. Last, click on 'Integrations'.
3. Click Enable to the right of the Public API option.
4. Once enabled, you'll land on the 'Company API keys' page. It looks like this.
5. Click the Create new key button.
6. Add in a short name for your API key. This name can be anything; usually, a name that is easily identifiable from your server-side. If you would like to limit the API access to High Fives only, check that box before saving.
7. Click Save to save your name and setting.
8. You will be redirected back to the 'Company API keys' page to verify your API key and access token.
The Public API key is 32 characters long. Not to be confused with the SCIM key, which is 30 characters long.
The endpoint for your API, assuming you do not have a unique subdomain, is my.15five.com.
9. Use the access token to link 15Five's API to your server.
In Rippling
After entering your API key into Rippling, you will be prompted to import performance data from 15Five.
- Select Yes, if you wish to use the 15Five integration directly within Rippling.
- If you select No, you will still be able to use the provisioning aspect of the 15Five integration, but will be unable to use 15Five itself directly from Rippling.
Adding users
Now that the connection is established with 15Five, you will configure the provisioning rules for your company’s use of 15Five.
1. This configuration step determines which users will automatically receive 15Five user accounts when a Rippling account is created, aka which users will be provisioned in 15Five when added to Rippling.
2. Choose the option that best fits your company's need for when people receive access to 15Five. This setting allows you to define when appropriate user accounts will be created and when access will be provided to your employees.
3. Match your pre-existing employee accounts in 15Five with your corresponding employee accounts in Rippling. In some cases, Rippling’s matching algorithm will not be able to identify an exact match. If this occurs, you should match your pre-existing 15Five accounts with the corresponding employee accounts in Rippling.
Creating groups
Add your employees, or groups of employees, to your 15Five groups. Groups need to be pre-created from directly within 15Five first to then show up in Rippling. If 15Five recognizes a new group name in the columns 'add_to_groups' or 'active_groups' from your import, these groups will be created upon import. Please exercise caution when you are assigning individuals or Rippling groups to groups in 15Five, as any group changes in Rippling will take place in 15Five as well.
Note
You can also manually synchronize your groups to retrieve the latest accounts from 15Five to associate with your Rippling groups.
Setting up SSO
Now that you’ve set up your API connection to 15Five, you will have the opportunity to set up SAML single sign-on for your employees as well. If you’d prefer to not set up SAML, you can select I’ll Do This Later in the bottom right corner or you can also leave SSO off for the duration of your account. If you choose not to enable SSO/SAML, people will be asked to create a password upon their first 15Five log in. Please follow the SAML instructions on screen in order to configure SAML for your account.
Note
15Five normally requires their Enterprise package for Single Sign On (SSO), but Rippling customers can access this feature for free. For questions/issues regarding setting up SSO with Rippling, reach out to support@15five.com.
If you decide to enable SAML for your 15Five account, it is strongly recommended that you require your employees to only use single sign-on to access the account. To do this, please proceed to the ‘Single Sign-on’ tab in 15Five under My Account. Underneath ‘SAML Single Sign-On’, please select Details. From here, ensure the 'Allow Password Sign In’ checkbox is unchecked. This will enforce your employees to sign in to 15Five through Rippling and is generally a good security practice for SAML-enabled applications.
Tip
Please ensure that you have tested your SSO configuration before enabling this to ensure that you do not get locked out of your account.
Performance data
To enable the Rippling 15Five integration for performance data, please select the 15Five dashboard and go to the ‘Settings’ tab. Click on the '15Five Options’ tab and click Edit. Then find the option ‘Important performance data from 15Five’, make sure it is set to 'Yes', and click Save.
Once users have been matched within the matching page, a new tab titled ‘Performance’ will be visible in the profile pages of users.
Using 15Five with Rippling
In addition to auto-provisioning and single sign-on, the integration with 15Five gains your company insights into your employee’s pulse information, OKRs, and reviews from within Rippling.
Pulse data
Pulse data and employee performance metrics are collected regularly in 15Five. Visit your 15Five account to manage your companies check-in reporting settings ie. cadence or check-in question. 15Five Pulse data is collected through automated surveys that are sent to your employees providing a 1-5 feedback scale. This information is then viewable in aggregated form for your company in Rippling under ‘Pulse Data’. Only 15Five admins are able to see this information from the Rippling application dashboard. 
Pulse data is viewable at an individual level from each employee's profile, which can be accessed from the ‘People’ tab as an admin and then selecting on the employee or by selecting ‘My profile’ as an employee.
Once you're on an employee’s (if you’re an admin) or your own profile page in Rippling, select ’15Five’. This allows you to view the individuals Pulse data, OKRs, and Review cycles, so long as you're are properly allowed to view this data based on 15Five permissions.
Objectives
Objectives or OKRs are your company’s objectives involving this employee within 15Five. These objectives show the time to completion, as well as the completion percentage as marked within the 15Five.
Reviews
Reviews shows the employee's Ended, Active, and Upcoming review cycles. The employees are able to view the review cycles they have and the cycle periods associated with each review cycle.
Note
For each data point mentioned, Rippling provides deep links to view the data from directly within 15Five.
Disable 15Five + Rippling integration
1. To disconnect your 15Five account, access your 15Five Application in Rippling and select ‘Settings’.
2. From the ‘Settings’ tab, find the ‘Manage App Accounts’ options. Click on the trash icon to remove the connection between 15Five and Rippling.
FAQs
Q: How do I create and manage users?
A: Connect 15Five with Rippling to automatically create and remove user accounts when you onboard and offboard employees. You can use smart rules to set configurations about who should have access to which administrative status– and when– so each employee gets 15Five access in addition to the correct permissions. If SSO/SAML is enabled, users will be able to access 15Five through Rippling. If SSO/SAML is not enabled, users will use their email and set a 15Five password to log in.
Q: How do I manage groups in 15Five?
A: You can automatically assign your employees to groups in 15Five, so every team is together. Configure your groups using specific employee names, or by fields in Rippling such as department, role, employment status, or management level.
Managing groups in 15Five takes your provisioning automation to the next level by allowing you to map your teams user accounts to the corresponding access types in 15Five. Groups in 15Five can also be used to ask group-specific questions on 15Five check-ins, pull reporting per group, configure unique settings for a group, and/or create group-type objectives.
Groups can be pre-created from directly within 15Five or groups can be created and members added simultaneously through your integration. If 15Five recognizes a new group name in the columns 'add_to_groups' or 'active_groups' from your import, these groups will be created upon import.
Q: What information is pushed to 15Five via SSO/SAML?
A:
- Employee Email
- Employee First Name
- Employee Last Name
- Employee Job Title
- Employee Reviewer Email (Manager)
- Employee Work Location
- Employee ID
Q: What information is pushed to 15Five via API?
A:
| Data Pushed to 15Five from Rippling | |
| Rippling Field | 15Five Field |
| first_name | first_name |
| last_name | last_name |
| job_title | title |
| pushState | is_active |
| manager_email | send_welcome_from |
| employee_id | employee_id |
| manager_email | review_email |
| work_location.nickname | location |
| Review Data Pulled from 15Five to Rippling | |
| Rippling Field | 15Five Field |
| all_participants | participants |
| spokeId | user_details.id |
| review_id | review_id |
| review_start_ts | cycle_start_ts |
| review_end_ts | cycle_end_ts |
| description | name |
| status | status |
| Objectives Data Pulled from 15Five to Rippling | |
| Rippling Field | 15Five Field |
| spokeId | objective_id |
| status | is_active |
| end_ts | end_ts |
| start_ts | start_ts |
| description | description |
| objectiveCompletePercentage | percentage |
| Pulse Data Pulled from 15Five to Rippling | |
| Rippling Field | 15Five Field |
| spokeId | pulse_id |
| created_ts | reporting_period_end |
| pulse_value | value |
| su_spoke_id | user |
Q: Who can view 15Five data in Rippling?
A:
| Type of Data | Which fields are used by Rippling | Where in Rippling is it shown? | Who can view the data? |
| Individual pulse data | The value and create_ts of all pulses | Profile page | Self, and admins with permission to view sensitive data |
| Individual’s objectives | The description, percentage, is_closed, start_ts, and end_ts of any objectives with scope=’individual’ | Profile page | Self, and admins with permission to view sensitive data |
| Individual’s review cycles | The name, cycle_start_ts, cycle_end_ts, status of review cycles, and number of completed reviews for individual. Does NOT include contents of actual reviews. | Profile page | Self, and admins with permission to view sensitive data |
| Aggregate pulse data | Pulse values averaged over the whole company, or filtered by department, location, etc. In practice, the user may be able to filter down to showing only a single person’s pulse data. | Rippling 15Five Application | Admins with permission to view sensitive data |
Q: How and when does data syncing occur between 15Five + Rippling?
A: All data fields are synced on any update to a user. Daily data syncing occurs at approximately 1:30am pst, but manual syncs can be triggered from directly within the Rippling 15Five Application at any time.