> 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/standards/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery/method-3-operator-portal.md).

# Method 3: Operator Portal

Issue to one of your signed-in users from the Portal, with the Offer shown as a QR code

The Portal can drive this journey too: an operator fills in the credential and the Offer is presented on screen for the Holder to pick up with their wallet.

{% hint style="info" %}
In the Portal this is the **Issue by user** issuance method, which shows a QR code or opens the web wallet. It is intended primarily for demonstrations and assisted, over-the-counter issuance. For issuance at volume, use [Method 1: API](/standards/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery/method-1-api.md) - or **Auto issuance**, which is the Portal's production path.
{% endhint %}

**Before you start** you need an [Issuer and VC Schema](/standards/issuance/configuration-issuer-and-vc-schema.md), and your identity provider registered with the platform - see [Bring Your Own IdP](/standards/onboarding/bring-your-own-idp.md). The Holder has to be signed in to an EQUS Wallet as one of your users for the wallet to fetch the code.

### 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 **Issue by user**

This is the path that shows the Offer on screen. The other option, *Auto issuance*, sends it to the Holder's wallet instead - see [Auto-issuance](/standards/issuance/flow-1/auto-issuance.md).
{% 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

Your own identifier for them - the same subject your IdP reports at sign-in. That match is what lets their wallet fetch the `tx_code` on their behalf, so no email is needed here.
{% 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%2FQVmrJumEvZ4Phu44rVrO%2Fimage.png?alt=media&amp;token=7fd8e26c-6b45-4de9-9414-cc9ddb40e9fe" alt=""><figcaption></figcaption></figure>

The Offer is then shown for the Holder to scan or open. Because they are signed in as one of your users, their wallet fetches the `tx_code` itself - there is nothing to read out and nothing for them to type.

### Track the result

The **Issuance** list shows every Offer with its Holder, Issuer, Schema, date and status, filterable by any of them. Revocation is available from a row once its status is **Accepted**. See [Issuance Results](/standards/issuance/issuance-results.md) for the same record over the API.


---

# 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/standards/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery/method-3-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.