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

Restrict which authorized users can participate in a component / item

Avatar: Participant deleted
13/02/2019 15:04  

Here at Populate we'd like to implement the following feature:

*Problem that needs to be solved*

Ability for an admin to restrict which authorized users have permission to participate in a given component or item (extending the current component permission scheme), based on criteria provided by the authorization (ie. admin needs to configure a process so only participants with ages between 16 and 24 can participate).

*Solution proposed*

- An authorization defines which criteria will be known from a participant (ie. age, gender, district). Right now this is stored in the authorization metadata.
- In the component permission form (https://try.decidim.org/admin/participatory_processes/costa-verde/components/5/permissions/edit?locale=es), the UI will be modified so several criteria can be specified according to what the authorization makes available.

  • Filter results for category: Administration Administration

List of Endorsements

Avatar: Pau Parals Pau Parals verified-badge
Endorsements count1
Restrict which authorized users can participate in a component / item Comments 5

Reference: MDC-PROP-2019-02-14253
Version number 1 (of 1) 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: dca5067385e44763353f8db009285b9c9b346340ed7cb7b284b15cf2b73d559e

Source: {"body":{"en":"Here at Populate we'd like to implement the following feature:\r\n\r\n*Problem that needs to be solved*\r\n\r\nAbility for an admin to restrict which authorized users have permission to participate in a given component or item (extending the current component permission scheme), based on criteria provided by the authorization (ie. admin needs to configure a process so only participants with ages between 16 and 24 can participate).\r\n\r\n*Solution proposed*\r\n\r\n- An authorization defines which criteria will be known from a participant (ie. age, gender, district). Right now this is stored in the authorization metadata.\r\n- In the component permission form (https://try.decidim.org/admin/participatory_processes/costa-verde/components/5/permissions/edit?locale=es), the UI will be modified so several criteria can be specified according to what the authorization makes available."},"title":{"en":"Restrict which authorized users can participate in a component / item"}}

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/14253/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/14253/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Report inappropriate content

Is this content inappropriate?

Reason

5 comments

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed
Conversation with Carol Romero
Avatar: Carol Romero Carol Romero verified-badge
02/04/2019 12:44
  • Get link Get link

Hi @! Could you please link here the PR? Thanks

Avatar: Virgile Deville Virgile Deville
12/05/2019 20:53
  • Get link Get link

This sounds super cool @carol @ !
Where can I find documentation and a testing link ? Is the permission based on a declarative field in signup or is it linked to some kind of authorization handler ?

Avatar: Carol Romero Carol Romero verified-badge
13/05/2019 10:00
  • Get link Get link

Hi @virgile_deville this was finally done for a specific municipality, as it was not a generic development. This setting was incorporated as part of the authorization.

Avatar: Virgile Deville Virgile Deville
13/05/2019 17:29
  • Get link Get link

@carol Could you provide a link to the repo ?

Avatar: Antti Hukkanen Antti Hukkanen
19/08/2019 10:50
  • Get link Get link

I wasn't sure how the feature would work that is suggested in this proposal but it sounds possibly similar to a problem we have encountered.

Just to make sure, I created another proposal to the problem we have encountered:
Better control of the authorization permission requirements for a component

It may be related or not.

Add your comment

Sign in with your account or sign up to add your comment.

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 Barcelona
Or

Sign up

Forgot your password?