The Request Diploma Feature: Opt-In Document Issuance, Explained

The Request Diploma feature lets each recipient actively request their diploma or certificate instead of having one issued to them automatically. With it turned on, a document is only generated when the recipient asks for it. It is a simple switch with a clear purpose: put the choice to be issued a document in the recipient's hands.

Most of the time, automatic issuing is exactly what you want. A course ends, a document goes out, and the recipient gets their proof without lifting a finger. That flow is fast, hands-off, and right for the majority of cases. But there are situations where issuing on demand is the better fit, and that is what this feature is for.

What is the Request Diploma feature?

It is an issuance setting in TRUE. Normally, when you issue to a group, every recipient is automatically given their document. With the Request Diploma function switched on, recipients are not auto-issued anything. Instead, each person decides whether they want the document and requests it. Once they do, the document is generated and delivered.

You can think of it as the difference between push and pull. Automatic issuing pushes a document to everyone. Request Diploma waits for the recipient to pull it when they want it. Both produce the same blockchain-secured, verifiable document. The only thing that changes is who triggers the issuing.

When should you use opt-in issuance?

There are three situations where letting recipients request their own document makes the most sense.

1. Privacy and choice. Not everyone wants a diploma or certificate issued in their name. Some people would rather keep an achievement private, or simply do not want a public record of it. Opt-in issuance respects that. The recipient who wants their document requests it, and the recipient who does not is never issued one they did not ask for.

2. Recipients under 18. When the recipients are children, auto-issuing a document in their name is not always appropriate. Letting a young person, or their parent or guardian, request the document deliberately puts a clear, conscious step between the achievement and the issued record. It is a more careful way to handle documents for minors.

3. Paid documents as a revenue stream. A document can be a product in its own right. An organization can charge for a certificate of authenticity, for example, and turn issuing into a source of revenue. In that model you only want to issue to the people who actually want the document and are willing to pay for it, not push it out to everyone. Request Diploma fits this exactly: the recipient asks for the document, and you issue it to those who choose it.

How does it work for the recipient?

The recipient experience stays simple. Instead of arriving in their inbox finished, the document waits for them to ask. They request it, and TRUE generates and delivers the same branded, blockchain-secured document they would have received automatically. There is no second-class version of a requested document. It carries the same design, the same verification, and the same permanence as any other TRUE document.

For the issuer, the setting is a choice you make per use case. You decide where automatic issuing fits and where opt-in issuing fits. You can run automatic issuing for one program and Request Diploma for another. The platform does not force one model on everything you do.

Request Diploma vs automatic issuing

Neither model is the "advanced" one and neither is the fallback. They answer different questions.

• Automatic issuing answers: "How do I get documents to everyone quickly, with no manual step?" Use it for most courses, training, memberships, and events where everyone expects and wants their document.
• Request Diploma answers: "How do I make sure a document is only issued to someone who actively wants it?" Use it for privacy-sensitive groups, recipients under 18, and paid documents you sell as a product, such as certificates of authenticity.

The strength of having both is that you do not have to compromise. You match the issuing model to the situation rather than bending the situation to fit the platform.

Does a requested diploma look different from an auto-issued one?

No. A document issued through Request Diploma is identical in every way that matters. It lives on your own domain, carries your branding, and is verifiable by anyone through a QR code or your verification portal. It is secured by blockchain, which means it is tamper-proof and verifiable for good. The only difference is the moment it was created: when the recipient asked for it rather than the moment you issued to the group.

A quick recap

The Request Diploma feature gives recipients the choice to request their document instead of being auto-issued one. It is built for opt-in privacy, for handling documents for minors with care, and for paid documents you sell as a product, such as certificates of authenticity. Automatic issuing remains the right default for most cases. Request Diploma is there for the cases where deliberate, on-demand issuing is the better answer.

If you are weighing where automatic issuing fits and where opt-in issuing fits for your documents, we are glad to help you think it through and set it up.

FAQ

What is the Request Diploma feature in TRUE?
It is an issuance setting that turns off automatic document issuing for a group and lets each recipient request their diploma or certificate instead. The document is only generated when the recipient asks for it.

Why would I let recipients request their own diploma?
Three common reasons: to respect privacy so only people who want a document are issued one, to handle documents for recipients under 18 with a deliberate request step, and to sell documents as a product, such as certificates of authenticity, where you only issue to people who want and pay for them.

Is a requested document less secure or lower quality?
No. A requested document is identical to an automatically issued one. It is branded, lives on your own domain, is blockchain-secured, and is verifiable by anyone, anytime.

Can I use automatic issuing for some programs and Request Diploma for others?
Yes. Issuance is set per use case, so you can run automatic issuing where it fits and opt-in issuing where it fits, side by side.

Does Request Diploma replace automatic issuing?
No. Automatic issuing is the right choice for most cases. Request Diploma is an option for situations where opt-in, deliberate, or paid issuing makes more sense.