Dear all,
We would like to not only add more optional user fields at sign-up for organizations but also a short introductory text at the beginning in which we explain why such additional information would be helpful for us. Is it possible to add such a text, and if yes, how?
Furthermore, we would like to add some sort of “license policy” under the user fields with which the users agree upon sign-up. How is this feasible?
To add additional info you can create a simple theme component and add it to the main theme(s) on your site. You need only to insert in the Common/CSS tab something like this:
.d-modal.create-account .login-form table:before {
content: " EXTRA TEXT HERE EXTRA TEXT HERE EXTRA TEXT HERE EXTRA TEXT HERE EXTRA TEXT HERE EXTRA TEXT HERE ";
}
There is already something similar at the end of the form, but you can add more text if needed. Go to the /admin/customize/site_texts page, search for By registering, you agree to the to find the correct template and edit it or add more text.
Thanks a lot for your quick response!
I’ve got another question:
We want to make registration possible for the general public as well as to experts from organizations, institutions, etc. From the latter, we would like to ask more information than from the general public.
Our idea is, therefore, to first ask for e-mail, name, username and password and then add a confirmation or dropdown box, in which we ask the registering person whether he*she belongs to an organization. So far, so easy.
However, we would like the extra fields to be filled out by experts only to pop up if the person clicks yes. If no, the next step would simply to create a new account.
I hope it became clear what we are trying to set up.
Is this technically feasible?
ATM this is not possible do what you want on Discourse, but you should be able to do it using an external site (for example a WordPress site) and enabling the SSO from WP to Discourse. You could create the custom user fields on Discourse without enable the 'Editable after signup" option for the fields. In this way the user fields could only be filled in on the WordPress end.