The "Default to creating reports/updates as the council" permission only changes the default "Report as" / "Provide update as" dropdown selection in the normal reporting/updating flow/form, it doesn't at present have any effect on the 'inspect area' form. It certainly could do, do raise a ticket about it.
I don't understand the "names are displayed publicly" aspect, though - the update created by filling in the inspect area form does not supply a name to use, and the default code for updates is for any staff user to use the associated body's name on that update, not the user's name. I've just tested this and indeed, the update I made used the body's name on it. Are you seeing the names because you have the view permission to see the actual user name on updates?
I don't understand the "names are displayed publicly" aspect, though - the update created by filling in the inspect area form does not supply a name to use, and the default code for updates is for any staff user to use the associated body's name on that update, not the user's name. I've just tested this and indeed, the update I made used the body's name on it. Are you seeing the names because you have the view permission to see the actual user name on updates?How strange! The name is visible publicly as you can see here:
If `always_view_body_contribute_details` is not used then it doesn't make any difference whether an update is made via...
- the inspect UI,
- the normal flow with "as body" selected, or
- the normal flow with "as user" selected
... as long as the user in question is a body user, correct?