> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/verification-methods/notarized-document-bypass.md).

# Notarized Document Bypass

***

### Overview

1Kosmos enables community/helpdesk administrators to add an affidavit to a user's web wallet, allowing them to become IAL2 certified users without the need to physically scan their documents.

An affidavit in 1Kosmos is a declaration made by the administrator certifying the authenticity of another user's Passport (PPT), Driving License (DL), or SSN. The administrator who creates the affidavit assumes responsibility for verifying the accuracy of the document.

### Why you'd use it

It lets a user reach **IAL2 certification without physically scanning their documents**. This is useful when document capture isn't practical or has already happened in person for example, when a user's identity has been confirmed face-to-face using notarized physical copies and you want that in-person check reflected in their wallet. Because the administrator certifies the document, they take on responsibility for its accuracy, which is what makes the affidavit a valid substitute for an automated scan.

### Where it lives

The affidavit is added from **Users > All Users** in AdminX by an authorized administrator, and it is stored in the user's **Identity Wallet**. The user can view it under **Dashboard > My Profile > Identity Wallet**, but cannot delete it.

### How it helps

* Removes the document-scanning step for users who have already been verified through notarized physical copies.
* Extends IAL2 enrollment to situations where automated capture isn't an option.
* Keeps the verification evidence in the same wallet as scanned documents, so downstream relying parties treat it consistently.
* Produces an auditable record an `E_AFFIDAVIT_ISSUED` event is logged whenever an affidavit is added (see Event logs).

{% hint style="warning" %}
Only administrators with **all** of the following permissions are authorized to add an affidavit:

* `user.affidavit.add`
* `users.view-user`
* `users.edit`
* `users.all-users`
  {% endhint %}

### Prerequisites

To add an affidavit, you need the following details for the document:

* Document type
* Expiry
* Document number

### Adding an affidavit

{% stepper %}
{% step %}
**Log in as a community administrator**

Log in to a tenant as a community administrator.
{% endstep %}

{% step %}
**Open the user**

Navigate to **Users > All Users** and select the user for whom you want to add the affidavit. 
{% endstep %}

{% step %}
**Start the affidavit**

Click **...** and select **Add an affidavit**.
{% endstep %}

{% step %}
**Enter the document details**

In the **Add Verification Evidence** window, select the document you want to add as an affidavit, then enter the document number and the expiry date of the document.
{% endstep %}

{% step %}
Click **Save**. The UI confirms that the new evidence has been added.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/identity-verification/verification-methods/notarized-document-bypass.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.