Attribute consent

Attribute consent allows users to consent to the use of their personal data (referred to as attributes) for specific processing purposes, for example, receiving marketing emails or personalization. Unlike document consent, attribute consent is always optional and represents a user preference rather than a gate to access a service.

Attribute consent is organized in a three-level hierarchy:

Purpose definition
└── Purpose version (one or more)
    └── Purpose localization (one per language)

Purpose management

A processing purpose definition (for example, Email Marketing) is the top-level object that identifies what the user's personal data is used for. The definition includes a legal basis under GDPR Article 6, a default language, and an optional description.

Purpose list

When you open the Attribute Consent section of the Consent Management console, a paginated table lists all the purpose definitions for your tenant.

The table includes the following columns:

You can sort the table by any column and use the pagination controls to navigate between pages.

Purpose list actions

Each purpose row includes an actions menu (⋮). Select the menu to access the following actions:

The actions menu is only visible to users with the consent_write role.

Legal basis values

The Legal Basis field identifies the lawful basis under GDPR Art. 6 for processing personal data:

Create a purpose definition

1. In the purpose list, select Add New Purpose Definition.

2. Enter the following information:

   • Name: The purpose name must be unique within the tenant (1–100 characters).

   • Legal Basis: Select the applicable GDPR Art. 6 legal basis from the dropdown.

   • Default Locale: Select the default language from the tenant's configured locales.

   • Description: (Required) A description of the purpose (1–1,000 characters).

3. Select Save.

The new purpose appears in the list with no versions.

View purpose details

To open the purpose details page, select a purpose name in the list.

The detail page shows:

• The purpose definition properties (name, identifier, legal basis, default locale, description).
• An active version callout (if a version is currently ACTIVE).
• A table of all versions with their status, version number, version name, and lifecycle dates.

Edit a purpose definition

All fields are editable: Name, Legal Basis, Default Locale, and Description.

On the purpose details page, select Edit.

An unsaved changes dialog warns you if you navigate away with unsaved edits.

Delete a purpose definition

Deleting a purpose definition is a hard-delete: the definition and all its versions and localizations are permanently removed.

Deletion is allowed only if the purpose has no versions or all versions are in DRAFT status.

On the purpose list, select Delete from the actions menu (⋮) for the purpose.

Version management

On the purpose details page, the versions section lists all versions of the purpose.

For each version, the table includes:

When a new version becomes active, the previous active version is immediately archived.

Version actions

Each version row includes an actions menu (⋮). Select the menu to access the following actions:

Create a version

1. On the purpose details page, select Add Version.

2. Enter a Version name (unique within the purpose, 1–100 characters).

3. (Optional) Select the Identity Schema Source:

   • OIP: Identity attributes come from the OneWelcome Identity Platform schema.
   • External: Identity attributes come from an external identity schema.

4. (Optional) Configure the Data Scope (linked identity attributes) and Preferences (communication channels).

5. (Optional) Add localizations.

6. Select Save.

The version is created in DRAFT status with no version number.

Version detail page

The version detail page is where you configure all aspects of a purpose version. The page is organized into the following sections:

Version Metadata

Displays the version name, identity schema source, status badge, and lifecycle dates. You can update the version name and identity schema source here.

Data Scope

The Data Scope section defines which personal data attributes are linked to this processing purpose.

• Select identity attributes from the available list (grouped by category, for example personal.firstName, personal.email).
• You can link up to 50 attributes per version.
• Attributes come from either the OIP identity schema or an external schema, depending on the Identity Schema Source selected for the version.

Preferences

The Preferences section defines the communication channels and contact frequencies for this purpose.

You can add up to 10 channels per version. For each channel:

• Channel type: Select from the available types:

  Channel	Description
  EMAIL	Email communication
  SMS	SMS/text message communication
  PUSH_NOTIFICATION	Mobile push notifications
  PHONE_CALL	Phone call communication
  POSTAL_MAIL	Physical postal mail
  IN_APP_MESSAGE	In-app messaging

