> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/team/rippling-sso.md).

# Rippling SSO Configuration

Configure Rippling SAML single sign-on for your AirOps workspace, map employee attributes, and test sign-in from AirOps and Rippling.

Connect Rippling to your AirOps workspace so employees can sign in with their Rippling account. An admin configures the connection once, then assigns the AirOps app to employees in Rippling.

The setup exchanges two sets of values: AirOps provides the destination URLs, and Rippling provides the identity provider metadata.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-807c59ee1a49bf7780e4ef92a4d971913c5ecb3b%2Frippling-sso-00-overview.png?alt=media" alt="Copy the ACS URL and SP entity ID from AirOps to Rippling, then import Rippling IdP metadata XML into AirOps"><figcaption><p>Keep both admin pages open. You will copy values in each direction.</p></figcaption></figure>

## Before you start

You need:

* An AirOps workspace with Rippling SSO enabled and permission to manage SSO settings. Contact your AirOps account team if Rippling is missing from the provider list.
* Permission to create and configure a custom SAML application in your Rippling company.
* An employee you can assign for testing, with a work email and first name in Rippling.

Keep your current AirOps admin session open while testing in a separate browser profile or private window.

## How to Configure

Follow these steps in order. Keep AirOps and Rippling open in separate tabs so you can exchange the connection details before testing sign-in. Each annotated onboarding screenshot includes numbered callouts for the controls to use. Click an image to enlarge it.

### 1. Copy the connection details from AirOps

In your **AirOps** tab:

1. Open **Settings → Single Sign On**.
2. Find **Rippling** and click **Configure**.
3. Copy the **ACS URL** and **SP entity ID**. Keep this form open; you will return to it in step 8.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-5966527e78da4fd419065326b0e64f32be85e3fc%2Fsso-rippling-01-connection.png?alt=media" alt="Add Rippling SAML connection dialog with the ACS URL and SP entity ID and their copy buttons"><figcaption><p>Copy both values from your own workspace.</p></figcaption></figure>

### 2. Start a custom integration in Rippling

Switch to **Rippling**:

1. Open **IT → Third-Party Access**.
2. Click **Add integration**.
3. Select **Create new custom integration**.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-671cecbb4b87af80cf2de7c97963c58b8476322d%2Frippling-sso-02-add-integration.jpg?alt=media" alt="Rippling Add integration menu with Create new custom integration"><figcaption><p>Open the custom integration creation form.</p></figcaption></figure>

### 3. Enter the app name, category, and logo

On **Create new integration**, fill in:

| Field                 | What to enter                                                   |
| --------------------- | --------------------------------------------------------------- |
| **Name**              | A recognizable name, such as `AirOps SSO`.                      |
| **Select categories** | Choose a category, such as **Productivity**.                    |
| **Upload logo**       | Upload the logo you want employees to see on their AirOps tile. |

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-2805edfe525c635b5fa076a3d473b83eb8e383d2%2Frippling-sso-app-details-full.svg?alt=media" alt="Rippling Create new integration form showing the app Name, Productivity category, and an uploaded logo"><figcaption><p>The example app is named AirOps SSO. Choose a name employees will recognize.</p></figcaption></figure>

Stay on this page and scroll down to **Custom integration type**.

### 4. Select SAML single sign-on

In the lower part of the same form:

1. Select **User access integration**.
2. Under **Capabilities**, check **Single sign-on**.
3. Choose **SAML** in the dropdown that appears.
4. Leave **Account provisioning and deprovisioning via SCIM** unchecked.
5. Enable **Supports just-in-time provisioning** if employees should receive an AirOps account at their first successful sign-in. AirOps sign-up restrictions still apply.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-310ae5bc1a46256990da53bf9d08fe0ce787b71a%2Frippling-sso-app-saml-full.svg?alt=media" alt="Rippling form with User access integration selected, Single sign-on checked, SAML selected, SCIM unchecked, and just-in-time provisioning enabled"><figcaption><p>Select the SAML capability and the provisioning behavior for your rollout.</p></figcaption></figure>

