Skip to main content

Provides a functionality to ask users for consent to different topics.

Project description

Provides a functionality to ask authenticated users for consent to different topics, before they can continue. One can add multiple consent items and define which user will have to give there consent based on there permission roles. Each of this users have to give the consent before they can continue to work.

collective.consent-demo.gif

Demo

This is realized by viewlet which will check a list of consents for each user/consent_item combination and redirect the user to the consent item case they still have to give there consent. Soup Internally the consents are stored in a soup on the ConsentsContainer (‘/consents’) object.

Features

  • Allows you to add multiple consent items (documents).

  • A consent item consists of a Title, Description, RichText and a custom button text.

  • Also you can define an update period, when the user has to give the consent again.

  • For every consent item one can choose the target permission roles and consent update period.

  • Users are only ask for consent on published consent items.

  • One can reset (invalidate) all existing consents for a consent item.

ToDo

  • Support local roles, currently only if the user has global roles that match, she will see the consent note.

  • Add a global list of consents, sorted per user (maybe)

  • remove Anonymous from roles vocab, as we only support authenticated users

  • allow users to remove there consent?

  • list given consents on the user dashboard (action: my consents)

Installation

Install collective.consent by adding it to your buildout:

[buildout]

...

eggs =
    collective.consent

and then running bin/buildout, start Plone and activate the add-on in the add-on’s control panel. Then add a ConsentContainer on the top-level (portal-root).

Thanks

Initial implementation by: Derico - https://derico.de Sponsored by https://www.uni-giessen.de

Contributors

Contribute

Support

If you are having issues, please let us know.

License

The project is licensed under the GPLv2.

Contributors

Changelog

2.0b1 (2023-01-19)

  • Plone 6 compatibility [MrTango]

1.0b3 (2021-02-09)

  • Fix permission on consent_item_consents view [MrTango]

1.0b2 (2019-11-19)

  • add plone.app.contenttypes as dependency [MrTango]

  • sync travis config with tox config [MrTango]

  • remove plone.app.contenttypes dependency and define RichText field our self. [MrTango]

  • Add some german translations [MrTango]

  • Fix i18n domain, add styles, refacture views, exclude consents container from nav [MrTango]

1.0b1 (2019-05-16)

  • Initial release. [MrTango]

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

collective.consent-2.0b1.tar.gz (32.6 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page