Events have several classifications.
1) Events with the "Confirm participation" setting. I.e. with pre-registration.
2) Events without the "Confirm participation" setting. I.e. without prior registration.
Let's look at how statuses behave in events.
Event with pre-registration
It's like a closed event, that is, to get to it, you need approval from the platform administrator. Therefore, here the administrator should pay attention to the registration end date (after its occurrence and before the event, all user requests must be processed).
Initially, the user did not submit an application (while the link / address of the event is not visible in the application).
The user submits an application. In the admin panel, the participant gets the status "Submitted an application" (while the link / address of the event is not visible in the application). Now the administrator needs to consider the applications.
The user gets the status "Approved" if the administrator allows the event to be attended (now the link/address of the event is visible in the application).
The user gets the status "Denied" if the administrator prohibits the event (while the link / address of the event is not visible in the application).
After the start of the event, the statuses are automatically changed: participants in "Approved" get to "Confirm participation" (the link / address of the event is visible in the application); "Refused" remains in the same status (while the link / address of the event is not visible in the application). Here, "Confirm participation" implies that the administrator will mark users after the event (who was at the event and who skipped).
The administrator transfers the participating participants to the status "Participated" (the link / address of the event is visible in the application).
The administrator transfers the participating participants to the status "Missed" (the link / address of the event is visible in the application).
Event without prior registration
This is an open event where anyone can get in. In this case, the address/link to the event is always displayed in the user application.
Initially, the user did not submit an application.
The user signs up for the event and gets the status "Approved".
After the start of the event, the statuses are automatically changed: participants in "Approved" get to "Confirm participation". Here, Confirm participation implies that the administrator will mark users after the event (who was at the event and who skipped).
The administrator transfers the participating participants to the status "Participated".
The administrator transfers the participating participants to the status "Missed".
In addition to recording events on the part of users, there is a forced recording by the administrator (this can be done in the admin panel through manual addition or through import). The logic of the participants' statuses is the same as described above (using the example of a user record).
Status scheme:
It is possible to change the statuses from:
"Applications" → "Approved" or "Refused".
"Approved" → "Refused".
"Confirm participation" → "Participated" or "Absent".
"Participated" → "Absent".
"Absent" → "Participated".
"Refused" → "Approved" (the event has not yet come) or "Confirm participation" (the event has already come).