Understand the submitted-to-authority timestamp
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 when submitted_to_authority_at is populated.
Where to goAdmin Area → Licence Applications → Case → Timeline
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 when submitted_to_authority_at is populated. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the case.
- Scroll to the timeline.
- Check the status label, description, actor and date.
- Compare client-visible items in a controlled client session when required.
Fields and options
Trigger statussubmitted_to_authority
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-status-timeline/
Rules and limits
- The model sets the timestamp during this status transition.
Check it worked
- Understand the submitted-to-authority timestamp 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.