Apparently Registry goes through great lengths to prevent setting the 'modifiable' and 'hidden' attributes on several specific types of COPerson, COPersonRole, OrgIdentity or related attribute types.

I even found code to explicitely not honour the 'modifiable' attribute and display the attribute value as a suggestion for change instead.

As this is highly confusing for administrators, the suggestion is to remove all these exceptions and just allow defaults, modifiable and hidden settings for all attributes.

Any privacy and consent policies that should be honoured by the community as far as displaying attributes or allowing users to modify specific attributes during enrollment should be exactly that: policies of the administrator. They should not be forced upon by the platform.

To reference a specific piece of comment:

// Skip anything that's hidden. This will prevent us from setting a
// default value for metadata attributes, and will also prevent using
// default values in hidden attributes (which is probably a feature, not
// a bug).

Well, it looks like a bug.