Click **Continue** to create the integration.

### 5. Choose the installer

On **Select an installer**:

1. Select **Yes, I'll install this integration** if you manage the AirOps integration for your company.
2. Click **Continue** to reach **SSO setup instructions**.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-9866733f83400a6d74636dba862b0821f38f6482%2Frippling-sso-installer-full.svg?alt=media" alt="Rippling installer selection screen with numbered callouts for choosing the installer and continuing"><figcaption><p>Select the person who will configure the connection. The screenshot shows the form before a choice is made.</p></figcaption></figure>

For an existing installation, open **Access → Single sign-on (SSO) → Configuration** and click **Reconfigure** under **General** to reopen the wizard.

### 6. Copy or download Rippling's metadata XML

On **SSO setup instructions**, find **Step 1 - Enter SAML configuration fields**, then locate **IdP Metadata**. This XML contains the Rippling connection details AirOps needs.

Choose one option:

* **Download the XML:** Click the download icon to the right of **IdP Metadata** and save the file. You will upload it to AirOps in step 8.
* **Copy the XML:** Copy the complete XML contents from **IdP Metadata**. Switch to your AirOps tab and paste them into **Or paste metadata XML** now, then return to Rippling. Keep the AirOps form open.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-44ef5f9ff6b79bd19ac24d3bda9c7ad150213073%2Frippling-sso-05-rippling-metadata.jpg?alt=media" alt="Rippling IdP Metadata section showing the XML contents and its download icon"><figcaption><p>Copy or download the complete IdP metadata XML for the AirOps configuration.</p></figcaption></figure>

For an installed app, the download is also available under **Access → Single sign-on (SSO) → Configuration → Metadata → Metadata XML**.

Keep the Rippling setup page open to enter the AirOps URLs next.

### 7. Paste the AirOps URLs into Rippling

On the same **SSO setup instructions** page, scroll to **Step 2 - Provide Service Provider Metadata**. Copy each value from the AirOps form into its matching Rippling field:

| Rippling field                     | Value to paste                |
| ---------------------------------- | ----------------------------- |
| **Assertion Consumer Service URL** | Your AirOps **ACS URL**.      |
| **Service Provider Entity ID**     | Your AirOps **SP entity ID**. |

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-fc52a7014db2a452acddf222c3546301e832bef4%2Frippling-sso-02-rippling-endpoints.jpg?alt=media" alt="Rippling SSO setup instructions showing Assertion Consumer Service URL and Service Provider Entity ID"><figcaption><p>The screenshot shows example URLs from one AirOps workspace. Copy the generated URLs for your own workspace and environment.</p></figcaption></figure>

These two fields supply the service provider metadata. You can leave the alternative **Metadata url** and **Metadata** inputs empty when using this method.

Leave Rippling open and switch back to AirOps.

### 8. Save the connection in AirOps

In the AirOps form you left open:

