I was answering a support ticket this morning and decided that it would be better to just create a forum post to answer as other users might have similar questions.

Question: It is unclear how an admin adds a new user themselves - how does this happen? The help file shows a + sign after the users in manage users - this doesn't show up on my implementation (maybe there is a setting I have missed?) 

Answer: The + sign not showing up is a bug we are researching and will be fixed shortly. This is simply an icon that redirects to a URL though that is the registration page with &AddUser=True to the URL. After adding this to the URL you can successfully add a user if you are an Administrator of the module.

Question: How do I create the DisplayName automatically from FirstName + " " + LastName? (is there an easier way than the SQL event?

Answer: Dynamic Registration automatically will make the Display Name the First / Last Name if you leave it blank (don't select any dynamic field from the DNN Core Integration area for the Display Name field type.

Question: There is no description of how the authorization process works - only that I can create a separate authorise field in the system, is liked to roles, and if so how? How does an admin authorise with this field?

Answer: Dynamic Registration authorization works in conjunction with the DNN Core User Registratino type. So under Admin, Site Settings, Advanced Settings it depends on what you have user registration set to. For example if you set it to Public the user would automatically be authorized and logged in after registration, if you set it Private the user would not be authorized etc... If you set it to Verified the user would not be authorized and you can use the $(VerificationCode) and $(VerificationCodeLink) within a Dynamic Completion Event to send the user the verification code. There are other options here as well, for example you could leave it as Public but within Dynamic Registration specify under Module Configuration, General Settings to not sign the user in after registration. This would still authorized the user but wouldn't sign them in after initial registration.

Question: There seem to be two methods of going to a page after registration - the completion event - navigate to URL, and the after registration goto page section (I think in module setup?) - I presume that I shouldn't use both, what are the benefits of the event method over the one in the modules?

Answer: Yes, this is somewhat related to the history of Dynamic Registration and features/enhancements added etc... So... basically use the settings under general settings for page redirection after initial registration and settings. The only time you need to use a completion event is if you want the page to be redirected differently than general settings based on a specific field type. For example maybe you want to redirect them normally to the home page unless they select 'Option A' from a dropdownlist and then you can complete a redirection completion event to 'Page A' etc... Completion events always override what is in general settings but I believe completion events for redirection event types required a Dynamic Field/Response and don't follow the same 'Any Field Response' like the other completion events work. So, short answer is only rely on redirection completion events if you want to redirect based on the response to a field.

Question: Can I put twp email addresses in an email event?

Answer: Yes, just include a ; between email fields. Example might be $(EmailField1);$(EmailField2);youremail@zzz.com etc.... In the future we are adding the ability to also add a CC and BCC to the field.

Hope this answers a few questions. We have upcoming releases and updates that should be out soon. New features in the next release include several client side events that can be fired and also integration with Authorizenet and possibly PayPal for a seamless user registration/subscription process at the same time.

-Chad