CORINTHIAN.

Inbox Views & Queues

Understand how personal queues, shared queues, filters, and status tabs divide inbox work.

The inbox is not one flat list. Corinthian splits the work into personal queues, broader queues, and filter state so teams can separate ownership from intake without losing the thread history that keeps the work together.

Inbox views showing predefined queue shortcuts for common triage contexts. Inbox my threads showing the personal queue for assigned work. Inbox thread detail showing the open thread state that each inbox view ultimately drives into.

Typical Workflow

  1. Start in All threads or Not assigned to catch new or reopened work.
  2. Move owned work into My threads.
  3. Use status tabs and filters to cut the queue down to the segment you need to work.
  4. Open the selected thread and keep the queue context in the URL so you can move to the next item without resetting your search.

These queue views help you work one coherent segment instead of re-scanning the full inbox repeatedly.

Personal and broader work

My threads

Use Inbox → My Threads for work already assigned to you. This view defaults to a broader status view so personal execution work is easier to review.

All threads

Use Inbox → All Threads for the broadest queue available to you.

Not assigned

Use Inbox → Not Assigned to isolate threads that still need an owner.

Filter behavior

The queue supports:

  • status tabs: todo, snoozed, all
  • priority filter: urgent, high, normal, low
  • multi-label filtering
  • text search against thread context
  • natural-language AI filter parsing

Filters stay in the URL, which is why the queue context survives when you open a thread and move back.

Current limitation to know

Inbox visibility still follows ownership more than a fully shared team queue:

  • invoice-created threads inherit invoice ownership context
  • inbound-created threads inherit client ownership context
  • All threads is not yet a universal organization queue

Teams should account for that when comparing workloads across users.

State and action behavior

  • the list is grouped by priority and sorted by recent activity within each band
  • infinite loading is used for larger datasets
  • bulk actions support done and snooze
  • visible navigation includes a Views entry, but the browse and task pages are the more complete sub-experiences today

Troubleshooting

I filtered the queue and then lost my place

Re-open the page with the same URL parameters. Filter state is URL-backed and should restore the same segment.

All threads still seems incomplete

That is usually a visibility-model issue, not a broken filter. Compare ownership and assignee context before assuming data is missing.

Bulk actions do not offer every queue operation

Use per-thread controls for assignment and labeling changes.

Inbox Thread Lifecycle

Learn how thread state, timeline events, notes, reminders, follow-ups, and audit history evolve after an invoice enters the inbox.

Invoice Inbox

Work invoice replies as a queue with live thread history, metadata, follow-ups, labels, and payment context.

On this page

Typical WorkflowPersonal and broader workMy threadsAll threadsNot assignedFilter behaviorCurrent limitation to knowState and action behaviorTroubleshootingI filtered the queue and then lost my placeAll threads still seems incompleteBulk actions do not offer every queue operationRelated pages

We value your privacy

We use cookies to improve your experience, analyze traffic, and personalize content.