1. If you downloaded the XML in step 6, choose **Upload IdP metadata XML** and select the file. If you copied it, use the contents already pasted into **Or paste metadata XML**.
2. Click **Review metadata**.
3. Check the imported **IdP entity ID**, **SSO URL**, and **Signing certificates**.
4. Enter the exact attribute names configured in your Rippling app. **The names below are examples; your app may use different names.** See [step 16: Configure the employee attributes](#16-configure-the-employee-attributes) to check or create them before testing sign-in.

| AirOps field                       | Example          | What to enter for your connection                                                               |
| ---------------------------------- | ---------------- | ----------------------------------------------------------------------------------------------- |
| **NameID format**                  | **emailAddress** | The same NameID format configured in Rippling.                                                  |
| **Work email attribute**           | `emailAddress`   | The exact attribute name Rippling uses to send the employee's work email.                       |
| **First name attribute**           | `firstName`      | The exact attribute name Rippling uses to send the employee's first name.                       |
| **Last name attribute (optional)** | `lastName`       | The exact attribute name Rippling uses to send the employee's last name. Leave blank if unused. |
| **Default role**                   | **Member**       | Choose the AirOps role new workspace members should receive.                                    |

These fields contain attribute names. Rippling supplies the employee's actual email and name when they sign in.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-a73f137f2c676a7da8f47c82cc2f5b0a3f8f5ead%2Fsso-rippling-02-attributes.png?alt=media" alt="Rippling SAML connection with NameID format emailAddress, the emailAddress, firstName, and lastName attributes, and Member as the default role"><figcaption><p>Example configuration. Use your Rippling attribute names and choose the AirOps role for new members.</p></figcaption></figure>

Click **Add connection**. Confirm that AirOps displays **Rippling connection saved.**

{% hint style="info" %}
The imported **IdP entity ID** identifies Rippling. The **SP entity ID** you copied in step 1 identifies the AirOps workspace. Each belongs on its own side of the connection.
{% endhint %}

### 9. Set the SSO app access rules

Return to the Rippling **SSO setup instructions** page and click **Move to Next Step**. On **SSO app access rules**, choose who should receive the AirOps app:

1. Use **Assign a group** to assign your pilot group, or **Assign an individual** to assign your test employee. You can use either method.
2. Review **Assigned groups**, **Assigned individuals**, and **Exclusions**. Keep the initial assignment limited to the people in your pilot.
3. Click **Continue**.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-dddcad45377a78d57a8daa11cbd0c244500afba0%2Frippling-sso-access-rules-full.svg?alt=media" alt="Full Rippling SSO app access rules screen with numbered boxes and arrows around the group assignment, individual assignment, and Continue controls"><figcaption><p>Assign the app to your test employee or pilot group. SSO eligibility is a separate choice in step 14.</p></figcaption></figure>

### 10. Review access timing

On **Provision time**, **New hire access time** determines when someone who matches the app's access rules becomes eligible for access.

| Option                                                        | When access becomes available                                     |
| ------------------------------------------------------------- | ----------------------------------------------------------------- |
| **As soon as they've signed their offer letter or agreement** | After the employee signs their offer or agreement.                |
| **On their start date, not before**                           | On the employee's start date.                                     |
| **A fixed time before their start date**                      | At the interval you configure before the employee's start date.   |
| **As soon as the admin hires them**                           | When the admin hires the employee, before they sign an agreement. |

Select the timing that fits your organization's onboarding and access policies, then click **Continue**. AirOps creates an eligible new account at the first successful sign-in, subject to sign-up restrictions.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-48af3406e4495e5a900210991f747f681e9e8ff6%2Frippling-sso-provision-time-full.svg?alt=media" alt="Full Rippling Provision time screen highlighting the available access timing options and Continue"><figcaption><p>The selected option is an example. Choose the timing that fits your organization's policies.</p></figcaption></figure>

### 11. Review admin SSO options

On **SSO for admin**, Rippling asks whether your company's Rippling admins should be able to sign in to a shared AirOps admin account.

| Option                                                                    | What it controls                                                                                |
| ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Let \[your company] admins sign in to \[your app] admin account**       | Rippling offers full admins access to the account designated as the app's shared admin account. |
| **Don't let \[your company] admins sign in to \[your app] admin account** | Leaves shared admin access disabled. Admins can still use SSO with their individual accounts.   |

For this setup, we recommend selecting **Don't let \[your company] admins sign in to \[your app] admin account** so each person signs in with their own AirOps account. AirOps admins can still use SSO and keep their assigned workspace roles.

After reviewing the setting, click **Continue**. Manage individual users' workspace roles in AirOps.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-db7c7ba0da198a6319fb2f9847411972a2085ece%2Frippling-sso-admin-sso-full.svg?alt=media" alt="Full Rippling Shared Admin SSO screen highlighting the recommended Don&#x27;t let option and Continue"><figcaption><p>The screenshot shows the recommended choice for this setup. The company and app names will match your integration.</p></figcaption></figure>

### 12. Review optional group attributes

**Group attributes** let Rippling include group-related values in the SAML sign-in response. For example, a `groups` attribute could send `Engineering` for employees in your Engineering group.

Review any group attributes already configured for your app. If your organization's SAML setup calls for additional group information, use **Create new** to define the values and the people they apply to. You can also continue without adding group attributes.

For AirOps, these attributes are optional and do not assign workspace roles. New workspace members receive the **Default role** selected in step 8; existing active members keep their roles. App assignments and SSO eligibility are configured separately in steps 9 and 14. Employee email and name attributes are configured in step 16.

After reviewing the configuration, click **Continue**.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-1fe53e2abbc0baa7c71d5f6ba24496abb90fd253%2Frippling-sso-group-attributes-full.svg?alt=media" alt="Full Rippling Group attributes screen for AirOps SSO showing no configured group attributes and highlighting Continue"><figcaption><p>This example has no group attributes configured. Configure optional values to fit your organization's setup.</p></figcaption></figure>

### 13. Defer the initial connection test

The **Verify SSO integration** step displays **Test Rippling's connection to \[your app]** and a **Connect via Rippling** button.

The employee attributes and dashboard settings still need to be reviewed after installation. Click **Continue** for now and return to this test in step 19. Continuing past this screen does not confirm a successful sign-in.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-5349c853c1ae22549b809c3df02ffdae1b7d5599%2Frippling-sso-connection-test-full.svg?alt=media" alt="Full Test Rippling&#x27;s connection screen highlighting only Continue"><figcaption><p>Click Continue to keep setting up the app. Run the connection test in step 19.</p></figcaption></figure>

{% hint style="info" %}
Rippling's generic test text mentions creating and deactivating users. This SAML setup creates eligible new AirOps accounts at sign-in. It does not configure SCIM or automatically remove AirOps membership when a Rippling assignment is removed.
{% endhint %}

### 14. Choose which assigned users can sign in with SSO

On **SSO Eligibility**, the page asks **Which assigned users can sign in with SSO?**:

1. Choose **All assigned users** if everyone assigned in step 9 should use SSO. To test SSO with a smaller subset of the app's assigned users, choose **Only selected assigned users** and include your test employee in the rules that appear.
2. Review **Exclude users (optional)** and check that your test employee is not excluded. Use **Preview people** to check the result of any rules.
3. Click **Continue**.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-884b2ba441aa1c86691228b058c0bf61ca4f9eea%2Frippling-sso-sso-eligibility-full.svg?alt=media" alt="Full Rippling SSO Eligibility screen highlighting All assigned users or Only selected assigned users, exclusion rules, and Continue"><figcaption><p>An employee must have both an app assignment and SSO eligibility. The screenshot shows All assigned users selected.</p></figcaption></figure>

### 15. Finish installation and open Configuration

Complete any remaining prompts Rippling presents for your installation. When you reach **\[your app] installation complete**, click **Go to integration**.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-072c9125d3994f115872f7d80cc343547028ed95%2Frippling-sso-installation-complete-full.svg?alt=media" alt="Full Rippling installation complete screen with a numbered arrow pointing to Go to integration"><figcaption><p>Open the installed app to review its employee attributes and advanced settings.</p></figcaption></figure>

In your AirOps integration:

1. Select **Access**.
2. Select **Single sign-on (SSO)**.
3. Open **Configuration**.

Keep this page open for the employee attributes and advanced settings below.

### 16. Configure the employee attributes

In **Rippling**, open your AirOps integration and go to **Access → Single sign-on (SSO) → Configuration → SAML attributes**.

First, find the attributes for work email, first name, and optional last name in the **Name** column. Reuse existing attributes and create only the mappings that are missing.

The table below shows example names and employee fields. Your attribute names may differ; each name must match the corresponding field in AirOps.

| AirOps field from step 8           | Example Rippling attribute name | Example Rippling employee value                                                              |
| ---------------------------------- | ------------------------------- | -------------------------------------------------------------------------------------------- |
| **Work email attribute**           | `emailAddress`                  | **User's email address**, containing the employee's work email.                              |
| **First name attribute**           | `firstName`                     | **User's Preferred first name**.                                                             |
| **Last name attribute (optional)** | `lastName`                      | **User's Preferred last name**. Omit this mapping if the last-name field is blank in AirOps. |

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-866aef3dabc10630713be92a856b5e67790c2b0b%2Frippling-sso-03-rippling-attributes.jpg?alt=media" alt="Rippling SAML attributes table showing emailAddress, firstName, and lastName mapped to employee fields"><figcaption><p>AirOps SSO uses preferred first and last names in this example. The Name column must match the attribute names saved in AirOps.</p></figcaption></figure>

**Create a missing attribute**

For each missing row:

1. Click **Create new** in **SAML attributes**.
2. On **Create SAML attribute**, select **Global attribute**. This lets you map an employee field for each person signing in.
3. In **Global attribute name**, enter the name you will also use in AirOps. For example, enter `firstName` for a new first-name mapping.
4. Open **Value** and select the corresponding employee field. For `firstName`, choose **User's Preferred first name**. Select the field from the dropdown so Rippling uses the value for the employee signing in.
5. Click **Save**, then check that the row appears under **SAML attributes**.
6. Repeat for any missing work-email or last-name mapping, using your chosen attribute names and the corresponding employee fields. The table shows `emailAddress` and `lastName` as examples. Skip any mapping that already exists.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-7ecfc5baa42f448c6bcaf8fb0a5dc607a772ddac%2Frippling-sso-create-employee-attribute-full.svg?alt=media" alt="Rippling Create SAML attribute form with numbered callouts for Global attribute, the firstName name, the dynamic Preferred first name value, and Save"><figcaption><p>Example of creating firstName when it is missing. Use the table above for emailAddress and lastName. The screenshot shows an unsaved form.</p></figcaption></figure>

**Check or correct an existing attribute**

1. Open the attribute row's menu and choose **Edit**.
2. Check **Value** against the table and select the matching employee field if needed.
3. Click **Save** if you changed the value. Repeat for the other existing attributes.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-f4a30675e85a29519c7a349ca5fb299c87fb8412%2Frippling-sso-03-rippling-attribute-editor.jpg?alt=media" alt="Rippling Edit SAML attribute dialog showing firstName and the Value dropdown set to User&#x27;s Preferred first name"><figcaption><p>Edit an existing row instead of creating a duplicate.</p></figcaption></figure>

**Match the names in AirOps**

The Rippling **Name** values must match the **Work email attribute**, **First name attribute**, and optional **Last name attribute** you saved in step 8. If you used different names, open **AirOps → Settings → Single Sign On → Rippling → Actions → Update Credentials**, enter those exact names, and click **Save connection**. Rippling fixes the names of its default attributes, so use the names your app actually sends.

{% hint style="info" %}
Names are case-sensitive. For example, if your Rippling work-email attribute is named `emailAddress`, enter `emailAddress` in AirOps and select **User's email address** as its dynamic value in Rippling. AirOps requires the email attribute even when NameID contains an email. The optional **Group attributes** screen in the onboarding wizard does not configure these employee identity fields.
{% endhint %}

### 17. Match the NameID format and signing settings

Scroll to **Advanced Settings** and click **Edit**.

The example in this guide uses **emailAddress** for **Default NameID format to be used**:

```
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
```

Choose the format that matches your AirOps connection. Keep **Default relay state** blank.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-f82be7ba5d74c0859f7e37906f25681c96d63f75%2Frippling-sso-04-nameid.jpg?alt=media" alt="Rippling advanced settings showing emailAddress as the default NameID format and a blank default relay state"><figcaption><p>Use the same NameID format in Rippling and AirOps.</p></figcaption></figure>

Check the remaining settings:

| Setting                             | Value                       |
| ----------------------------------- | --------------------------- |
| **Signing algorithm**               | **RSA-SHA256** recommended. |
| **Digest algorithm for assertions** | **SHA-256** recommended.    |
| **Encrypt assertions**              | **No**.                     |

AirOps requires a signed SAML assertion. Signing the response alone does not meet that requirement.

If you are updating an existing connection, retain its stable NameID value and format, and match them in AirOps. Stay in **Advanced Settings** for the next step.

### 18. Enable dashboard quick access

In the same **Advanced Settings** form, set:

| Setting                                                                                                   | Value                                     |
| --------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
| **Disable 'InResponseTo' field in assertions for IdP initiated SSO**                                      | **Yes**                                   |
| **Application only supports login initiated from the application, also referred to as SP initiated flow** | **No**                                    |
| **Disable automatic standardization of attributes**                                                       | **Yes**, to preserve the attribute names. |

Click **Save**, then reopen **Advanced Settings** and check the saved values.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-3f9e670465251d3f32189a17710105f6ad73e8d6%2Frippling-sso-04-rippling-quick-access.jpg?alt=media" alt="Saved Rippling advanced settings with Disable InResponseTo set to Yes and SP-initiated-only set to No"><figcaption><p>Confirm the two quick-access values after saving: Yes for Disable InResponseTo and No for SP-initiated-only.</p></figcaption></figure>

The `InResponseTo` option applies to dashboard launches. Responses to a sign-in started from AirOps must still match the original request. Rippling describes the available options in its [SAML SSO reference](https://developer.rippling.com/documentation/developer-portal/v2-guides/saml).

### 19. Test the completed connection

Both sides are now saved. Keep your AirOps admin session open and test sign-in in a separate browser profile or private window.

If you are connecting an existing AirOps account for the first time, follow [Connect an existing AirOps account](#connect-an-existing-airops-account) before testing a signed-out login.

**Sign in from AirOps**

1. Open the [AirOps sign-in page](https://app.airops.com/users/sign_in).
2. Click **Sign in with Rippling** to show the **Workspace slug** field.
3. Enter your AirOps workspace slug and click **Proceed**.
4. AirOps redirects you to Rippling. Sign in with your Rippling account and complete any authentication prompts. If you already have an active Rippling session, Rippling may continue without asking you to sign in again.
5. Rippling returns you to AirOps. Confirm that your workspace opens and that you can access it with the expected role.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-f3d9f24bd63e5db30df157e5f34454b28b7bfb33%2Frippling-sso-07-airops-sign-in.png?alt=media" alt="AirOps sign-in flow: choose Sign in with Rippling, enter the workspace slug and click Proceed, authenticate with Rippling, and return to the AirOps workspace"><figcaption><p>Select Sign in with Rippling, enter your workspace slug, and click Proceed.</p></figcaption></figure>

**Sign in from the Rippling dashboard**

1. Open Rippling and click the AirOps quick-access tile.
2. On the AirOps continuation page, click **Continue to workspace**.
3. Complete any Rippling sign-in prompts, then confirm that you reach the intended AirOps workspace.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-b7a06114c36d8a1488a5ea9348572d553091e8ca%2Frippling-sso-06-sign-in.png?alt=media" alt="Rippling quick-access flow: AirOps tile, Continue to workspace, Rippling verification, and AirOps workspace"><figcaption><p>The AirOps continuation page is an expected part of dashboard sign-in.</p></figcaption></figure>

**Revisit Rippling's connection test**

You can also return to the installation wizard's **Connect via Rippling** test:

1. Under **Configuration → General**, click **Reconfigure**.
2. Open the step selector at the top left and select **Verify SSO integration**.
3. Check the employee email shown on **Test Rippling's connection**, then click **Connect via Rippling**.
4. Complete sign-in. If AirOps shows **Continue to workspace**, click it and confirm that you reach the intended workspace.

If a test fails, check the configuration before treating the setup as complete. Completing the Rippling wizard alone does not verify the AirOps connection.

Check that a new member receives the configured default role and an existing active member keeps their role.

## AirOps configuration reference

| Field                              | What to enter                                                                                                          |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **ACS URL / SP entity ID**         | Generated by AirOps. Copy both into the Rippling SAML application.                                                     |
| **IdP metadata XML**               | Export from the matching Rippling application. Upload or paste a file up to 250 KB, then click **Review metadata**.    |
| **NameID format**                  | Match Rippling's format and use a stable employee identifier. Keep the identifier and format consistent after rollout. |
| **Work email attribute**           | Exact, case-sensitive SAML attribute name containing the employee's work email. Required.                              |
| **First name attribute**           | Exact SAML attribute name containing the employee's first name. Required.                                              |
| **Last name attribute (optional)** | Exact SAML attribute name containing the employee's last name. Leave blank if omitted.                                 |
| **Default role**                   | Role for new workspace members. Existing active members keep their current role.                                       |

To update a connection, open **Settings → Single Sign On → Rippling → Actions → Update Credentials**, make your changes, and click **Save connection**. Import fresh metadata when Rippling rotates its signing certificates, before the existing certificates expire.

## Sign-in examples

### Share sign-in instructions

Share the [AirOps sign-in page](https://app.airops.com/users/sign_in) and your workspace slug with employees. They can select **Sign in with Rippling**, enter the slug, and click **Proceed**.

Employees can also use the AirOps SAML tile on their Rippling dashboard.

### Connect an existing AirOps account

For the first Rippling sign-in on an existing AirOps account:

1. Sign in to AirOps using the account's current sign-in method.
2. In the **same browser profile**, open the AirOps SAML tile on your Rippling dashboard and click **Continue to workspace**.
3. Complete the Rippling sign-in using the matching work email.

After the account is linked, test a signed-out login. If AirOps asks you to use your original sign-in provider, contact your AirOps account team to arrange the transition.

### Understand membership behavior

AirOps creates a new account and workspace membership during the employee's first successful sign-in, subject to your workspace's sign-up restrictions. This SSO connection does not synchronize employee membership or roles through SCIM. Manage existing AirOps membership separately when removing access.

## Troubleshooting

| What you see                                                | What to check                                                                                                                                                                                                                                                                                                      |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Rippling** is missing from AirOps settings or sign-in     | Ask your AirOps account team to enable Rippling for the workspace.                                                                                                                                                                                                                                                 |
| **Rippling sign-in could not be verified**                  | Confirm the ACS URL and SP entity ID match the same AirOps workspace and environment. Recheck the metadata, certificate validity, NameID format, and signed-assertion setting. For dashboard launches, also check both quick-access toggles in step 18 and leave Default Relay State blank. Start a fresh attempt. |
| An email or first-name attribute is missing                 | Match the exact attribute names, including capitalization. Select employee fields as values in Rippling and confirm the assigned employee has those values populated.                                                                                                                                              |
| The quick-access tile opens the general AirOps sign-in page | Confirm the tile launches the SAML application, rather than a bookmark to the sign-in page. Reopen and verify the quick-access settings in step 18.                                                                                                                                                                |
| AirOps asks you to sign in to an existing account first     | Follow **Connect an existing AirOps account** above in the same browser profile.                                                                                                                                                                                                                                   |
| **Add connection** is unavailable                           | Import the metadata and click **Review metadata**. Review it again if you change the XML.                                                                                                                                                                                                                          |
| An existing member's role did not change                    | The default role applies to new members. Update the existing member's role in AirOps.                                                                                                                                                                                                                              |

If sign-in still fails, share the workspace slug, entry point, time of the attempt, and displayed error with AirOps support. Do not include a SAML response or session tokens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/your-workspace/team/rippling-sso.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
