Which data cannot be found in the Admin audit log?

• A. Timestamp
• B. Type of user
• C. Action performed
• D. Board name

Answer: (B)

The Admin audit log is designed to capture events with precise context: when something happened (timestamp), what action was performed, and which board or resource was affected, along with who performed the action. This combination lets admins trace activities and understand the exact sequence of events.

What isn’t included as a separate field is a labeled category for the user, such as a general “type of user” (admin vs member vs guest) within each log entry. The log records who acted, but doesn’t provide a defined user-type attribute for that event. To know a user’s role, you’d refer to their account outside the log, rather than a dedicated type field in the audit entry.