Review certificate requests before issuing
Choose manual review, automatic issue, or listed-recipient-only requests, then accept, reject with a reason, or reopen submissions from one inbox.
An open request form is convenient and easy to abuse. Someone who did not attend can submit their email; a person already on the list can submit twice; a walk-in may be legitimate but not yet verified.
The request flow now has three approval modes.
The three modes
Review Before Issuing. Every submission waits in Issue Requests until someone accepts it. Issue Automatically. A valid submission is issued and emailed immediately. Listed recipients only. The form only accepts an email already on the certificate, which stops strangers from requesting a certificate they were never part of.
Set the mode in the Issue Request setup flow. The inbox shows the submission, the applicant's details, and the requested certificate. Accept & Issue issues and emails the certificate. Reject sends your reason and issues nothing. Mark as Pending puts the request back in the queue.
Where it helps
A workshop with an open form can review submissions against the attendance record. A hackathon can reject duplicate team submissions. A university department can keep the form limited to registered students while still letting them claim a certificate they missed.
What it costs
Accepting a request spends one credit, like any other issue. Rejecting does not. Bulk accept is available when the queue is long, but the confirmation still shows how many certificates will be issued and what the batch costs.
Related