# Configuring a Workflow for Matched Documents (RIM)

Admins can configure a document workflow to send matched documents for review and approval directly from the [Content Plan Hierarchy Viewer](/en/lr/59502/#multi-document-workflow) in RIM Submissions Vaults. This article discusses best practices for configuring document workflows for matched documents. See [Configuring Document Workflows](/en/lr/50498/ ) for detailed configuration instructions.

## Workflow Configuration Best Practices

When configuring a document workflow for matched documents, we recommend configuring an _Any Lifecycle_ workflow. The sections below highlight when to use _Any Lifecycle_ and when to use a _Specific Lifecycle_.

### Any Lifecycle Workflows

You should consider configuring an _Any Lifecycle_ workflow:

  * When the matched document's _Steady_ state version is locked to a content plan item and you want to include that document version in the workflow instead of the latest document version
  * When the matched documents have different lifecycles, for example, when _Labeling_ documents and _Safety_ documents are sent for review together
  * If some matched documents don't require a verdict; for example, Module 3 documents require review and approval, but Supporting Literature references are already in an _Approved_ state
  * When you don't want an _Action_ document workflow step to perform state change on specific states; for example, at the start of the workflow, you want to change the state from _Draft_ to _In Review_, but not from _Approved_ to _In Review_

In _Any Lifecycle_ workflows, _Action_ steps cannot update custom fields or fields specific to a lifecycle.

### Specific Lifecycle Workflows

You should consider configuring a _Specific Lifecycle_ workflow:

  * When none of the situations described above apply to your matched documents
  * When you want to have a _Single Verdict_ that applies to all matched documents
  * When you want to update custom document fields