CiviCRM Community Forums (archive)

Hi all,

I'm in need of being able to have users being confirm and authorized for the events they register for. That way, admin can approve them.

I envision the following process

1. One registers for an event (enters email and other event specific information)
2. Confirms information on the screen (as is the case now).
3. Instead of being automatically registered (as is the case now), i want all information to be saved for admin approval.
4. After admin approval they are allowed to register to event and their payment processed.
5. Once approved, the individual is - then - registered for the event.

Can this be done easily? Let me know.

I am in - urgent - need for this functionality. If you can help me i would really appreciate it.

Thanks in advance

Albi

This would definitely be coding issue and would be a good community contribution to the code base.

Easy is a relative term. If you have a competent programmer willing to work with the core team (Dave & Lobo) to understand how CiviCRM works, it should be relatively easy. I'll let Lobo offer you a time estimate.

The best way to get started is to connect with Lobo on IM, start coding it, and get it back into the codebase.

Yes I agree on this ....this is a good feature and allows the admin to approve the registered participants and payments.

One sense you are in total control of the registration process.

One more good point is you can deny registrations and payment if admin smells something wrong with the registered participant and payment.

This should be as an option for admin for all events and the payment processes.

This is an excellent option to protect your system/event from abuse of introducers and competitors.

In order to keep this from becoming a big project and a potential security nightmare(you don't the hassle of what is required to protect those stored CC #'s) How about this flow instead

- When creating an event it is flagged as requiring administrator approval. This would create the registration page as normal and also a page where the user could request access to that page. The "request access" page address would be the one displayed on the event description and one that you would mail out if you want them to bypass the description page.

- When the user goes to the "request access" page they enter all information except the CC #'s and in addition  to entering their info create an account with the CMS (drupal/joomla) being used so as to verify that contact e-mail.

- This ""request access" function when completed would have created an approval to be processed by the administrator.

- When the "request access" is approved by the admin, a unqiue authorization code(works only for this event/user combo) is sent to the user. This email also contains the actual registration page address

- when accessing the "actual registration page" for any event the event record is checked to see if it is restricted. If it is restricted, the user is required to enter the authorization code that they were sent before registration could proceed

- Then once the auth code is entered or for a normal open event the  event registration would proceed normally

- I hope that would minimize the modifications needed to the current event flow since most activity should be handled by new pages/modules (the auth code creation/processing)

I hope the idea helps who ever decides to work on this. I don't have a need for this at the moment and have other code I'm digging into and learning

I think this is what we want .... I have one additional request (yes, I gather we will need some custom work contributed , but want to get your thoughts on the concept)

1.   When creating an event, specify an additional 2 options:
a.   Require authorization
b.   Event is for one or more groups that are allowed to join that event.
2.   If the user has an account, and they are in the group, they are processed immediately.
a.   Any other case requires your steps for admin authorization.
b.   When authorizing admin has 2 options:
i.   Authorize
ii.   Authorize and add to group

This would allow us to manage multiple events that are restricted.  A Board Meeting, for example.

It sounds like this is going to help others too, what is the best process for getting some development help to do this?

Yikes - guess that will blow my $600 budget!  Any ideas for doing this on a shoestring.... we are a non-profit, all volunteers.  Guess it didn't seem that involved ....