## Configuring Decision Logic

DocV decisioning is designed around two complementary layers. Each layer plays a different role, and together they determine both the Predictive Document Verification module’s internal decision and the final workflow outcome you return to your application.

1. **Predictive DocV Product Settings**  
   These settings control how the Predictive Document Verification module evaluates an ID. They determine:
   
   - How extracted data is interpreted (age, expiration, PII matching).
   - The module’s internal decision (`accept`, `review`, `resubmit`, `reject`).
   - Which reason codes are generated to explain that decision.
   
   Think of this layer as configuring how **DocV scores the document itself**.

2. **RiskOS™ Workflow Logic**  
   Once DocV returns a decision and its reason codes, you use RiskOS™ workflow logic to apply your business rules:
   
   - Allowed document types
   - Country/region restrictions
   - Reason-code overrides
   - Compliance requirements
   
   This layer determines the **final outcome** your app receives.

> 👍  
> **Tip**:  
> - **Product settings** shape DocV’s internal scoring and reason code output.  
> - **Workflow logic** produces the final decision (Accept / Reject / Resubmit / Review / Cancel) returned from RiskOS™.

## Access the RiskOS™ Dashboard  
To view the full DocV Decision Logic documentation, go to **Settings > Documentation > DocV Decision Logic** in the RiskOS™ Dashboard or use the links below.

| Environment | Dashboard Link |
| --- | --- |
| **Sandbox** | [Go to Sandbox Dashboard](https://riskos.sandbox.socure.com/accounts/documentation/docv-decision-logic) |
| **Production** | [Go to Production Dashboard](https://riskos.socure.com/accounts/documentation/docv-decision-logic) |

Updated 4 months ago

* * *