I had a request to support fields that weren’t visible to the end users when they used the system. I decided to support these “administrative” fields as I have been referring to them by enhancing the optional fields for swimmers and users to be tagged as “user” fields or “administrative” fields.
When a field is defined as “administrative”, only users with WordPress permissions of EDITOR or higher will have the fields visible. For all other users, they are hidden. An Admin or Editor can change the value of the field and it will be saved when the user or swimmer data is saved.
The first practical usage of this is with a team that wants to mark registration fees as paid on a per swimmer basis. Not the sort of thing you would expose to a parent but useful from a logistics perspective.
Both user and administrative fields are available in reports.