Which fields are NOT allowed on the Audit list view?

In the context of the Audit list view within a system, certain fields are restricted because they are either sensitive in nature or do not contribute to the utility of the audit log. The fields related to security and edit actions typically include critical information that could compromise the integrity of the audit process. For instance, allowing direct interactions with security settings or edit capabilities on the audit log could lead to manipulation or unauthorized changes, undermining the purpose of maintaining a clear and accurate audit trail.

Furthermore, the inclusion of specific fields in the audit view may be restricted to ensure clarity and focus, promoting essential fields that are useful for tracking user actions without cluttering the interface with unnecessary information. Fields such as Name and User, or Artifact ID and Document Type, tend to provide relevant information in auditing contexts, enabling administrators to trace actions back to specific users or documents without exposing security risks.

Therefore, the selection of security and edit fields as not allowed highlights an emphasis on maintaining the integrity and security of the audit log while still allowing useful and relevant information to be accessible to the users managing these logs.