AdemeroHelp

Send new documents to a team's work queue

Every new document of a type lands on a team's Work tab without anyone forwarding it — a Content Capture trigger and a Work Queue - Assign action, with an optional expiration so items don't pile up forever.

Catalog administratorsContent Central 7.8+15 minutesVerified 2026-09-05

Before you begin

  • The receiving group (or users) exists in Content Central
  • The document type allows work-queue assignment (Allow Work-Queue Assignment permission)

When you're done, each new document of this type appears on the team's Work tab the moment it's filed, with a due date if you want one, and it leaves the queue when someone removes it — no forwarding, no email chain.

The planDocument type scope
  1. Trigger
    1. Content Capture › Content Captured in this Document TypeAny source, any format
  2. Action
    1. Work Queue - AssignWork-Queue Assignment Evaluation: Selected Group(s) · Selected Groups: the team · Expiration Type: Selected Expiration, 5 Days
  3. Rule
    1. "New document → team work queue", enabled

A work queue is a to-do pile; sending to a group puts one item in the group's shared pile, and the first member to take it, takes it. If you'd rather each person get their own copy, choose the users individually (see Variations).

Build the trigger

  1. Go to Administration > Catalogs & Document Types, pick the Catalog and Document Type, and click the Workflow tile. Click Triggers, then New Trigger.

  1. Type: Content Capture and Content Captured in this Document Type.

  1. Trigger Name: New document filed. Leave Source Evaluation:, Format Evaluation:, Field Evaluation:, and Capturing-User Evaluation: at their All / No Field Evaluation defaults.

  1. Click Save.

Build the action

  1. Click the Actions card, then New Action.

  1. Type: Work Queue - Assign. Action Name: Assign to HR team queue.

  1. Work-Queue Assignment Evaluation: Selected Group(s). Under Selected Groups, pick the team's group.

  1. Expiration Type: Selected Expiration, then set the Expiration to how long the item should sit before it ages out — 5 Days is a reasonable start. Leave it at No Expiration if items must never disappear on their own.

  1. Click Save.

Important

An expired item leaves the queue silently. Use an expiration for "nice to review" documents; for things that must be handled, keep No Expiration and pair it with the aging alert recipe instead.

Wire the rule

  1. Click the Rules card, then New Rule. Rule Name: New document → team work queue.

  1. Add Trigger: New document filed. Add Action: Assign to HR team queue. Click Apply.

Test it

  1. Capture one document into this document type.

  1. Have a member of the group open Work Queue from the left menu (the Queues page, Work tab).

What you should see: the document in the Work tab with a Date Received a few seconds after filing and your Expiration date. The document's View History shows the queue arrival.

If the item never appears: confirm the document type grants Allow Work-Queue Assignment to the workflow, and that the document was filed rather than left in the Coding Queue.

Variations

Want this insteadChange this
Each person on the team gets their own copyWork-Queue Assignment Evaluation: Selected User(s) and pick the people
Only documents scanned at the front deskTrigger: Source Evaluation: DirectScan Upload; or Capturing-User Evaluation: Selected User(s) with the front-desk login
Only documents missing a required fieldTrigger: Field Evaluation: Selected Field Lacks Value — the queue becomes a fix-the-coding pile
Route to a different team depending on a field valueOne trigger per value (Field Evaluation: Selected Field Value(s), Field-Match Type: Equals) and one action per team
Pull the item back out when a status field changesClear paid invoices from queues and file them
Notify the team by email as wellAdd a Send E-mail action to the same rule