Skip to main content

Integrate Rippling with Kisi

info

This is a Kisi-built integration, maintained and supported by Kisi.

The Rippling integration with Kisi allows you to automatically sync your Rippling accounts with Kisi and simplify access control in your office.

Prerequisites​

  • a Kisi organization owner account
  • a valid and activated SSO license

Before setting up the integration, ensure you are logged in as the Kisi organization owner and have a valid, activated SSO license. If these prerequisites are met and the SSO & SCIM option is still not visible on the dashboard, please reach out to Kisi Support for assistance.

Set up SSO on Rippling​

  1. Sign in to Rippling
  2. Search for Kisi. Install it and follow the setup instructions (If you have already installed Kisi, skip this step)
  3. Click on SSO Setup
  4. Copy the IdP Metadata URL in the
  5. Fill out the following fields in the SSO Setup Screen section:
    • Provide the Assertion Consumer Service (ACS) URL: https://api.kisi.io/saml/consume/<your-kisi-domain>. You can find your Kisi organization domain under Settings > General.
    • Provide the Service Provider Entity ID: https://api.kisi.io/saml/metadata
  6. Click Move to Next Step
  7. Select your desired Rippling configurations for the SSO rules and click Continue

Set up the integration in Kisi​​

  1. Sign in to Kisi as the organization owner
  2. Under Settings, click on SSO & SCIM
  3. Paste the IdP Metadata URL that you saved in the step above into the Metadata URL field. You can find the Metadata URL in the Kisi app settings in Rippling > Advanced SAML Settings > Metadata
  4. Click Save

Manage groups in Kisi​

Once the integration is set up, you can import your Kisi groups into Rippling. Configure your groups using specific employee names, or by fields in Rippling such as department, role, employment status, or management level.

Flexible authentication: SSO or password​

Kisi organizations with Single Sign-On (SSO) enabled can, if needed, also enable authentication with password for users. If enabled, the user will be able to log in with email and password. If the user is in the organizations' IdP directory, an SSO login will also be available.

User removal impact on event logs​

If you're utilizing a Single Sign-On (SSO) platform and an employee is removed, upon reviewing the Event history, the logs related to that user will continue displaying the user's name, even though they've been removed from the system.