# How to become an issuer?

## Operating an issuer

There are different ways to operate an issuer:

* Manually through our Issuer Portal: Allows you to do all the same actions listed in ["How to become an issuer?](https://app.gitbook.com/o/-MlQFRDRKTg8X3AcjoU_/s/pNRD7nSXokLbc17tTyyL/~/changes/184/tng-identity-issuers/how-to-become-an-issuer) . [Create an account for free today. ](https://products.teranode.group/)​
* Or using [TNG Identity Issuer’s API](https://app.gitbook.com/o/-MlQFRDRKTg8X3AcjoU_/s/pNRD7nSXokLbc17tTyyL/~/changes/184/tng-identity-issuers/issuer-api), which allows you to manage issue credentials and establish connections with holders and verifiers programatically.

***

## What can issues do?

In the issuance of a Verifiable Credential (VC), issuers may conduct their own identity verification and validation steps before proceeding with issuance. Some issuers choose to independently verify the identity of subjects to ensure the integrity and authenticity of the credentials they issue.

Issuers can easily participate in the credential issuance process by signing up on the [TNG Platform](https://products.teranode.group/) or accessing our [Issuer API](/tng-identity-documentation/tng-identity-issuers/issuer-api.md). The platform offers a user-friendly interface, that helps issuers to create, revoke and maange Reusable Digital credentials. 

TNG Issuer ensures issuers to have control over the entire lifecycle of  credentials and user management roles and permission inside the portal, including: 

### Credentials in the Issuer Portal

| Actions                                    | Description                                                                                       |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| Issue a credential                         | Create and sign a new Verifiable Credential from a template for a specific subject/holder.        |
| Assign values to claims                    | Fill in the credential’s data fields (claims) before issuance—manually or via import/API.         |
| Add expiration date                        | Set when the credential becomes invalid; used during verification and for reminders.              |
| Revoke a credential                        | Mark the credential as no longer valid so future verifications fail (optionally record a reason). |
| Present a credential (for claiming)        | Generate a QR code or link so the subject can claim the credential into their wallet.             |
| Send a credential via email (for claiming) | Email the subject a claim link/QR to retrieve the credential into their wallet.                   |
| Assign an image to a credential template   | Attach a default image/logo to the template; shown in the portals and in the holder’s wallet.     |
| 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 Issuer Portal

| 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).                   |


---

# Agent Instructions: 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:

```
GET https://docs.teranode.group/tng-identity-documentation/tng-identity-issuers/how-to-become-an-issuer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.