I'm new to the Create User Wizard so I've done some searching and haven't found the answer to this. I am happy with the way the wizard works and the info it collects, but we want to be in control of who is allowed to log into our site.
Ideally, if the user entered his own data and we were notified and could allow/deny access, that would be great. This site is for our employees and clients' employees, not competitors! When an employee leaves we'll disable their access. (This will be an internal screen one of us will manage.)
What is the best way to handle this? I'm imagining a bit (Boolean) column called [AllowAccess] in the aspnet_Users table.
1) Is there a problem if I add the field to this table? Should it be added to a separate table?
2) I can default the value to NotAllowed and send a notification (email or whatever) to the user who allows users via a SQL trigger. (What about bots? Will there be a gazillion records added? Do I need a Captcha thing? Dang, I hope not.)
3) Is there some way I can configure the Wizard to do this? Is my approach re-inventing the wheel?
Thanks for your thoughts.
Ideally, if the user entered his own data and we were notified and could allow/deny access, that would be great. This site is for our employees and clients' employees, not competitors! When an employee leaves we'll disable their access. (This will be an internal screen one of us will manage.)
What is the best way to handle this? I'm imagining a bit (Boolean) column called [AllowAccess] in the aspnet_Users table.
1) Is there a problem if I add the field to this table? Should it be added to a separate table?
2) I can default the value to NotAllowed and send a notification (email or whatever) to the user who allows users via a SQL trigger. (What about bots? Will there be a gazillion records added? Do I need a Captcha thing? Dang, I hope not.)
3) Is there some way I can configure the Wizard to do this? Is my approach re-inventing the wheel?
Thanks for your thoughts.