Understand audit actor and network evidence
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that what each audit row can store.
Where to goTechnical/admin case evidence → license_application_audit
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What this guide helps you do
Know what each audit row can store. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the relevant case or email settings.
- Identify the trigger, recipient, subject or audit event described.
- Correct contact or SMTP configuration where needed.
- Use a controlled new action only after confirming the original record was already saved.
Fields and options
Storedapplication ID, event summary, actor type/id, IP address, timestamp
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-notifications-audit/
Rules and limits
- The model records email outcomes in audit evidence and does not roll back the case transaction solely because email fails.
Check it worked
- Understand audit actor and network evidence completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.
Related guides
Was this guide useful?Your response is stored only in this browser.