Skip to content

Configure permissions at district (scope) level for the different components #5708

@carolromero

Description

@carolromero

ref: PP003

User story

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

In Barcelona's participatory budget process, citizens will be able to vote on projects in two different districts, in which they are registered and in another district of their choice (see #5711). As an administrator I need to configure some components and spaces to work with districts (scopes).

Describe the solution you'd like

To be able to configure an Initiative, or any component of: Budgets/Debates/Meetings/Proposals/Surveys for one or more Districts.

Note: currently the initiatives can be configured by a single scope. That configuration should be reviewed to see if some of the code can be used to do this.

Describe alternatives you've considered

To also make it work with Neighborhoods but this could be really tricky to have by our Municipal Census API. This is a real need, as for instance on Decidim Barcelona there are Initiatives that work at the Neighborhood level. [Page 19 of the Regulations of Citizen Participation mentions "barris" (catalan for neighborhoods)].
We'll tackle this in the future.

Additional context

URL: https://www.decidim.barcelona/admin/participatory_processes/pam/components/1/edit

🎨 Backend


(this field needs to be a checkbox)

Does this issue could impact on users private data?
Yes, this is about adding metadata to the verification (municipal census authorization).

Acceptance criteria

  • As an administrator I can configure Initiatives by one or more districts (to be discussed in EPIC: Management of the initiatives by the promoters from the front-end #5736)
  • As an administrator I can configure Budgets by one scope
  • As an administrator I can configure Debates by one scope
  • As an administrator I can configure Meetings by one scope
  • As an administrator I can configure Proposals by one scope
  • As an administrator I can configure Surveys by one scope

Related issues

Metadecidim link

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions