Assembly creation

Title of the assembly, "General Committee" or "neighborhood city council" for example.

Visible in the card of the assembly on the homepage, the assemblies index, the navigation, and the "Hero image and CTA" landing page block.

Subtitle of the assembly.

Visible in the "Hero image and CTA" landing page block.

Determines the order of the assembly when displayed in the processes index or homepage.

N/A

URL slugs are used to generate the URLs that point to this process. Only accepts letters, numbers and dashes, and must start with a letter.

Visible in the URL of the assembly, for example https://example.org/assemblies/city_coucil.

Hashtag redirecting to the X social network.

Visible in the "Hero image and CTA" landing page block.

A short explanation of what’s your participatory process about.

Visible in the "Main data" landing page block.

A long explanation of what’s your assembly about.

Visible in the "Main data" landing page block.

The explanation of the assembly’s goals.

Visible in the "Main data" landing page block.

Who composes the assembly.

Visible in the "Main data" landing page block.

How the assembly is organized.

Visible in the "Main data" landing page block.

The text you enter here is shown to the user right below the process information.

Visible in the "Announcement" landing page block.

When this assembly was created. You have a calendar widget to choose the day. Expected format: dd/mm/yyyy.

Visible in the "Dates metadata" landing page block.

The date when this assembly was added to the instance. It does not necessarily have to be the same as the creation date. Expected format: dd/mm/yyyy.

Visible in the "Dates metadata" landing page block.

If the duration of this assembly is limited, select the end date. Otherwise, it appears as indefinite. Expected format: dd/mm/yyyy.

Visible in the "Type and duration" landing page block.

When this assembly closed. Expected format: dd/mm/yyyy.

Visible in the "Dates metadata" landing page block.

Why this assembly closed.

Not displayed on the landing page.

Image used in presentation cards of this process. Guidance for file: Has to be an image or a document. For images, use preferably landscape images, the service crops the image. Maximum file size: 10 MB

Deprecated, isn’t used anywhere. Use "Hero image and CTA" content block on the landing page instead.

Check if you want to have Scopes filtering in this assembly.

Which Scope does this assembly belongs to.

Which Area does this assembly belongs to.

The issue of the assembly, the object of what is decided.

The decision making process inside the assembly.

Metadata on the assembly scope, if it’s relevant.

If a specific group is at the origin of the assembly, like a city direction, an association committee, etc.

The organization domain or category, if it’s relevant.

Who are the authorized participants, who can participate to the assembly.

To what other assemblies this assembly belongs. Assemblies can be nested inside one another.

Check if you want the assembly to have more visibility in the Assemblies public list. It’s also visible in the "Highlighted Assemblies" Content Block in the Homepage configuration.

Check if this assembly should only be accessible by Private Participants.

Check if this assembly is private but should be visible to all the participants. This means that other participants or visitors can see it but they can’t participate in it.

Choose "City Council" "Public" or "Other" in case you want to specify the name of the organization that created this assembly.

Which Assembly type is related to this assembly.

Select other participatory processes related to this assembly.

Which social networks profile does this assembly has. Can be X, Facebook, Instagram, YouTube, and/or GitHub.