Skip to contentVerifycate
ImprovedRecipient formsNo. 017

Choose what certificate applicants tell you

Edit the Issue Request Form fields, mark what is required, and match field keys to certificate Attributes so approved requests fill the certificate automatically.

By Ashwin Shenoy · Founder and engineer

An open request form that asks only for a name and email creates work later. The certificate may need a roll number, a team, a session, or a LinkedIn profile, and none of it is in the submission.

The Issue Request Form now has a field editor.

What you can configure

Add the fields the certificate actually needs, choose which are required, and decide whether the form is open to anyone with the link or limited to recipients already on the certificate. The form editor is under Issue Requests on a certificate, in the setup flow at Form Fields.

Field keys matter. A field whose key matches a certificate Attribute is applied to the issued certificate automatically. A field without a matching Attribute is still stored with the request, but it does not appear on the certificate unless you add it later.

Useful configurations

A university form can collect a roll number and programme. A hackathon form can collect team name and track. A webinar form can ask which session the person attended. A training provider can ask for a LinkedIn profile or a portfolio link before issuing a completion certificate.

The limit

The form collects what you ask for. It does not verify attendance or eligibility. If those checks matter, use Review Before Issuing and inspect the submission before accepting it.

The form is a Pro feature. Submitting a request does not spend a credit; issuing the certificate does.

Related

← Back to all updates

Start issuing

Certificates people can prove.

Design once, issue in bulk or from your LMS, and give every recipient a public page anyone can verify.