System — activity logs and error logs
The System section contains Activity logs and Error logs. These are for oversight and troubleshooting, not for day-to-day customer processing.
Activity logs
Activity logs record meaningful actions staff take in the system (who did what and when, depending on what the product captures). Use them to:
- Investigate “what happened” after a support question or audit request.
- Reconstruct a sequence of events when training new team members on correct procedures.
Who can access: Users with permission to view activity logs. This is usually a subset of staff, not everyone.
Error logs
Error logs help technical or senior staff see when something failed in the application. Use them when:
- A user reports an error and you need a timestamp or reference to share with support.
- You are following up on a recurring issue.
Who can access: Users with permission to view error logs. Treat the contents as internal: they may include technical detail that is not useful for external communications.
What not to do
- Do not use logs as a substitute for approvals or official records in finance or compliance processes unless your policy explicitly says so.
- Do not share raw error details with customers unless your security and communications policies allow it; prefer user-friendly summaries.
Related
- People and access — who can open these screens.
- Finance — when errors occur during posting or reporting.