Redacted Fields in the Audit Log
Overview
For security reasons, certain sensitive fields are intentionally redacted in the Audit Log. When you view the details of an audit entry, some values may appear as hidden or masked. This is by design—it protects sensitive information while still providing visibility into what changed and when.
This guide explains which fields are redacted and why.
Pre-requisites
Role Requirements
Access to the Audit Log requires:
Owner – Full access
Admin – Full access
Even with full access, redacted fields remain hidden for security purposes.
Redacted Field Categories
Authentication & Security
These fields are always redacted to protect platform security:
Field | Why It's Redacted |
|---|---|
API Key | Prevents exposure of API credentials |
Encrypted API Key | Security-sensitive credential storage |
Access Token | OAuth tokens must remain confidential |
Refresh Token | Used for token renewal—highly sensitive |
Content Identifiers
These technical identifiers are redacted as they serve no user-facing purpose:
Field | Why It's Redacted |
|---|---|
Document | Internal file reference |
S3 Key | Cloud storage path—internal use only |
GUID | Global unique identifier |
GUID Source | Identifier origin |
GUID Published At | Identifier timestamp |
Unique Identifier | Internal reference key |
E-Learning Packages
For SCORM and xAPI content:
Field | Why It's Redacted |
|---|---|
Rustici Package ID | Third-party e-learning system reference |
Integration Settings
Configuration values that could expose system architecture:
Field | Why It's Redacted |
|---|---|
OAuth Application ID | Internal application reference |
Filters | Query configuration details |
Settings | System configuration values |
What You Can Still See
While specific values are redacted, the Audit Log still shows:
That a change occurred – You'll see the field was modified
Who made the change – The actor is always visible
When it happened – Timestamp is always shown
The type of change – Created, Updated, or Deleted
💡 Tip: If you need to verify what a redacted field was changed to, you can often check the current state of the record directly (e.g., view the user's profile, check the integration settings).
FAQs
Q: Why can't I see what an API key was changed to?
API keys and tokens are redacted to prevent credential exposure. If you need to verify an API key, regenerate it through Settings > API & Data Imports.
Q: The audit entry shows a change but the value is hidden—is this a bug?
No, this is intentional security behaviour. The field is one of the protected categories listed above.
Q: Can I request to see redacted values?
No. Redaction is a platform-wide security measure that cannot be overridden, even for Owners. This protects against insider threats and ensures compliance with security best practices.
Q: Do redacted changes count towards my audit history?
Yes. All changes are logged and retained for 18 months, regardless of whether specific values are displayed.
Q: How do I audit API credential changes if the values are hidden?
You can see when credentials were created, updated, or regenerated, and by whom. For the actual values, check the current state in Settings or regenerate if needed.
Troubleshooting
Issue | Solution |
|---|---|
Expected field value not visible | Check if it's in the redacted categories above—this is expected behaviour |
Need to verify a redacted setting | Check the current state of the record directly in the relevant settings area |
Concerned about unauthorised credential changes | Review the actor and timestamp; reset credentials if suspicious |