---
title: "Create a Blocker"
slug: "how-to-create-a-blocker"
updated: 2025-11-03T03:09:36Z
published: 2025-11-03T03:09:36Z
canonical: "support.whatfix.com/how-to-create-a-blocker"
---

> ## 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.

# Create a Blocker

Use the following steps to create a **Blocker** on Whatfix Studio and publish it through Whatfix Dashboard: For more information on **Blockers**, see [What’s a Blocker?](/studio/docs/improve-data-accuracy-and-user-compliance-with-blockers)

****Step 1. Create a Blocker on Whatfix Studio****

1. Log in to your application, and then launch the **[Whatfix Studio](/studio/docs/how-to-install-the-whatfix-editor)**.  

![CLM_editor plug in2](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/CLM_editor%20plug%20in%282%29.png)

1. Click **Blocker**. ![SelectBlocker_Widgets](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Widgets_SelectBlocker.png)
2. Enter a **Blocker Collection Name**. ![AddBlocker_Collectionname](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_Addcollectionname.png)

> [!NOTE]
> Info:
> 
> - A Blocker Collection is a group of Blockers created on the same page of an application.
> - The Blocker Collection name is solely for your reference and is not visible to the end user.
3. Click **+ Add Blocker** and then Select a UI element in the application that you want to block or disable.![AddBlocker](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_AddBlocker.png)
4. Select the Blocker type based on your requirement, either **Invisible blocker** or **Visible blocker**. ![Types_of_Blocker](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_Types.png)

> [!NOTE]
> Note:
> 
> Customize the **Appearance** of the Blocker type that you select.
> 
> - For **Invisible blocker**, you can change only the **Tooltip** type, **Color**, **Close (X)**, and **Close (X) colo**r.
> 
> ![Blocker_InvisibleOverlay_Appearance](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_InvisibleOverlay_Appearance.png)
> - For **Visible blocker**, you can choose not only the **Tooltip** type, **Color**, **Close (X),** and **Close (X) color**, but also the **Opacity** and **Grey filter** of the Blocker. ![Blocker_DisableElement_Appearance](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_DisableElement_Appearance.png)
5. Enter a description of the Blocker action. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Blocker_Tooltip_Description.png)

> [!NOTE]
> Info:
> 
> The Blocker description is visible to the end users when they hover their cursor over the element.

1. Click **Save**. ![Blocker_save](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_Save.png)
2. To save the Blocker collection, click **Save**. ![Save_Blockercollection](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Studio_Blocker_savecollection.png)

> [!NOTE]
> Info:
> 
> Once you have created the Blocker collection, a segment is automatically created on the Whatfix Dashboard. Go to the Widget section on the Dashboard and move the associated Blocker segment from Draft to Production.

> [!WARNING]
> Note:
> 
> **Blocker** is WCAG compliant and can be accessed and used by end users who rely on using assistive technologies such as screen readers. For more information, see [Accessibility in Whatfix](/studio/docs/accessibility-in-whatfix). To understand how end users with disabilities can access **Blockers**, see [Is the Blockers feature on Studio WCAG compliant?](/studio/docs/is-the-blockers-feature-on-studio-wcag-compliant)

****Step 2. Configure the Blocker segment on Whatfix Dashboard****

1. On the Whatfix Dashboard, click **Widgets**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Dashboard_Widgets_Click(2).png)
2. Click **Blockers**. ![Widgets_Blockers](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/DB_Widgets_Blockers.png)
3. In the **Draft** stage, hover your cursor over the auto-created segment, and then click the **Edit** icon. ![Blockers_Edit](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/DB_Blockers_Edit.png)
4. Click **Set Visibility Rules** and configure the Visibility Rules that determine how the Blocker collection appears to the end users.![Blockers_SetvisibilityRules](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/DB_Blockers_SetVisibilityRules.png)

> [!NOTE]
> Info:
> 
> To understand New Visibility Rules, see [Understand how content is shown based on New Visibility Rules](/studio/docs/understand-advanced-visibility-rules-behaviour).
5. Click **Save**. ![Blockers_save_visibilityrules](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/DB_Blockers_save_visibilityrules.png)
6. Once you have configured the Blocker segment, select the segment using the checkbox, and then click **Send to ready**.

![Sendtoready](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/clm_db_send_to_ready_button.png)
7. Go to the **Ready** stage, and then click **Publish**.

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

> [!WARNING]
> Note:
> 
> - Ensure that you push the widget first from the Widgets section, as this guarantees that the segment and its associated content are simultaneously pushed to Production. For more information on pushing a widget to Production, see [Push Whatfix content and widgets to Production](/studio/docs/pushing-whatfix-content-to-production).
