> For the complete documentation index, see [llms.txt](https://docs.teranode.group/tng-identity-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teranode.group/tng-identity-documentation/tng-identity-verifier/how-to-become-a-verifier.md).

# How to become a Verifier?

## Operating an Verifier

There are different ways to operate an issuer:

* Manually through our Issuer Portal: Allows you to do all the same actions listed in out platform. [Create an account for free today. ](https://products.teranode.group/)​
* Or using [TNG Verifier's API](/tng-identity-documentation/tng-identity-verifier/verifier-api.md), which allows you to manage issue credentials and establish connections with holders and Issuers programatically.

***

## What can verifiers do?

{% embed url="<https://youtu.be/edXBw-01cMQ>" %}

Verifiers can join the process by signing up on the **TNG Platform** or integrating with our **Verifier API**. The portal provides a clean UI to create verification requests (QR/link), configure a one-time **challenge**, receive presentations from holders, and review the cryptographic results and context before making a decision.

**TNG Verifier** gives teams control over the end-to-end verification workflow and portal roles/permissions, including: **defining required claims and policies**, **managing trusted issuers**, **verifying issuer signatures and credential status** (expiry/revocation), **binding the subject to the presenter**, **issuing pass/fail decisions with audit logs**, and **surfacing results via UI, webhooks, or receipts** for downstream systems.

## Credentials in the Verifier Portal

| Actions                            | Description                                                                                                                                                                                                                   |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Select a template for verification | Choose the verification template (policy) that defines the required credential type/schema, claims to check, and trusted issuers.                                                                                             |
| Verify a credential                | Start a verification by scanning a QR code or pasting a link/presentation; the portal validates issuer signature, expiry/revocation status, and subject binding against the selected template and returns a pass/fail result. |
| Review credential                  | Open the verification result summary for a single credential, showing its type, issuer, subject, current status, and which policy checks passed or failed.                                                                    |
| Review credential history          | View the audit trail of events (issued, claimed, revoked, updated) for that credential.                                                                                                                                       |
| Review credential information      | Open the detail view with all claims and metadata, including current status and subject.                                                                                                                                      |

## User Management in the Verifier Portal <a href="#user-management-in-issuer-portal" id="user-management-in-issuer-portal"></a>

| Action                             | Description                                                                                                                 |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Invite a user to the Issuer Portal | Send an invitation email with a link for the person to join your organisation’s Issuer Portal, choosing their initial role. |
| Assign a role to the user          | Set the user’s permissions (e.g., Viewer, Issuer, Admin) for your organisation/environment.                                 |
| Upgrade role of the user           | Increase the user’s permission level to grant more capabilities.                                                            |
| Downgrade role of the user         | Reduce the user’s permission level to limit capabilities; the account remains active.                                       |
| Delete the user                    | Remove the user from the organisation and revoke their access to the Issuer Portal (audit trail is kept).                   |

<br>
