We currently expose all fields on nodes, terms, situations, drafts and so to none logged in users. Some of these fields are not useful to not logged in users and prob. should not be exposed.
Scope of issue
Figure out what fields should not be exposed to none logged in users. This req. filling out all fields in all content types and situations to flush them all out.
Fields to hide
- Record status:
field_record_status Content type: Creative WorkSituation.
- Notes:
field_notes Content type: Creative Work, Person, Situation.
- Optional notes:
field_optional_notes Content type: Character.
- KB editor notes:
field_editorial_notes Content type: Person.
Hide properties and other type of data that is not fields
- Authored by
- UUID (generated)
original report
User can see both "record status" and "UUID" without logging in. It is probably a bug.

We currently expose all fields on nodes, terms, situations, drafts and so to none logged in users. Some of these fields are not useful to not logged in users and prob. should not be exposed.
Scope of issue
Figure out what fields should not be exposed to none logged in users. This req. filling out all fields in all content types and situations to flush them all out.
Fields to hide
field_record_statusContent type:Creative WorkSituation.field_notesContent type:Creative Work, Person, Situation.field_optional_notesContent type:Character.field_editorial_notesContent type:Person.Hide properties and other type of data that is not fields
original report