Progress Reports
Why Progress Reports?
If you use Antragsgrün to archive resolutions, it is possible to also add progress reports to each resolution. So eligible members can not only read the resolutions themselves, but also the progress that the acting organization is making in implementing them.
Progress reports therefore add an additional text section to the resolution, the one that holds the protocol of the progress made since its publication. This section behaves differently from regular text sections in the following aspects:
- There is a separate permission to allow users to create and edit progress reports, independently from the main resolution text. Typically, only special admins will be allowed to modify the text of a resolution itself under very special circumstances, while the permission to change the progress report will be given out to a wider user group, like to the secretariat of the organization or dedicated working groups.
- Editing the progress report is way quicker and informal than editing the resolution text. It is possible to edit it directly from within the main motion view, without having to go to the admin view first.
- The progress report has a “last changed on” and “author” field that is independent of the resolution itself.
In the remainder of this page, we will describe how to set up and how to use progress reports.
Use
While creating the resolution (as part of the “Merge amendments” function), you will be presented a choice if to create a new motion, a preliminary resolution or a final resolution. If you choose a resolution, and a compatible motion type exists (see “Setup”), a dropdown with compatible motion types will appear, the progress reports type being one of them. Select it and proceed as normal.
![Screenshot: Creating a resolution with progress report](/img/help/ProgressReport1.png)
By default, the generated resolution will be presented as any resolution, without a progress report.
Eligible editorial persons, however, will be given the chance to create and edit the progress report, just below the resolution text. Once a text is entered, it will be visible to all users.
![Screenshot: Editing the progress report](/img/help/ProgressReport2.png)
Setup
Setting up progress reports has two aspects: creating a compatible motion type, and granting permissions to the users that are allowed to write them.
Creating a Motion Type
If you use the default motion type for motions (that is, a title, a motion text, and optionally a reason), it will be fairly simple to create a motion type for the progress reports: In the settings, choose “Create new motion type”, and select “Progress reports” as template there. A new motion type will be created with the following noteworthy settings:
- Only Admins are allowed to create new documents (resolutions)
- Besides the default sections “Title” and “Resolution”, there will not be a “Reason” (as the reason is typically removed when creating a resolution) section, but a “Progress” section of type “Editorial Text” instead.
If the motion type you use for motions has additional sections besides the ones mentioned above, you will need to make sure that the new motion type for the progress reports is compatible with it. Basically, for each non-optional text section in the original type, there needs to be a corresponding text section in the progress report motion type. If there is none, you will not be able to select the motion type when creating the resolution.
Grant Permissions
The relevant permission to edit progress reports is called “Manage editorial sections / Progress reports”. Users can receive this permission in three ways:
- Consultation and Site admins have this permission automatically
- You can assign users to the user group “Progress reports”. This group grants said permission to all members.
- Alternatively, you can create a new user group, add members, and grant this permission to this group. This would be the approach to take if you want to define users that can only edit the progress reports of a subset of all resolutions - for example, having different user groups, with each being responsible for a specific Topic / Tag. (Use the “Restricted to: Tag” choice when defining the permissions in this case).