Skip to content

Policies and Consents in Agora

Agora includes a mechanism for managing policy texts and client consents. It is used in scenarios where a viewer registers on the portal, submits an event request, or receives access to a broadcast as an identified client.

The system stores the documents themselves, their versions, and client consent records for a specific document version. This makes it possible to see who accepted the personal data processing policy or marketing consent, and when.

Document Types

The Policies and consents section uses two document types:

  • pdn — consent to collect and process personal data;
  • marketing — consent to marketing emails.

The pdn document is required for client registration on the portal. Without acceptance of the current published version of this policy, Agora does not complete client registration.

The marketing document is used for optional consent to marketing communications. The user can refuse it if the registration form allows that scenario.

Admin Section

Documents are managed in the Agora admin UI under Content -> Policies and consents.

The document list shows:

  • document type;
  • version;
  • publication date;
  • last update date;
  • document identifier.

The list can be filtered by type: pdn, marketing, or all documents.

Creating a Draft

A new document is created as a draft. During creation, the content manager must select the document type: pdn for consent to collect and process personal data, or marketing for consent to marketing emails. After selecting the type, insert the document text in Markdown format.

A draft can be edited before publication. This is useful for legal review: the document already exists in the system, but is not yet shown to users as the active version.

Recommended workflow:

  1. Create a draft of the required type.
  2. Recheck the text, wording, links, and legal details.
  3. Edit the draft if needed.
  4. Publish the document only after final review.

Agora maintains separate version numbering for each document type. A new pdn version does not affect marketing version numbers, and vice versa.

Publishing a Version

To make a document active, specify the publication date and time in the draft card and save the document.

After publication, the version becomes available on the portal and is used in registration forms. The previous published version of the same type is no longer current, but remains in history.

A published version cannot be edited. If the text needs to change, create a new draft of the same type, make the changes, and publish the new version.

Required During Registration

During client registration on the portal, Agora checks the current published pdn policy.

The user must explicitly accept this policy. If consent is not accepted, Agora does not create a new client and does not update an existing client as part of registration.

If the pdn policy was updated after the previous registration, the client must accept the new current version. Consent to an old version remains in history, but does not count as consent to the currently published revision.

Marketing consent can be requested together with registration, but is usually optional: its absence should not block registration if the required pdn policy has been accepted.

Consent History

Agora stores consent history for each client and each document version.

For each consent record, the system stores:

  • client;
  • consent type;
  • document version;
  • acceptance time;
  • IP address, if it was detected;
  • browser User-Agent, if it was sent.

This history is important for audit: it is possible to check exactly which policy revision the client accepted and when that happened.

Consents in the Client Card

The client card in Agora shows the latest known consents for pdn and marketing.

For each consent, it shows:

  • acceptance time;
  • IP address;
  • link to the document and version;
  • whether the consent matches the latest published version.

If the client accepted a version that is not the latest published one, the interface highlights this state. Such a client must accept the updated policy during the next appropriate registration or access confirmation step.

Practical Recommendations

Before launching registration workflows, make sure that:

  • the current pdn version is published;
  • the policy text has been reviewed legally;
  • if marketing consent is used, the current marketing version is published;
  • the registration form shows users the published document versions;
  • after a policy update, users accept the current version again.

Do not edit published legal text retroactively. For any changes, create a new version: this keeps consent history correct and auditable.