The Feature Audit Log gives System Admins a clear, chronological view of every feature configuration change made in Hi Marley. You can use it to track when features were enabled or disabled, who made the change, and quickly investigate unexpected behavior across your organization.
This feature is especially useful for maintaining accountability, supporting audits, and understanding how configuration changes may impact your workflows.
Who can access this feature
- System Admins can view and use the Feature Audit Log
- Access is available within Settings > Organization > Features
How to access the Feature Configuration Audit Log
- Navigate to Settings from the left-hand navigation
- Select Organization
- Click Features
- In the upper-right corner, click Audit Log
The Audit Log will open with a chronological list of all feature configuration changes for your organization.
What information is included
Each entry in the Feature Audit Log includes:
| Field | Description |
|---|---|
| Feature Name | The specific feature that was updated |
| Change Type | Indicates whether the feature was enabled or disabled |
| Date & Time | When the change occurred |
| Updated By | The name and email of the user who made the change |
This level of detail ensures full traceability and accountability for all feature configuration updates. :contentReference[oaicite:1]{index=1}
How to filter the Audit Log
You can narrow down results to quickly find what you’re looking for using the available filters:
- Start Date — View changes from a specific point in time
- End Date — Limit results to a defined timeframe
- Feature — Focus on changes to a specific feature
Using filters helps you isolate activity during key events such as releases, testing periods, or incident investigations. :contentReference[oaicite:2]{index=2}
Common use cases
- Investigate unexpected behavior
Quickly confirm whether a feature was recently enabled or disabled - Support UAT and production validation
Track configuration changes across environments and ensure expected settings are in place - Maintain accountability
Identify exactly who made a change and when it occurred - Prepare for audits and compliance reviews
Use the log as a reliable record of configuration history
Best practices
- Review the Audit Log whenever workflow or feature changes are made.
- Use date filters when investigating issues to reduce noise.
- Align Audit Log reviews with internal change management processes.
Note: The Feature Audit Log provides visibility into feature configuration changes only. For broader platform activity tracking, refer to your organization’s full audit logging and reporting workflows.
FAQs
Does the Audit Log show all platform activity?
No. The Feature Audit Log is specific to feature configuration changes (enable/disable actions). It does not include other user actions such as messaging or case updates.
Can I export the Audit Log?
Export functionality may vary by organization setup. If you need to retain records externally, check with your Hi Marley implementation team or internal admin configuration.
How far back does the Audit Log go?
The Audit Log maintains a historical record of feature changes. The available timeframe may depend on your organization’s data retention policies.
Why don’t I see the Audit Log button?
If you do not see the Audit Log button, confirm that you have System Admin permissions. If access is still unavailable, contact your internal administrator.
Comments
0 comments
Please sign in to leave a comment.