Moderation of subscribers

[djulien19]

For an organization, there is always the possibility to accept or not a member. It could be the IRL meeting, the validation of documents or even some duties.
For that, we would like to get a process after the subscription of any member with a list of all queued subscribers with their status: in progress, paid and validated.

[djulien19]

Yannick you said that we could use the active tick in the membership form, that's all right for now. In the menu association, there will be to add this status in a column and to get the possibility to manage many members.

[YannickB]

Hum, you are speaking about many things here so I'll speak about what I understood during our offline meeting.

If I understood correctly, the subject was the access to the platform. This mean, you suggest that the administrator can choose if visitors can register and directly access to the platform, or go in a waiting list until administrator accept his access to the platform.

Note that I am not here speaking about the native option "Allow external users to sign up " in Settings / Configuration / General Settings. This option hide completely the sign up option in front.
I suggest to add another checkbox "Place new users in waiting list" in Settings / Configuration / General Settings, appearing only if Allow external users to sign up is True.

If "Place new users in waiting list" is True, then the active checkbox on new user will be set to False.
Also, since the active in false will hide the users, we need to create a specific menu "User awaiting access" to easily find them.
We need also a way to differentiate awaiting users and disactivated users, since both are based on the active field.

[djulien19]

and a process flow as a document? with the deactivation of the tickbox at the beginning as you suggest, with a specific menu depending of the status of the users

[djulien19]

the missing point concerning the status of members is that we cannot link from the beginning, from the mailinglist subscribers, the creation of a partner with three fields (contact name, email and phone), then the approach with the CRM module, the payment of membership fees, the activation of his account to his leaving (with a date at the end).

[YannickB]

I'm not sure I understand your last comment. Can you please describe the whole registering process according to you and the impact on different documents (user record, partner record, mailinglist, etc...)?

[lucode]

I think you should determine between membership to an organization and membership in the exchange system. They are not the same. If I have paid the annual fee I'm a member of the association, but maybe I don not fulfill yet a fully documentation or some dutys.

[lucode]

I see three levels of processing new members:

• Identity approval
• Member (association/organisation) approval
• Exchange system approval and control system~

~ For the exchange system I propose to two or three new profile fields (only access by admins?):
1 Active/Passice (bool)
2 Status (Dropdown text) {as for example: ok/questionable/Intake Process/In Disput}
3 Remarks
Field 1 and 2 could ev. be put together!

I would suggest that to maintain enough flexibility to offer a basic workflow for the the processing of this levels. Then every organisation can decide for themselves how to manage this.

To get an impression what are the needs for a business related system (barter) here you can download a BPMN scheme.
https://www.dropbox.com/s/cmt4ai80z76xas0/Jeema_User_Organisation%20Registration.pdf?dl=0