Appearance
Application detail — Activity tab
The Activity tab is the audit timeline for one application: who did what, when the system ran automations, and how the application moved through steps. It is read-only — you do not send email or change status from here.
Select Activity as the last tab in the main tab bar.
[NEEDS SCREENSHOT: Activity tab with This week accordion expanded]
Layout
Events are grouped into collapsible accordions by time. On first load, all non-empty groups open automatically.
| Group title | What it contains |
|---|---|
| This week | Events since start of current week (Sunday-based) |
| This month | Earlier in the current calendar month |
| {Month name} | Earlier in the current year (e.g. April) |
| {Month} {Year} | Previous years (e.g. March 2025) |
Click a group header to expand or collapse it.
If there is no history, the page shows: No application history.
Each timeline entry
Every line includes:
- Icon rail — dashed vertical connector between events
- System (database icon) for automated events
- User (person icon) for actions by a team member
- Header line — actor name (System or user display name), optional badge text from the event, and timestamp
- Description — plain language summary of the event
Event types and visuals
| Type | What you see |
|---|---|
| update | Description text; variable names with underscores may render as badges in the sentence |
| step_change | Previous step badge → arrow → new step badge (labels from your tenant’s step dictionary when available) |
| consent | Unchecked box → checked box (consent captured) |
| view | Hidden eye → visible eye (visibility change) |
| app_assign | Assignment changes (in description) |
| document_status_update | Document approved/rejected/requested (in description) |
Other types fall back to description text only.
Step names
When tab_dict is configured for your tenant, step codes in step_change events show friendly labels (e.g. UNDERWRITING → Underwriting). Otherwise raw step codes appear.
What Activity is good for
- Compliance and audits — prove when status, assignment, or consent changed
- Debugging — see order of integration runs, doc reviews, and variable updates (alongside Integration and Data tabs)
- Handoffs — new assignee reads Activity before calling the applicant
- Customer calls — CSR confirms “when did we request documents?” without opening Email history
Activity does not replace Email history (delivery status) or Notes (internal-only commentary).
Loading state
While history loads, skeleton blocks approximate accordion sections.
Sidebar width
When the right rail (Overview, SMS, Notes) is expanded, the Activity column may use a narrower width (~70% of content area). Collapse the right rail for a wider timeline when reviewing long descriptions.
Related topics
- Email and communications — outbound messages with delivery status
- Documents — document review actions that appear in Activity
- Application detail overview — Update Status in the header; section edit on Application tab
- Use cases — audit and escalation scenarios
- Workflows — when to check Activity vs other tabs