Overview

The AutoElevate Audit Log provides visibility into important configuration and account changes made within your AutoElevate environment. It records who made a change, what was changed, and when the change occurred, helping administrators troubleshoot issues, track administrative activity, and maintain audit readiness.

Audit Logs are especially valuable for organizations that need accountability for administrative actions, internal change tracking, compliance reporting, or security investigations.

What Is the Audit Log?

Audit Logs provide a historical record of supported administrative changes made within AutoElevate.

Each audit entry contains information about:

• The user who performed the action
• The date and time of the change
• The affected record
• The action performed
• The values that changed

This allows administrators to quickly determine how a setting was modified, when a user account was updated, or who performed a specific administrative action.

Current Audit Coverage

At the time of writing, Audit Logs track supported changes related to:

• User records
• Settings records

Only actual changes are recorded. If no values were modified, an audit entry is not created. 

Accessing Audit Logs

Open the AutoElevate Admin Portal

1. Sign in to the AutoElevate Admin Portal.
2. Select Audit Logs from the left navigation menu.
3. Review available audit records and filters.

If the Audit Logs option is not visible, your user role may not have the required permission to access audit records.

Understanding Audit Log Entries

Each row represents a recorded change.

Standard Fields

Viewing Change Details

Select any audit record to open the detailed view.

The details window displays:

• Record information
• User information
• Change timestamps
• Original values
• New values
• Field-by-field modifications

This allows administrators to understand exactly what was changed during an update.

Filtering Audit Logs

Filtering allows administrators to quickly locate specific changes.

Common Filter Scenarios

Use filtering when you need to:

• Investigate a configuration change
• Review activity during a specific timeframe
• Locate actions performed by a particular administrator
• Gather records for compliance reviews
• Research support incidents

Best Filtering Practices

• Start with a narrow date range.
• Filter by specific entity types when possible.
• Use correlation IDs when investigating multiple related changes.
• Export filtered results before making additional changes.

Exporting Audit Logs

Audit Logs can be exported for reporting, investigation, or compliance purposes.

Export Audit Data

1. Apply the desired filters.
2. Review the resulting records.
3. Select the CSV export option.
4. Save the exported file.

Exported data can be reviewed using:

• Microsoft Excel
• Security monitoring platforms
• Compliance reporting tools
• Internal audit procedures

Advanced Use Cases

Change Tracking

Use Audit Logs to determine:

• Who changed a setting
• When a modification occurred
• What values were changed
• Whether multiple changes occurred during the same administrative action

Compliance Reviews

Audit Logs help support:

• Internal security reviews
• Change management validation
• Administrative oversight
• Regulatory and policy-based evidence collection

Support Investigations

When troubleshooting unexpected system behavior, Audit Logs can help identify whether a recent configuration change may be contributing to the issue.

Best Practices

Review Administrative Activity Regularly

Establish a routine schedule to review audit records for unexpected or unauthorized configuration changes.

Export Important Records

If you require long-term retention for internal processes, export relevant audit data regularly.

Investigate Unexpected Changes

When a setting changes unexpectedly:

1. Locate the audit entry.
2. Review the acting user.
3. Compare original and new values.
4. Verify the change was intentional.

Use Audit Logs Alongside Other Reporting

Audit Logs provide change visibility, but use them with standard AutoElevate reporting and operational monitoring tools during investigations.

Security and Data Protection

Sensitive Information Protection

Audit Logs are designed to display only approved, non-sensitive information.

Sensitive information such as credentials is not included within audit records.

Access Control

Audit Log visibility is permission-based.

Users can only access information their role and organizational permissions allow them to view.

Audit Readiness

Audit Logs help organizations maintain accountability by preserving a record of supported administrative changes within the AutoElevate platform.

Troubleshooting

Audit Logs Menu Is Missing

Possible causes:

• Your role does not include the required Audit Log permission.
• Your administrator has not granted access.

Contact your AutoElevate administrator to review role assignments. 

Expected Change Is Not Visible

Possible causes:

• The activity falls outside the available viewing window.
• The record type is not currently tracked.
• No actual value changed.
• The action is not part of the current audit coverage.

User Can Only See Their Own Changes

This may be expected behavior based on organizational access permissions and assigned role permissions. 

Sensitive Information Does Not Appear

This is expected behavior. Sensitive information is intentionally excluded from audit records.

Frequently Asked Questions

How long are Audit Logs available?

Current documentation indicates the Audit Log interface is limited to approximately the most recent 30 days of activity.

What actions are currently tracked?

Current documentation states that Audit Logs track supported changes to Users and Settings. [

Can I export Audit Logs?

Yes. You can export the current filtered view to CSV format. 

Are passwords or credentials included?

No. Audit Logs do not expose sensitive information.