Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Consent Management v2

search

Please Note:

Consent Management v2

Organizations managing user consents across multiple applications need a reliable, auditable, and GDPR-ready solution. Consent Management v2 provides centralized consent management as a standalone microservice of the OneWelcome Identity Platform.

Key capabilities

  • Document lifecycle management: Track consent documents (privacy policy, terms of service, cookie policy, and custom types) through a structured DRAFT -> SCHEDULED -> ACTIVE -> SUNSET -> ARCHIVED lifecycle, with transitions driven by dates rather than manual status changes.

  • Multi-version versioning: Maintain multiple versions of each document with content lineage tracking. Only new legal content triggers re-consent, translation-only updates do not.

  • Multi-language support : Store localizations for any number of languages per document version. A content lineage model (NEW_CONTENT vs DERIVED) determines whether a language update requires users to re-consent.

  • Immutable audit trail: Every consent action is appended to an insert-only ledger table, providing a tamper-proof compliance record for GDPR audits.

  • Batch consent operations: Register up to 50 document consents in a single API call, designed for high-throughput login flows.

  • Re-consent campaigns: Automated grace periods allow users to continue accessing services during a document transition, with a configurable deadline after which access is blocked until the user accepts the new version.

  • Multi-tenancy: Full data isolation at the PostgreSQL schema level. Each tenant has an independent document library and consent ledger.

  • Attribute consent management: Define processing purposes with legal basis (GDPR Art. 6), linked identity attributes, and communication channel preferences. Each purpose follows an independent version lifecycle (DRAFT → SCHEDULED → ACTIVE → ARCHIVED).

  • Consent Management console: A dedicated web interface for administrators to manage documents and processing purposes, versions, and localizations, and to query the consent ledger.

Consent Management v2 distinguishes between two types of consents:

  • Document consents give consent to a document and are often required to gain access to a company's service (for example, a Privacy Policy or Terms of Service).

  • Attribute consents give consent to the use of personal data (referred to as attributes) for a specific purpose (for example, allowing marketing emails or analytics). They are always optional and indicate a preference of the user.

Use cases

GDPR compliance: Consent Management v2 helps organizations meet GDPR requirements by:

  • Requiring users to explicitly consent to Terms of Service, Privacy Policy, and other mandatory documents before accessing services.
  • Storing a dated, immutable record of each consent event, including the exact document version and language the user consented to.
  • Enabling compliance teams to query and export consent records filtered by user, document, date range, or status.

Login-time consent enforcement: During login, your backend calls the Runtime API to check whether a user has outstanding documents requiring consent. If mandatory documents are outstanding, access is blocked until the user accepts them. Optional documents (such as marketing consents) can be presented without blocking access.

Document update and re-consent: When the legal content of a document changes, a new document version is published with NEW_CONTENT lineage. Users who consented to the previous version are automatically identified as having outstanding consents. A grace period can be configured to allow existing users continued access while they review and accept the new version.

Multi-language rollout without re-consent: When a document is translated into a new language without changing the legal content, the new localization is marked as DERIVED from the original. Users who consented to the original language are considered compliant for the translated version, and no re-consent is required.

Admin UI access and permissions

Access to the Consent Management v2 console is controlled by role-based access. Two roles are available:

Role Permissions
consent_read View documents, purposes, versions, localizations, and consent history. Cannot create, edit, or delete.
consent_write Full access — create, update, activate, and delete documents, purposes, versions, and localizations. Query and export consent history.

These roles apply to all Admin UI features: document consent, attribute consent, and consent history.

Contact your platform administrator to have the appropriate role assigned to your user account.

The legacy Consent and Preference Management product uses a different role: role_consent_admin. This role grants access to the legacy Consent UI only and has no effect on Consent Management v2.

Note

The legacy role and the Consent Management v2 roles are independent. If a user is assigned both role_consent_admin and consent_read or consent_write, the OneWelcome console displays both the legacy Consent UI and the Consent Management v2 Admin UI to that user. This is expected behavior, not an error. To present a single Consent UI, assign only the role that matches the product the user should work with.

On this page