- π§πͺBelgium vodde83
I think I get what @Kris77 is referring to, I'm seeing this issue as well. That is, unless I misconfigured and/or overlooked something :)
There are basically 3 relevant roles in the website : A, B and X.
The roles A and B are for front-end users, and have their own profile type with specific fields.
The role X is pure back-end, and does not have a profile type.
Through use of https://www.drupal.org/project/multiple_registration β , the roles A and B each have their own registration page. Role X does not, as they're not supposed to go through the front-end to get an account.But if I - as a superadmin - want to create an additional back-end user with role X, I can't do so without filling in both the profile fields for A and B. All profile forms show up on '/admin/people/create', and some of them contain required fields.
So I can't just leave them blank.I think that either the respective profile form(s) should only appear when selecting a role that has a profile type connected to it, or the profile forms should not appear on '/admin/people/create' at all.
However, I can see situations where some back-end roles do have a profile type with additional fields that are required.