# Consent Management: Configuring Privacy Experiences

This tutorial requires Fides Cloud or Fides Enterprise. For more information, [talk to our solutions team.](/content/speak-with-us?utm_source=docs-site/index.html)

In this tutorial, we'll review privacy experiences, how they're configured, and how they're presented to visitors.

After reading this, you'll be familiar with how to configure privacy experiences and how privacy notices are presented within your privacy experiences to visitors based on their location.

## Prerequisites

For this tutorial you'll need:
- A Fides Cloud or Fides Enterprise account
- The role of `Owner` or `Contributor` for your Fides organization.
- At least one system with a data use on your Data Map. Read how to [add systems to the Data Map](/content/docs/data-mapping/guides/adding-systems-manually/index.html) now.
- At least one privacy notice configured. Read how to [configure privacy notices](/content/docs/consent/concepts/fundamentals/privacy-notices/index.html) now.

## What are Privacy Experiences?

A privacy experience in Fides is the user experience for how privacy notices are presented to a visitor based on the regulations that apply in the user's location.

Fides has three default privacy experiences, the **Banner+Modal**, the standalone **Modal** and the **Privacy Center**. Learn about [privacy experience fundamentals](/content/docs/consent/concepts/fundamentals/privacy-experiences/index.html) here.

## Viewing Privacy Experiences

To view privacy experiences in Fides, navigate to **Consent** → **Experiences** where you'll see a list of currently configured privacy experiences for your Fides account.

Each item on the list of privacy experiences consists of a title, component type, locations, properties, last updated date, and a toggle to enable it.

- **Title**: the name given to the privacy experience to identify it.
- **Component**: the type of privacy user experience.
- **Locations**: the locations this privacy experience is configured to be displayed.
- **Properties**: the properties to which the privacy experience is assigned.
- **Last update**: the last time the privacy experience was modified.
- **Enable**: a toggle to activate to deactivate the privacy experience. An inactive experience is not displayed to any visitor.

The **Get JavaScript tag** button allows you to copy your JavaScript tags for configuring front end consent. Learn how to [configure front end consent](/content/docs/consent/guides/index.html) here.

## Available Privacy Experiences

Fides has four default privacy experiences you can configure:

1. **Banner+Modal**: a banner and pop-up commonly used for opt-in cookie consent.
2. **Modal**: a pop-up often used for opt-out consent which is common in the United States.
3. **Privacy Center**: a privacy center typically available at `https://privacy.your-brand.com`.
4. **TCF Overlay** (if enabled): a privacy experience that is compliant with the IAB's Transparency and Consent Framework.
5. **Consent Form**: a pop-up that lets a visitor in a US state opt out of the sale or sharing of their personal information without identity verification. See [Configuring the Consent Form Experience](/content/docs/consent/guides/privacy-experiences#configuring-the-consent-form-experience/index.html) below.

## Configuring the Banner+Modal Experience

Click on any **Banner+Modal** component to view the detailed configuration page.

From here you can set the 4 components of the privacy center experience:

1. **Experience name, type, dismissable settings**:
   - **Name**: name given to the experience so that you can easily identify it.
   - **Type**: experience type assigned when the experience was created. Once created, this cannot be edited.
   - **Dismissable**: whether or not consumers can dismiss the experience before making a consent selection.
2. **Properties**: assign the experience to a property you've created.
3. **Privacy notices**: choose one or more privacy notices to display in the privacy experience.
4. **Locations & Languages**: choose the languages the privacy experience will support. Support for languages other than English requires a special Fides license.

## Configuring the Modal Experience

Click on any **Modal** component to view the detailed configuration page.

From here you can set the 4 components of the modal experience:

1. **Experience name and type**:
   - **Name**: name given to the experience so that you can easily identify it.
   - **Type**: experience type assigned when the experience was created. Once created, this cannot be edited.
2. **Properties**: assign the experience to a property you've created.
3. **Privacy notices**: choose one or more privacy notices to display in the privacy experience.
4. **Locations & Languages**: choose the languages the privacy experience will support. Support for languages other than English requires a special Fides license.

## Configuring the Privacy Center Experience

Click on any **Privacy center** component to view the detailed configuration page.

From here you can set the 4 components of the privacy center experience:

## Configuring the TCF Overlay Experience

When TCF is enabled for your Fides account, a TCF Overlay experience will also be available. Click on any **TCF Overlay** component to view the detailed configuration page.

From here you can set the 4 components of the TCF Overlay experience:

1. **Experience settings**:
   - **Name**: name given to the experience so that you can easily identify it.
   - **TCF configuration**: select the TCF publisher restrictions configuration to apply to the experience.
   - **Reject all behavior**: Determines whether opting out of all purposes blocks everything (both consent and legitimate interest processing) or only blocks consent-based processing while allowing legitimate interest to continue.
   - **Reject all visibility**: Choose whether the reject all button is visible on the banner and modal, or only on the modal.
   - **Dismissable**: whether or not consumers can dismiss the experience before making a consent selection.
2. **Properties**: assign the experience to a property you've created.
3. **Privacy notices**: TCF Purposes are automatically added to the TCF Overlay experience and cannot be removed. You can also add additional notices to the experience if necessary.
4. **Locations & Languages**: choose the languages the privacy experience will support. Support for languages other than English requires a special Fides license.

## Configuring the Consent Form Experience

The Consent Form is a pop-up designed for US-state opt-out of sale/sharing that does **not** require identity verification. It offers a two-tier opt-out: an immediate opt-out for every visitor, and an optional full opt-out that creates a privacy request when the visitor chooses to provide their identity details. It also surfaces a Global Privacy Control (GPC) prompt when a GPC signal is present.

Select **Consent form** as the experience type. You then configure it through the standard Privacy Experience editor. Different settings apply compared to the other types of experiences.

## Adding a new custom privacy experience

To add a new privacy experience, click on "Create new experience" in the top right of the Experiences page. Give your experience a name and select the type of experience you want to create from the dropdown menu. The available types are:
- **Banner+Modal**: a banner that appears at the bottom of the page with a modal for detailed preferences
- **Modal**: a modal dialog that appears in the center of the page
- **Headless**: an experience that does not display any UI, allowing you to programmatically manage consent or implement a fully custom UI using the Fides API and SDK
- **Privacy Center**: a standalone privacy center page
- **Consent form**: a pop-up for US-state opt-out of sale/sharing without identity verification. See [Configuring the Consent Form Experience](/content/docs/consent/guides/privacy-experiences#configuring-the-consent-form-experience/index.html).

## Configuring the locations and languages

All privacy experiences include a section to configure locations and languages the privacy experience is served in.

### Locations

You can assign a privacy experience to any location which is enabled in the Locations and regulations section of the Fides settings.

### Languages

Each privacy experience allows you to provide custom copy for all titles, descriptions, links, and buttons that are part of the experience.