---
title: "Display content using SSO based User Attributes"
slug: "display-content-using-sso-based-user-attributes"
updated: 2025-11-03T03:08:01Z
published: 2025-11-03T03:08:01Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Display content using SSO based User Attributes

### Overview

Previously, role-based segmentation relied heavily on window variables to identify user roles, increasing the difficulty in identifying the right window variable for each use case. Extracting variables from a website isn't always accurate; frequent changes to the underlying application can break the process, and integration setups can be tricky and time-consuming.

> [!WARNING]
> Your title goes here
> 
> The SSO-based User attributes capturing is a Beta feature. To enable this feature, contact [support@whatfix.com](mailto:support@whatfix.com?subject=SSO-based%20user%20attributes%20capturing&body=Hi%2C%0A%0APlease%20enable%20SSO-based%20user%20attributes%20capturing%20for%20the%20following%20account%3A%0A%0A).

To improve the accuracy and reliability of role-based segmentation, Whatfix enables you to fetch Single Sign-On (SSO) attributes and map them to User attributes. Once fetched and added as a User attribute, you can use them in Cohorts, Visibility Rules and Product Analytics filters.

Use the User Attributes to display content or track analytics for a specific set of users. For example, SSO-based User attributes enable you to display a reward program Pop-up just for the HR team of your organization or create a Cohort of users within the sales department to track sales-specific feature engagement.

> [!WARNING]
> Prerequisites before you enable end user SSO attribute capturing:
> 
> 
> 
> - You must configure and enable End-user authentication before you capture SSO attributes. For more information, see [End-user authentication](/studio/docs/end-user-authentication-for-browser-extensions).
> - Capturing of SSO attributes must be allowed by your Identity Provider (IdP).
> - New Visibility Rules feature must be enabled on your account. To enable this feature, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Enable%20Advanced%20Visibility%20Rules&body=Hi%2C%0A%0APlease%20enable%20the%20advanced%20visibility%20rules%20feature%20on%20the%20following%20account%3A%0A%0A).

### Step 1: Configure SSO Attributes

Use the following steps to enable end-user authentication and map SSO-based attributes with user attributes:

1. On the Whatfix Guidance dashboard, click **Settings**.  

![ia_settings_without_auto_testing](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/ia_settings_without_auto_testing.png)

1. Click **End-user authentication**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/click_settings_eua.jpg)
2. Click **Configure end-user authentication**. ![settings_eua_page](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/settings_eua_page.jpg)
3. Enable the **End-user authentication** toggle. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua_enable_toggle.jpg)

> [!WARNING]
> Your title goes here
> 
> Once you enable **End-user authentication**, ensure you perform a [Push to production](/studio/docs/pushing-whatfix-content-to-production), and then resume from Step 5.
4. Click **+ Add attribute**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua__plus_add_attribute.jpg)
5. In the **Add attributes** dialog box, enter a **User attribute** name. For example, **Employee_Type**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua_user_attribuite(1).jpg)

> [!WARNING]
> Your title goes here
> 
> To get the full list of all supported SSO-based user attributes, contact your IT team.
6. Select the **SSO attribute** you want to map to the User attribute. For example, **UserType**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua_sso_attribuite(1).jpg)

> [!NOTE]
> Your title goes here
> 
> Click the **Add** and **Remove** icons to add map more attributes: ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua_plus_minus_icons(1).jpg)
7. Click **Add attribute**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua_add_attribute_dialog_box(1).jpg)

> [!NOTE]
> Your title goes here
> 
> Once you’ve added the User attributes and the corresponding SSO attributes, click the **Edit** or **Delete** icons to manage the attributes. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/eua_added_attributes(1).jpg)

### Step 2: Use the SSO-based User Attributes for Role Segmentation

SSO-based User attributes work similarly to role tags. Use these attributes to display content for a specific set of audience. Once you have enabled End-user authentication and configured SSO-based user attributes, you can add User attributes as a Visibility Rule. The following example shows a Pop-up to full-time employees on an application. Use the same steps to map the User attribute as Visibility rules in other widgets as well.

Use the following steps to add the mapped User attribute as a Visibility rule:

1. Go to the **Set Visibility Rules** section of any widget that you want to edit.
2. In the **Visibility rules** section for your widget, click **Who does the pop-up appear?**

![Visibility Rules 2.0 Screenshots](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/vr2_who%20does%20the%20widget%20appear%20to.png)
3. In the **Who does it appear to?** dropdown, select **user attributes**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/vr_user_attributes.jpg)
4. Select the User attribute that you’ve mapped to the SSO attribute. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/vr_who_select_attribute.jpg)
5. Add the **Check if Attribute** condition and then enter the **Value**.

![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/vr_user_attribute_condition_details(1).jpg)
6. Once you have added all the required Visibility Rules, click **Save**.![vr2_save visibility rules](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/vr2_save%20visibility%20rules.png)
7. Finish creating the widget, and then click **Save**.

![vr2_save widget](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/vr2_save%20widget.png)

> [!NOTE]
> Your title goes here
> 
> Preview the content using Preview mode and push the widget to Production.

#### SSO-based user attributes in Product Analytics

The user attributes you have mapped on the Whatfix Guidance Dashboard can be used to drill down on the data and create Cohorts to group users having the same characteristics.

User Attributes provide information about the characteristics of your users, like who they are, what their role is, which department they belong to, etc.

An Identity Provider (IdP) is an authority system that holds and verifies user authentication information.