• Attributes: (Optional) Link identity attributes to this channel (for example, link personal.email to the EMAIL channel).

• Frequencies: (Optional) Select one or more permitted contact frequencies:

  Frequency	Description
  DAILY	Up to once per day
  WEEKLY	Up to once per week
  BIWEEKLY	Up to once every two weeks
  MONTHLY	Up to once per month
  QUARTERLY	Up to once per quarter
  SEMI_ANNUALLY	Up to twice per year
  ANNUALLY	Up to once per year

Localizations

The Localizations section lists all language-specific content for the version. You must add at least one localization (in the default locale) before the version can be scheduled. See Localization management for details.

Schedule / activate a version

1. Open the version detail page.

2. Set the Effective Date:

   • Set a future date to schedule the version. The status changes to SCHEDULED and the system assigns a version number.
   • Set the current date/time (within a 60-minute tolerance) to activate the version immediately. The status changes to ACTIVE.

3. Select Save.

When a version becomes ACTIVE, the previously ACTIVE version is automatically archived.

Prerequisites for scheduling:

• The version must have at least one localization.
• The version must have a localization for the purpose's default locale.

Unschedule a version (revert to DRAFT)

To revert a SCHEDULED version back to DRAFT:

1. On the version detail page, clear the Effective Date field.

2. Select Save.

The version returns to DRAFT status and its version number is removed.

Clone a version

To create a new version based on an existing version:

1. In the version actions menu (⋮), select Clone.

2. Optionally provide a new version name (the default is {original name} (Copy)).

3. Select Clone.

The clone is created as a DRAFT with all localizations copied and lifecycle dates cleared. After cloning, you are redirected to the new version's detail page.

Delete a version

Only DRAFT versions can be deleted. In the version actions menu (⋮), select Delete. SCHEDULED versions must be unscheduled first. ACTIVE and ARCHIVED versions cannot be deleted.

Localization management

Each purpose version can have localizations for multiple languages. A localization contains the language-specific title, legal text, and optional description that is shown to users when they are asked to consent to the purpose.

Localization list

On the version detail page, the localizations section lists all localizations for the version. Each row includes:

Add a localization

You can add localizations when creating a version, or at any time while the version is in the DRAFT, SCHEDULED, or ACTIVE status.

1. On the version detail page, select Add Localization.

2. Select the Language from the list.

   The list includes only locales configured for your tenant. A version can have at most one localization per language.

3. Enter the Title for the purpose in this language (1–100 characters).

4. Enter the Legal Text — the full legal text of the purpose shown to users.

5. (Optional) Enter a Description (1–1,000 characters).

6. Select the Lineage:

   • New content: The legal text is original or has changed. This creates a new consent requirement — users must actively consent to this localization.

   • Derived: The legal text is legally equivalent to another existing localization. Select the Source localization from an ACTIVE or ARCHIVED version of the same purpose. The legal text is inherited from the source. Users who consented to the source localization are automatically considered compliant.

7. Select Save.

Edit a localization

On the localization detail page, you can update the Title, Legal Text, and Description. The Language and Lineage fields cannot be changed after creation.

For DERIVED localizations, you can select View Source Details to open a dialog showing the source localization's version name, locale, and title.

Localizations on ARCHIVED versions are read-only and cannot be edited.

Legal vs non-legal changes on ACTIVE versions

When you edit a localization on an ACTIVE version, a dialog appears asking you to classify the type of change:

• Non-legal change: The change does not alter the legal meaning of the purpose (for example, fixing a typo or updating a description). The save proceeds normally and no re-consent is required from existing users.

• Legal change: The change alters the legal text in a way that requires users to re-consent (for example, changing the scope of data use or the processing basis). When you select this option, you are redirected to the Create Version page to create a new version with the updated content. The existing ACTIVE version remains unchanged.

Delete a localization

Select the delete action for a localization. Deletion is blocked if:

• It is the last remaining localization for the version.
• It is the localization for the purpose's default locale.