The ability to let users register themselves is very useful. However, we have 2 additional requirements:

1) We'd like the potential user to submit a few additional fields in which they enter their institution and brief reason for requesting access.

2) Before the new account is actually given meaningful access, we'd like our admin to formally approve that request. For the time being, I believe 'access' means adding membership to the right group, which I'm OK with being an ad hoc kind of thing. I would be OK with the user being automatically created through the LabKey process, and only actually receiving access when our admin adds them to the group. However, our admin needs some way to know they need to follow up on this user and to make sure requests dont get lost. I would also be OK with this extra information being sent as an email, rather than persisting the DB if that ended up being easier.

Is there a good way to extend the core request process? Given our requirement to capture additional information upfront, I dont see a good option other than to largely roll our own solution. I'd probably make our own custom java RequestLoginAction, which captures the user input, stores it in a table, and gives our admin some kind of action to 'approve'. The latter would actually create the user, ideally kick off a regular user/password email, etc. It doesnt seem like that much work; however, I'm open to other ideas if this could be more aligned with core labkey.

Thanks for any ideas,
Ben