Add an optional paywall to view Assemblies/Groups with particular Assembly Types

[paarals]

Is your feature request related to a problem? Please describe.
There are assemblies that will be of the type: Paid Access. For these assemblies, it will be necessary to make a payment (or donation) to access them.

Describe the solution you'd like
The donation module will be improved by allowing restricted access to participation spaces. Additionally, it will be used as a verification method if needed in other spaces.

Mock up

[ADMIN]

1. First, the Administrator sets up a new type in the Assembly Settings: Paid Access.
   

2. Second, the Administrator configures the Assembly and manually sets the assembly type: Paid Access.
   

3. Before publishing the Assembly, there is a new Payment Configuration section.
   

4. In the payment configuration, the desired amount can be set and the configuration saved.
   

[Public section]
5. Once the assembly is published, users can filter and see which Assemblies are of the type: Paid Access.

6. If there is a payment configuration in the assembly, the payment screen is automatically displayed for the user (when they click on the assembly or More info).
   

7. If the payment is made, the user gains access to the assembly.
   

Accepted Criteria

• Limit access to the assembly upon payment
• Set up a new section to determine the access verifier
• If there is a payment restriction, the user goes directly to the payment screen
• Allow setting a predetermined access payment amount
• Allow changing the predetermined access payment amount (up to removing it)

Technical specifications

Implementation

Testing

Demo:

Additional context
This is a first version. The following should be considered for a second iteration:

• Whether the user needs more information (see the assembly home) to make the payment (i.e., where we will regulate access and if other payment buttons are needed on the home page)
• Whether the administrator needs to know which users have paid and if there is a period when access expires and they have to pay again.

[microstudi]

Here is a mockup proposal of how this would look in the eyes of the administrator. Note that it will probably have more options than just the amount (a description text for the user, the expiration date for instance)

From the user's perspective, this could be a landing page for the non-authorized users (text and design will change according to the needs/configuration):

[BigSnicker]

Will be watching this. Let's stay in touch.