Propose new features
Designing Decidim together
Accepted
Linked to others proposals we submitted lately is another request from our client which deals with the customization of the registration form.
The aim through this feature is to collect data enabling him to improve his evaluation of his actions for his users. Data would be age, gender and others as already written in this proposal (https://meta.decidim.org/processes/roadmap/f/122/proposals/14381).
Obviously this is a sensitive matter regarding Decidim’s social contract.
We thought about making the registration form customizable by the admin from the back office. The responsibility of collecting the data being his, the admin would have to justify in terms and conditions the collection of additional personal data.
This proposal has been accepted because:
- Developed by Populate
- Available as module here: https://github.com/PopulateTools/decidim-module-extra_user_fields
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
View all comments
Regarding controlling what the user can do, yes, the authorization metadatas are meant for controlling that.
But the usability for manual form-based authorizations is not really great right now. This works when we are using e-identification services since we get the data from a central digital registry automatically during the authentication process. But when entered manually, users have no idea what is an "authorization", how they can get to that view and why they should authorize themselves.
It works the best when this happens through an action they tried to perform but they did not have the right to do so due to missing authorization metadata. E.g. in the budgeting view, it shows a popup that data is missing and then they can authorize themselves after which they are redirected back to the budgeting view. This is quite OK right now.
Loading comments ...