The Agreements API help web administrators to deal with legal issues regarding data protection, terms and conditions.

How does it work?

First of all, you create an agreement. The main fields are:




Title of the agreement. Is what it shows in listings and the subject in notifications.


Body of the agreement. Accepts del {site} macro, replaced by web site name.

Required to notify

Describes this agreement as required when sending email notifications to users.

Required to access

Describes this agreement as required to operate for authenticated users.


Will force sending a Pending signature notification each time encounters a failed intent, up to ten notifications.

What final users will see?

When the required signature forbids sending notifications, a Pending signature notification will be sent. The user will be able to Accept or Decline the agreement from the notification email.

When the required signature forbids operating, the user will be redirected to the agreement, expecting to Accept or Decline the agreement.

The agreement flow


This protocol is still pending to revision and may not reflect current behavior.




Since sendables are configured by administrators, recipients are manually selected. Those who explicitly declined to receive notifications, despite being selected, will not receive any email.


Only those who explicitly accepted to receive notifications and are category subscribers, will receive the email.


Only those who explicitly declined to receive notifications, will not receive the email.

The generic rule to follow explains itself better in terms of participation. When a user participates in a module, the participation will prevail to the not signed status.

Publication category subscriptors are not considered participants, but observers. In this case, not signed prevails.

Printer version
English05/23/18 14:24Lluís Turró Cutiller
English06/15/18 09:00Lluís Turró Cutiller
English07/24/18 10:26Lluís Turró Cutiller

©, 2011-2018
Tel. +34 609323947