Hi @Quentinchampenois,

Amazing project! At Digidem Lab, we've been reusing your authorisation handler and Populate's extra user fields module but it would be great to be able to customise this from the backend!

Some more features that would be great to have:

• being able to configure fields for statistical purpose (like demographic information) and fields with specific information (like a unique postal address for instance)
• being able to see and export the specific information
• being able to visualise aggregated values of statistic fields (maybe only above a certain threshold to not reveal demographic information about the first users on a platform/process) in the backend.
• being able to filter these visualisations by process, if not by action performed within a process ("submitted a proposal", "voted")
• being able to display some of these visualisations in the frontend on process pages or even on the homepage.
• being able to anonymise users after a certain period of time of inactivity from a user (this would erase the information from the database) while retaining aggregated values for closed processes and the whole platform
• being able to only save aggregated statistics in the database (instead of saving demographic information specifically linked to an account, the sign up form just increments aggregated values)
• being able to ask conditional questions (that are displayed or not depending on the value of another question, like in Surveys)
• being able to write help texts for each of those fields, and maybe a general help text for all fields to explain how this data is used and processed.

I know it's a long list with many points that would be very hard to implement. But I'm writing it in case, maybe you'll find some of them relevant. 😊