# Specifying additional documents to be captured ## Scope and provenance - Product: web - Status: Imported reference snapshot. Import date is not a verification date or guarantee of current release support. - SDK version: Not declared for this page. Versions in examples must not be assumed current. - Environment: Page-specific. Confirm the environment host, credentials, and service configuration; do not infer them from another product. - Source: https://websdk2docs.idmission.com/other/specifying-additional-documents - Imported at: 2026-10-21T17:27:01.149Z - Canonical page: https://docs.idmission.com/web/other/specifying-additional-documents - Agent index: https://docs.idmission.com/llms.txt --- ### Specifying additional documents to be captured Many customer flow documented above include a `captureAdditionalDocuments` property, which allows for an array of documents to be specified in the order that they will be captured in. **Additional Document Properties** | | | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string indicating the name of document to be captured | | `description` (optional) | string describing to the user anything extra about the document that they should know | | `skip` (optional) | async function that may return a boolean indicating whether this document should be skipped | | `processAsPOA` (optional) | boolean indicating whether the document should be treated as a proof of address -- when true, the document will be processed and validated on the server. |