# data[].attributes.body
- Steps in roughly chronological level, contains both considerations on the process as a whole (member services perspective) and technical considerations

- Assoc actions in GREEN, Moniheli actions and internal automations in BLUE, automated messages and communications in PURPLE

# data[].attributes.body
Form should be prefaced with an info box that tells them to get in touch with they need help with applying/documents!

- Association info: official name, EN version of name, accepted short version of name
- Y-tunnus (replaces the member number)
- Compulsory documents: PRH-ote jossa allekirjoittajat, säännöt
- Non-compulsory documents: toimintasuunnitelma, vuosikertomus, talousarvio. For toimintasuunnitelma and vuosikertomus, an additional field for people to freely write text, if no document available. IF POSSIBLE either/or compulsory rule
- Billing info: Laskutusosoite (sposti) OR verkkolaskutustunnus+verkkolaskutusoperaattori.
- Fname, lname, email, phone for contact person for the application stage (individual user accounts created later, this person's info is only kept for emergencies, or if no one creates their account)
- Asiointikieli EN/FI for messages related to joining as a member association (members otherwise select their own languages for member letters etc)

=> Creates ASSOC profile in pending members + summary and email notification to jasenpalvelut@moniheli.fi

# data[].attributes.body
- Email receipt of application saved to board folder + attachments in case the attachment links are not in the receipt
- Board approves association

=> ASSOC profile from Pending members is accepted
=> Automation message 1: Welcome to the network
=> Automation message 2: Share the email to all your association members who want to access our services + create your own profile
=> Billing, manually in Netvisor based on ASSOC billing info

# data[].attributes.headline
Automessage 1: Welcome to the Moniheli network! (to contact in ASSOC profile, in chosen asiointikieli)

# data[].attributes.subject
Automessage 1: Welcome to the Moniheli network! (to contact in ASSOC profile, in chosen asiointikieli)

# data[].attributes.body
Thanks and welcome, you're approved and we're happy you're there. We will send shortly the bill to the billing address.

Our general services and member-specific services are listed HERE.

Book a time for the INTRO INTERVIEW (could lead to booking calendar for the walk-in time) where we can get to know each other.

You will shortly receive a second email to create individual profiles. These give you access to XXXX. We recommend that anyone in your association eager to make use of our services and trainings, and to get to know and cooperate with others in the network, would join our pages. Please pass on the message to anyone in your association that's relevant.

=> ACTION BUTTON TO member reg form.

# data[].attributes.headline
Automessage 2: Create your profile to use Moniheli's services (to main contact people, both in Finnish and English)

# data[].attributes.subject
Automessage 2: Create your profile to use Moniheli's services (to main contact people, both in Finnish and English)

# data[].attributes.body
Hello! Your association ASSOC NAME is now a Moniheli member association. You are welcome to join our platform to access the following services:
- XXXXXX incl member letter (1-2 times a month)
- discussion platform
- resources for associations, document templates
- discussion forum if any (later)

Moniheli's Member pages are open to any member or volunteer of a Moniheli member association. Please forward this message to all relevant people in your association such as board members, staff and active volunteers.

BIG BUTTON to access USER form

# data[].attributes.body
Most likely via Netvisor? In which case I will need better guidance to mass-send membership bills (might be checked with Nina Rehell in a few weeks)

Setting up payment through the website is not a good option, since many member associations need a bill, require e-billing or PDF billing. For other members it might make it easier but not worth the hassle I think.

# data[].attributes.body
Form should be only accessible by link. Fields:
- Association name (either Select from list, ideally if we can pull the list of assocs from the database, OR, enter the association's y-tunnus + open field for the assoc name)
- fname, lname, phone, email
- preferred language (also for member letters)
- ROLE in association: PJ, VPJ, treasurer, secretary, board member; ED or similar, other employee, intern, volunteer, other member
- If luottamustehtävä, when does your current term ends (calendar)
- Do you have the right to sign for the assoc (y/n, we check from the PRH-ote before approving)
Communications options:
- Member letter (1-2 times a month with Moniheli's events and opportunities)
- Membership issues: Can we send you invitations to General Assemblies and requests to update the background information and billing info of your association?
- POSSIBLY newsletter, if we switch from MailChimp to FluentCRM for it as well
- GDPR + contact use: can we contact you, can we pass on your contact info if we see it fit

Later, depending on member page use:
- Personal picture (for the forums)?
- Extra fields for the forum, like who are you or something

=> USER profile created, this probably autosends a password creation message? to be checked!

# data[].attributes.body
- 1-2 times a year a request to update the ASSOC info by email to contact persons?
- Update requests for individual user profiles twice a year for those whose term is ended + what to do-

# data[].attributes.body
- USER info changes => users can update it themselves in the pages
- ASSOC info changes => ❓❓❓

❓ Can we / How to have certain roles in the association have access to the ASSOC info and be able to update it while being logged to their USER account??? Could it be possible to make a page that would be only accessible for users with a certain role (signing rights for example, or main contact person role, tbd), and include a form that would be populated with the background info from the ASSOC that is linked to their profile?

# data[].attributes.headline
// not updated after this point, the rest are mostly general notes about future development

# data[].attributes.subject
// not updated after this point, the rest are mostly general notes about future development

# data[].attributes.headline
ON HOLD 2022! Probably not needed // DISCUSSION BOARD?

# data[].attributes.subject
ON HOLD 2022! Probably not needed // DISCUSSION BOARD?

# data[].attributes.body
To make it worthwhile registering for the website when almost all contents are (and must be according to STEA) publicly accessible, the member pages must be providing a service focused on community. Slack was suggested by some members but it is not possible to seamlessly integrate it with the website login, and it might be too complex for many users in our network.

Having a simple discussion board might let us organise in an efficient way direct contact between member associations, as well as provide a springboard for the theme groups to be in touch with each other (they can setup their own Slack if they want).

After reading recommendation lists, browsing through fully compatible, widely used and well-rated plugins in the Wordpress dashboard, I believe that wpForo would be the best option as long as the login to it and profile is integration with the website's login and profile.

❓ Can wpForo be installed and integrated to our current website?
❓ Is the login and profile for wpForo integrated with the login and profile for the member pages? The forum should be accessible only to members.

# data[].attributes.headline
Other message templates or automations needed

# data[].attributes.subject
Other message templates or automations needed

# data[].attributes.body
- ASSOC info update once a year
- own contact info twice a year (check if your role is up to date, if your other info is up to date, if you are not the contact person anymore then ask the next person to register)
- Cleaning up yearly unpaid members

# data[].attributes.headline
IMPLEMENTED 2022! Moniheli Grant application

# data[].attributes.subject
IMPLEMENTED 2022! Moniheli Grant application

# data[].attributes.body
The application and reporting forms would need to have a draft saved at server level, so SurveyMonkey is the most suitable tool at our disposal currently unless we want to bring the whole setup also to our website's pages, with all the complexity of finding a plugin for forms where drafts could be saved, ensuring correct user roles etc and uncertainly about how the grant would be applied in the future.

The save to server level is only possible with SurveyMonkey email invitations, so that's the option on the table now. In this case the only thing needing collection would be the email addresses of the users needing the application from via SurveyMonkey. These could be collected through a form anywhere, either public or member pages.