Permission
Use a company admin account with certificates:manage in the company you are working in. Real-employee private preview also requires employees:read, employees:read:own, or employees:read:all.
Import approved artwork, configure controlled replacement fields, complete the publication check, publish an immutable revision, and use the existing policy flow to issue a verifiable credential.
Live: certificate import is available to companies by default. A company-level block is reserved for emergency denial or rollback, and platform operations may still pause authoring or issuance independently for safety.
On this page
Use a company admin account with certificates:manage in the company you are working in. Real-employee private preview also requires employees:read, employees:read:own, or employees:read:all.
Prepare one safe, single-page PDF, PNG, or JPEG. Password-protected and multi-page PDFs are not supported.
Confirm that your organization has permission to use the artwork, logos, signatures, and fonts represented in the design.
IgniteIQ preserves the effective single-page PDF dimensions and rotation. It does not silently stretch the design to US Letter or the legacy editor ratio.
Confirm Landscape Letter, Landscape A4, or a custom physical size. Preserve aspect ratio unless you deliberately crop, and resolve any low-resolution warning before publication.
These values belong to the saved revision. Private preview, the publication check, and final issuance all resolve the same approved settings.
Control how the issue date is written, such as 11 July 2026 or Jul 11, 2026.
Controls which calendar date applies at the moment of issuance. It does not change the learner's completion record.
Provide approved static signer wording for fields that use those bindings.
Choose an approved ready signature asset. No signature is rendered when none is selected.
Provide the approved place-of-issue wording when the design includes that field.
Changing any setting makes the draft unsaved and the prior publication check stale. Save, preview the formatted example, then run the check again.
Test short and long names, accented text, Arabic or right-to-left text, long learning titles, and missing optional values. An eligible company learner may be selected for a private preview, but preview does not establish issuance eligibility.
The publication check renders the current saved draft and marks it PREVIEW — NOT VALID. Review alignment, replacement coverage, overflow, fonts, QR clearance, and page bounds. Any later draft edit makes that check stale.
The first successful publication activates the imported template. When default-on-publish is selected, publication atomically replaces only the current default for the same company and template type. When it is not selected, the current default stays unchanged. Default selection changes appearance only; completion, exam, approval, entitlement, plan, and issuance eligibility rules are unaffected.
Select the active published template in the existing certificate policy for the course or learning path. For a scheduled cohort certificate, choose the cohort's underlying learning path and configure the cohort policy; that policy still owns eligibility and issuance. Reusing a template is allowed, but every active certificate-enabled course still counts under the applicable plan rules.
Read the certificate issuance playbookThe existing completion, exam, approval, entitlement, and plan policy decides whether a learner is eligible. A published design never bypasses that decision.
After successful imported-template issuance, the learner accesses the authenticated final PDF from the certificate area. Existing certificate formats keep their established access behavior. A failed render does not expose a valid-looking partial certificate.
The Certificate ID and QR use certificate-specific platform values. Public verification confirms allowlisted credential status; it does not publish the imported source or final PDF.
Makes the template inactive and non-default. It does not alter its published revision or any issued credential.
Rechecks certificate-import availability, the current published revision, its source, and any selected signature asset before making the template active again.
You can discard an upload during import or discard its template later while it is still an unreferenced, never-published imported draft. Once any revision has been published, preserve its history with Archive and Restore instead of destructive deletion.
Use one supported, unencrypted, single-page file. Correct the reported file, safety, size, or geometry problem before trying again.
Recheck the confirmed physical size and fit mode. A PDF keeps its effective native page geometry; raster crop must be explicit.
Load authorized options and search with at least two characters when the list is large. Confirm your role can read employees, the company has an active employee, and a compatible published course or learning path exists; scheduled-cohort previews use the cohort's underlying learning path.
Reload the editor if prompted, save the current draft, refresh the authorized options, and generate the preview again. The preview will not use stale draft content.
Resolve every missing required field, font or text problem, overflow, opacity, QR spacing, asset, geometry, or uncovered old wording, then save and run the check again.
The draft changed after the last check. Save the current draft and run a new publication check before publishing.
Read the publication readiness checklist beside Publish. Save any edits, complete a current publication check, clear its blockers, then confirm that you reviewed the result.
Confirm that it belongs to the company, is active, and has a published revision.
Check the target certificate policy and its selected completion, exam, approval, entitlement, and plan rules. Template publication alone does not issue a credential.
For import, publication-check, publication, assignment, or issuance problems, include the safe user-facing error, the affected company, the step you were on, and whether retry changed the result. Do not email certificate source files or learner data unless support explicitly provides an approved secure path.
No. IgniteIQ preserves the original single-page design as locked artwork. You configure supported replacement fields over it; flattened artwork and original PDF authoring layers are not reconstructed.
Use one safe, single-page PDF, PNG, or JPEG. Encrypted, malformed, multi-page, unsupported, oversized, or unsafe files are rejected with a corrective message.
No. Publication requires a successful publication check for the current saved draft and an explicit confirmation that an authorized admin reviewed it. Editing the draft makes the previous check stale.
No. Publication only makes a reviewed design revision available. Existing course or learning-path eligibility, evidence, approval, entitlement, and plan rules still decide whether a credential may be issued.
They remain bound to the exact immutable revision and final artifact used when they were issued. Publishing, editing, archiving, or replacing a template does not rewrite an existing certificate.
An eligible issued imported-template credential appears in the learner certificate area with its authenticated PDF download and verification details. Existing certificate formats retain their established access behavior. The certificate ID and platform verification QR resolve to backend-owned credential data.
A company admin needs certificates:manage in the correct company context. Selecting real learner data for private preview also requires an employee-read permission; learners cannot edit templates or choose certificate identity or verification values.