> For the complete documentation index, see [llms.txt](https://docs.toolkit.equs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolkit.equs.ai/docs/issuance/flow-1/auto-issuance/method-2-operator-portal.md).

# Method 2: Operator Portal

Issue a credential to one of your users from the Operator Portal, with no integration at all

The Operator Portal covers this journey without you writing anything. It suits issuance that is occasional, manual, or run by staff rather than software - and it is the Portal's production path.

**Before you start** you need an [Issuer and VC Schema](/docs/issuance/configuration-issuer-and-vc-schema.md), and your identity provider registered with the platform - see [Bring Your Own IdP](/docs/onboarding/bring-your-own-idp.md).

### Issue the credential

Open **Issuance** in [the Portal](https://portal.us.equs.ai/) and press **Issue VC**. In the modal:

{% stepper %}
{% step %}

#### Set the issuance method to **Auto issuance**

The other option, *Issue by user*, shows the Offer as a QR code instead - that is [`pull` tx\_code delivery](/docs/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery.md), and it is meant for demos and assisted issuance rather than volume.
{% endstep %}

{% step %}

#### Choose the Issuer and the VC Schema

Both are required. If you haven't created them yet, the **＋** beside each field creates one without leaving the modal.
{% endstep %}

{% step %}

#### Enter the Holder's user ID and email

The user ID is your own identifier for them - the same subject your IdP reports at sign-in. The email is where the notification goes, and it is required for auto-issuance.
{% endstep %}

{% step %}

#### Fill in the claims

The claims panel is built from the Schema you picked: one entry per claim, with the type of input the claim declares. The structure is fixed by the Schema and read-only here - you are supplying values, not shaping the credential. Every mandatory claim needs a value before **Issue VC** is enabled.
{% endstep %}
{% endstepper %}

<figure><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2F9PqI6KpnfF4bhJgF2y90%2Fimage.png?alt=media&amp;token=b7570c32-5b5f-42e4-aeac-baeed4e6981d" alt=""><figcaption></figcaption></figure>

### Track the result

The **Issuance** screen lists every Offer you have issued, newest first, with the Holder, Issuer, Schema, date and status. Filter by Issuer, Schema, status or date range.

| Status      | Meaning                                                      |
| ----------- | ------------------------------------------------------------ |
| `Pending`   | The Offer was created and is waiting for the Holder          |
| `Accepted`  | The Holder accepted it and the credential is on their device |
| `Declined`  | The Holder actively refused it                               |
| `Neglected` | The Holder never acted, and the Offer lapsed                 |
| `Expired`   | The credential was issued and has since passed its expiry    |
| `Revoked`   | You revoked the credential                                   |

Each row carries a revoke action. It is available only once the status is **Accepted** - before that there is no credential to revoke, so the action is shown but disabled.

The same record is readable over the API - see [Issuance Results](/docs/issuance/issuance-results.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.toolkit.equs.ai/docs/issuance/flow-1/auto-issuance/method-2-operator-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.