Ensure GDPR compliance by default (Article 25 GDPR – privacy by design and by default). Under GDPR, consent must be freely given, specific, informed and unambiguous [1]. We were subscribing users without explicity consent, which goes against the "No pre-ticked boxes" principle. For compatibility with existing installations, we're using a setting, disabled by default. Once we release version 2.4.0 we will enable it by default, which won't affect existing installations but only new ones. [1] https://gdprinfo.eu/best-gdpr-newsletter-consent-examples-a-complete-guide-to-compliant-email-marketing
34 lines
989 B
Ruby
34 lines
989 B
Ruby
class Admin::Settings::FeaturesTabComponent < ApplicationComponent
|
|
def settings
|
|
%w[
|
|
feature.featured_proposals
|
|
feature.facebook_login
|
|
feature.google_login
|
|
feature.oidc_login
|
|
feature.saml_login
|
|
feature.twitter_login
|
|
feature.wordpress_login
|
|
feature.signature_sheets
|
|
feature.user.recommendations
|
|
feature.user.recommendations_on_debates
|
|
feature.user.recommendations_on_proposals
|
|
feature.user.skip_verification
|
|
feature.community
|
|
feature.map
|
|
feature.allow_attached_documents
|
|
feature.allow_images
|
|
feature.help_page
|
|
feature.remote_translations
|
|
feature.translation_interface
|
|
feature.remote_census
|
|
feature.valuation_comment_notification
|
|
feature.graphql_api
|
|
feature.sdg
|
|
feature.machine_learning
|
|
feature.remove_investments_supports
|
|
feature.gdpr.require_consent_for_notifications
|
|
feature.dashboard.notification_emails
|
|
]
|
|
end
|
|
end
|