Use central security audit logging
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use the consolidated event trail for security-sensitive activity.
Where to goAutomatic core protection — no separate staff menu route
What this guide helps you do
Use the consolidated event trail for security-sensitive activity. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.
Follow these steps
- Use the supported Pixie CRM release or workflow that produces this security control.
- Check the expected protection through an authorised test.
- Record the result in the deployment or security audit evidence.
Fields and options
- Actor/token identity
- Event type
- Timestamp
- Source/context
- Outcome
Rules and limits
- Correlate actor/token, event type, time, source, context and outcome.
- Do not record plaintext passwords, reusable tokens or unnecessary sensitive content.
- Preserve events according to the authorised retention and investigation process.
Check it worked
- The protection is active without weakening another security control.
Security, audit and troubleshooting checks
- Use the exact authorised account, role and record before saving or sending.
- Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
- Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
- Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.
Related guides
Was this guide useful?Your response is stored only in this browser.