This site uses cookies. By continuing to browse the site, you agree to our use of cookies. Find out more about cookies.
Skip to main content
Metadecidim's official logo
  • English Triar la llengua Elegir el idioma Choose language
    • Català
    • Castellano
Sign Up Sign In
  • Home
  • Processes
  • Assemblies
  • Initiatives
  • Consultations
  • Conferences
  • Help

Propose new functionalities for Decidim software

#DecidimRoadmap Designing Decidim together

Phase 1 of 1
Open 2019-01-01 - 2030-12-31
Process phases Submit a proposal
  • The process
  • Debates
  • Propose new features
  • News
chevron-left Back to list

Ability to disable public profiles

Avatar: Antti Hukkanen Antti Hukkanen
24/02/2021 14:36  

**Is your feature request related to a problem? Please describe.**

Some users are very cautious about their privacy and currently in Decidim it is not possible to create private user accounts. Once you create an account on the platform, it is public and available for everyone's eyes.

The person searching their name in Google (or other search engines) will find results on the Decidim platform. Some people are extremely worried about this functionality and some will even refuse to participate unless they can do it privately.

**Describe the solution you'd like**

I'd like to be able to configure whether the public profiles functionality is active or disabled on the platform. When disabled, the public profiles would not be accessible on the platform.

Other possibility would be that this is configurable through the profile settings and the system administrator could decide the default (public or private).

After the discussion below, it would be also required that the person's name is hidden in all activities that they have done on the platform. This would apply e.g. to the profile badge in comments and proposals as well as the data exports and the API where the name would appear. In case the participant wants to remain anonymous, we could show e.g. "Participant 123" instead of the name in their profile.

**Describe alternatives you've considered**

Creating a customization per instance but this exact same request comes to us every other month now, so I think it would be sensible to consider how to solve this properly.

Given the proposed functionality, this could be also a setting per profile but in that case it should be disabled by default and only if the user wants, their profile would become public.

**Additional context**

Especially in Finland people can be extremely cautious about entering their details into any web platforms or having their name appear on public websites where other people can inspect what their neighbor is doing.

Some people feel this is a violation of their personal privacy.

**Does this issue could impact on users private data?**

Yes, it has a positive impact on users' private data as their private data won't become publicly visible on a website without them having full control over it.

**Funded by**

We can possibly find funding for this if it is agreed on.

  • Filter results for category: Participant profile and configuration Participant profile and configuration

List of Endorsements

Avatar: Virgile Deville Virgile Deville
Avatar: Pauline Bessoles Pauline Bessoles verified-badge
Avatar: Oliver Azevedo Barnes Oliver Azevedo Barnes
Avatar: Wouter Tebbens Wouter Tebbens
Avatar: álvaro ortiz álvaro ortiz verified-badge
Avatar: Pierre Mesure Pierre Mesure verified-badge
and 3 more people (see more) (see less)
Endorsements count6
Ability to disable public profiles Comments 18

Reference: MDC-PROP-2021-02-16247
Version number 2 (of 2) see other versions
Check fingerprint

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: 737ec39b4d365b828757cea379bcc657faef6533883fc6c53a4df293b2cff6b2

Source: {"body":{"en":"<p><strong>**Is your feature request related to a problem? Please describe.**</strong></p><p>Some users are very cautious about their privacy and currently in Decidim it is not possible to create private user accounts. Once you create an account on the platform, it is public and available for everyone's eyes.</p><p>The person searching their name in Google (or other search engines) will find results on the Decidim platform. Some people are extremely worried about this functionality and some will even refuse to participate unless they can do it privately.</p><p><strong>**Describe the solution you'd like**</strong></p><p>I'd like to be able to configure whether the public profiles functionality is active or disabled on the platform. When disabled, the public profiles would not be accessible on the platform.</p><p>Other possibility would be that this is configurable through the profile settings and the system administrator could decide the default (public or private).</p><p>After the discussion below, it would be also required that the person's name is hidden in all activities that they have done on the platform. This would apply e.g. to the profile badge in comments and proposals as well as the data exports and the API where the name would appear. In case the participant wants to remain anonymous, we could show e.g. \"Participant 123\" instead of the name in their profile.</p><p><strong>**Describe alternatives you've considered**</strong></p><p>Creating a customization per instance but this exact same request comes to us every other month now, so I think it would be sensible to consider how to solve this properly.</p><p>Given the proposed functionality, this could be also a setting per profile but in that case it should be disabled by default and only if the user wants, their profile would become public.</p><p><strong>**Additional context**</strong></p><p>Especially in Finland people can be extremely cautious about entering their details into any web platforms or having their name appear on public websites where other people can inspect what their neighbor is doing.</p><p>Some people feel this is a violation of their personal privacy.</p><p><strong>**Does this issue could impact on users private data?**</strong></p><p>Yes, it has a positive impact on users' private data as their private data won't become publicly visible on a website without them having full control over it.</p><p><strong>**Funded by**</strong></p><p>We can possibly find funding for this if it is agreed on.</p>"},"title":{"en":"Ability to disable public profiles"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

Share:

link-intact Share link

Share link:

Please paste this code in your page:

<script src="https://meta.decidim.org/processes/roadmap/f/122/proposals/16247/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/16247/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Report inappropriate content

Is this content inappropriate?

Reason

Comment details

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed
You are seeing a single comment

View all comments

Avatar: Antti Hukkanen Antti Hukkanen
05/05/2021 13:24
  • Get link Get link

The first point I would very much support, this would indeed solve the described problem for the direct registration users.


For the oauth options, we could default to not saving the name but it is a necessary field and without it, the user record won't save. Also, I believe the nickname is automatically generated from the name right now and if we remove the name, the users would have to create their nickname on the platform. Imagine the confusion the user would get when they come ONLY for PB voting and the system asks their nickname... I don't think this would be good either.

I really think it would be very beneficial to have the "privacy" options available under the user profile where they could decide e.g. about the visibility of the public profile (and default it to hidden or make the defaults configurable for admins). We could fork the user related functionality to its own module but it's not easy to manage in a module because we would have to override parts of the user model, user forms and the user views. This sort of stuff that strongly relates to existing core functionality is quite hacky to put in a module. + it becomes hard to manage every time there are core changes related to the users.

If you strongly feel in @product that the publicity of the profiles is a must in Decidim, I would really want to open the conversation further into how can we make it so that it wouldn't have any effect in the current functionality in instances by default but for system administrators we could add options to add these privacy options available for the users.

Loading comments ...

  • Terms and conditions of use
  • About the community
  • Download Open Data files
  • Metadecidim at Twitter Twitter
  • Metadecidim at Instagram Instagram
  • Metadecidim at YouTube YouTube
  • Metadecidim at GitHub GitHub
Creative Commons License Website made with free software.
Decidim Logo

Confirm

OK Cancel

Please sign in

decidim Sign in with Decidim
Or

Sign up

Forgot your password?