No saved views
This is the create-first empty state. Use it when a user has not configured anything yet.
Operational States
Empty vs no-results, loading, error, permission, activity history, files, and system notifications all in one place.
This is the create-first empty state. Use it when a user has not configured anything yet.
This is intentionally quieter than the empty state. The system has data, but this particular query did not find any.
Use a clear loading state for longer-running data refreshes instead of leaving a blank card.
Use this when the workflow broke and the user needs an obvious next step, not a generic alert buried inside the page.
Use the locked state for records that are temporarily unavailable because another process owns them.
An inline auto-refresh widget works well on queue and review pages where fresh data matters but the control should stay out of the main action area.
The shared queue filter is now available to the AP Team.
Use ephemeral notifications for asynchronous work that succeeded, failed, or is still in motion.
The payload normalized successfully and routed to the Needs Review queue.
This timeline variant works better than a plain list once actor, timestamp, and status all matter together.
Use this for audit-heavy pages where the sequence of events matters as much as the final state.
Use this for document-centric flows where operators collect several files before submission.