Skip to main content
Is it possible to disable this data filling:





We do not want to keep any personal data except e-mail.
Hmmm @Rodion I had a look in control, it looks like these are default fields that for some reason a admin or community manager cannot hide or remove.......not sure why.





Perhaps @Shane1 would be able to advise why we cannot make changes to these??
Hi @Rodion,





We have two default profile fields that are always set automatically and cannot be deleted. It is possible to change their visibility and whether they are required in control general settings/user profile fields.





Once you set the field visibility to hidden and not part of the registration, they are now shown to users at all and therefore no one is able to fill them in. This will be the equivalent of completely hiding these fields to users. Since they are default, there will always visible to moderators on user profiles in control.

Thanks @Maryam .


So this configuration means that a user will not somehow see, access and fill those profile fields? That's ok.
@Rodion exactly! ☺️
Perhaps @Shane1 would be able to advise why we cannot make changes to these??






Shane is not in the office this week, but I can explain why it is technically not possible to do this.





These fields belong to the standard setup of each community. A looong time ago, before you were able to add and change all these things by yourself, we used to set up all the profile fields for you.





As we thought that many communities want to use these profile fields as standard, we included them by default.





Just like with old (custom) Badges, things that once have been set up by a developer cannot be changed like other self-service items. So this is due to legacy-processes we have used back in the days.





We probably could change this (and we might as well do it), but at the moment we feel that working on improvements (like live-search) have a bigger impact on your community than an improvement of something that is easy to disable.





Cheers,





Julian

Reply