Every certificate template is either a site template or belongs to one issuing organization. Site templates work for everyone who can award certificates and carry no issuer. Issuer templates are managed and awarded by that organization’s members, and every certificate from them records the organization as its issuer. This article covers how to assign a template and what changes when you do.
The Organization Tab
Open a template in the designer and switch to the Organization tab. The Issuing organization picker lists the issuers you are allowed to assign to, with Site template as the default. Pick an issuer and save. The same tab holds the template’s program page settings, covered in Issuer Profiles and Program Pages.

Who Can Assign
Site administrators can assign any template to any active issuer. An issuer’s owners can assign templates to that issuer and move templates between issuers they own. Members with the Issuer role cannot change the assignment.
Reassigning a Template
Changing the issuing organization on a template that has already awarded certificates shows a warning worth reading: certificates that were already issued keep their original issuer, and only future awards use the new one. The change applies when you save. This is deliberate; a credential’s issuer is part of the historical record and never rewrites itself.
What Changes for an Issuer Template
- The Templates list gains an Issuer column and an issuer filter (including a Site templates option). Members see only their own issuers’ templates; administrators see everything.
- Every award path checks issuer rights: manual awarding, bulk awarding, retroactive awarding, and the template’s trigger all respect who may award for that issuer.
- Certificates from the template show “Issued by” the organization on the verification page, appear on the organization’s public profile and program pages when those are published, and use the organization’s verification branding.
- On the Certificates screen, filtering by template still gathers one organization’s certificates, since each template belongs to one issuer.
Nothing else about the template changes. Its design, trigger, display name, validity, and email settings all carry over.
