Skip to content
Athena User Guide
Esc
↑↓navigate↵open⌘Jpreview
On this page

Issue certificates

Design a certificate template, map it to award tiers, and issue credentials to your participants.

Athena can hand every qualifying participant a personalised certificate: you design a template over a background image you supply, decide which award tier each participant falls into, and issue credentials in one pass. Players download their own copy from their profile.

Everything lives on the event dashboard’s Certificates page, where you author templates, map them to award tiers, then issue and email credentials.

Create a template

Click New template. The dialog asks for two things, and reminds you to bring a finished background image, since the editor only places merge fields on top of it:

  • Name: up to 120 characters, e.g. Excellence.
  • Page size: A4 landscape (the default), A4 portrait, or Letter landscape.

Creating a template drops you straight into the editor.

Upload a background

The certificate’s entire visual design is your background image: Athena places text on top of it and draws nothing else. Bring a finished piece of artwork with the borders, logos, seals, and signature lines already on it.

Click Upload background. The requirements are strict, and the button spells them out:

Requirement Value
Format PNG or JPEG only
Maximum size 4 MB
Aspect ratio Must match the page proportions within 0.5%
Width Between 2× and 4× the page width in points

In practice that means:

Page size Export at
A4 landscape 1684–3368 px wide
A4 portrait 1191–2381 px wide
Letter landscape 1584–3168 px wide

The 4 MB ceiling isn’t arbitrary: every player downloads the background in their browser to build their certificate, so a heavy image is a slow download for every recipient.

Aspect-ratio and resolution are checked after the upload finishes, and the errors tell you exactly what was wrong, for example “Background aspect ratio 1.500 does not match A4 landscape (1.414). Export it at exactly the page proportions.”

Place your fields

Add field drops a text field onto the page; drag it to position and use the handles on its left and right edges to set the width of the box its text must fit inside. Snap to grid and automatic alignment guides help you line fields up with the page centre and with each other.

Add verification QR, beside it, places the code that lets anyone confirm the certificate; see How verification works.

Select a field to edit it:

  • Text: the content, mixing plain text with merge tokens.
  • Font: Inter, Inter Bold, Playfair Display Bold, or JetBrains Mono.
  • Size (pt): 4 to 240.
  • Colour: a #RRGGBB hex value.
  • Alignment: left, center, or right.
  • Box width (pt): the width the text must fit within.
  • Auto-fit: “Shrink the text to stay inside the box width.” Leave this on for anything containing a name.

Remove field deletes the selected field. There’s no confirmation, so be deliberate.

Merge tokens

Click a token in the palette to insert it at your cursor. Each is replaced per recipient when the certificate is generated:

Token Prints
{{name}} Recipient name
{{teamName}} Team name (team-mode events only)
{{eventName}} Event name
{{tier}} Award tier (the printed name you gave the tier)
{{rank}} Final rank
{{totalPlayers}} Total participants
{{points}} Points scored
{{solves}} Challenges solved
{{issuedAt}} Issue date, e.g. 5 August 2026
{{code}} Credential ID

On a solo event the team token is hidden and the palette notes “Team fields are unavailable. This event runs solo.”

Check the preview

The Preview card renders a real certificate using the same renderer players get, so what you see is what they download. Its Winner, Median, and Worst case tabs are drawn from your actual roster, letting you check how the longest real name behaves before anyone receives one. Before anyone has joined the event, the tabs use stand-in names instead, so a template that looks fine pre-registration is still worth re-checking once players have signed up.

The validation banner reads “Layout is valid against the live roster.” when you’re clear. Blocking problems include a missing background, no fields, an unknown token, a team token on a solo event, and any field positioned off the page. You’ll also see non-blocking warnings when a name has to shrink a long way to fit, or overflows its box. Those are worth fixing even though they won’t stop you publishing.

Publish the template

Save stores your work in progress; Publish turns the current draft into an immutable version and is disabled while any blocking error remains. Only published templates can be assigned to a tier, and publishing is what players’ downloads are generated from; later edits to the draft don’t affect certificates already issued until you publish again.

Published versions

The Published versions card under the preview lists every version of the template, newest first, each under the content hash it was published as. The badges tell you which one tiers currently issue from (Current) and whether the draft on screen is byte-identical to a published version (Matches this draft).

Two actions sit on each row. The eye opens a preview of that exact layout: the one credentials stamped with it render from. The arrow loads it back into the editor, replacing what is on screen; nothing is stored until you press Save, so leaving the page keeps your draft as it is.

Deleting a template

The ✕ on a template in the Templates list removes it along with every draft and published version of it. While any credential issued from that template is still active the delete is refused and the button is disabled, because the published layout is what those credentials render from; the Active credentials column tells you how many stand in the way. Revoking them frees the template for deletion.

Assign award tiers

The Tiers card is your list of awards, evaluated top to bottom: “Evaluated top to bottom. Each recipient gets the first tier they qualify for, and exactly one certificate.”

A new event starts with three suggested tiers, which you can rename, re-order, delete, or add to:

Tier Qualifies on Default
Winner Rank at or above the value you set 3
Finalist Within the Top percentile you set 10%
Participant At least this many solves (Minimum solves) 1

Each tier carries:

  • Printed name: what {{tier}} prints, up to 40 characters. The short key underneath it is fixed when the tier is created and identifies the tier in exports and the API.
  • Template: one of your published templates, or Not assigned.
  • Qualifies on: Rank at or above, Top percentile, or Minimum solves.
  • The threshold for that rule, an Enabled switch, and arrows to move the tier up or down the order.

Add tier asks only for a printed name: Honourable mention, Finalist (Junior), whatever your event awards. The tier is appended to the bottom, disabled. Tiers start disabled, so nothing is issued until you turn on the ones you want, point each at a template, and click Save changes.

A participant is awarded the first tier they qualify for. Anyone who qualifies for no enabled tier, or whose tier has no template assigned, simply receives nothing.

Order matters more than the rules do: a Minimum solves tier sitting above a Rank at or above tier will catch your winners first. Read the list from the top as “the best award we can give this person”.

Renaming a tier changes what future certificates print. Certificates already issued keep the name they were issued with, and deleting a tier leaves them untouched.

Issue the credentials

Issue certificates walks your whole leaderboard in one pass and creates a credential for every qualifying participant. Certificates are issued per person, not per team: each member of a qualifying team gets their own certificate, with their own name and their own credential ID.

The result is reported as a count of issued, reissued, and skipped. “Skipped” bundles three groups: people who already hold a certificate, people who qualified for no enabled tier, and people whose tier has no template assigned. That last group is why a surprisingly large skip count usually means a tier is enabled but unmapped.

Ranks and scores are snapshotted at issue time and never recomputed, so the certificate preserves the standings as they were when you pressed the button.

Each certificate prints, and is signed with, the event name on your Athena account. Issuing finishes only once every new certificate is signed. If signing can’t complete, you’re told how many certificates are still unsigned; press Issue certificates again to sign them without minting new credential IDs. athena certificate issue does the same from the command line.

Regenerate all re-issues everyone from the current standings. It revokes every existing certificate and mints new credential IDs, so anything already downloaded or shared stops matching your records. Use it to correct a mistaken early issue, not as a routine refresh; note that it runs immediately, without a confirmation step.

Email the recipients

Two buttons distribute the certificates:

  • Email new recipients: emails only people who haven’t been emailed yet.
  • Resend all: emails everyone again.

The message is subject-lined “Your … certificate is ready”, naming your event, and links the recipient to their profile with a Download your certificate button. It also prints their credential ID, with the note “Keep this credential ID. It identifies your certificate.”

Revoked certificates are never emailed.

Revoking a certificate

The Issued certificates table lists every credential with its recipient, tier, rank, credential ID, and whether it’s been emailed. The ✕ on a row revokes that certificate: it disappears from the player’s profile immediately and can no longer be downloaded or re-rendered.

Revoking is immediate, has no confirmation step, and cannot be undone: the only route back is re-issuing, which produces a different credential ID.

What players receive

After the freeze, a Certificate card appears on each recipient’s profile page carrying their tier badge, a summary line, and their credential ID. Three buttons offer their award in three formats: Download PDF, Download image (a PNG), and Open Badge. Files are named after the credential ID, e.g. athena-ATH-2026-4K7Q-M2XZ.pdf.

The player side is covered in After the freeze.

How verification works

Certificates can be checked by anyone, with no Athena account and no help from you. It works because the certificate carries its own proof rather than pointing back at your event.

Add a verification QR to your template with the Add verification QR button, beside Add field in the editor. Athena signs each recipient’s details (name, event, award, placing, issue date and credential ID) into the code that QR contains. Anyone can paste that code at cert.athena-ctf.com/verify and see exactly those details, confirmed against Athena’s public signing key. A template takes one QR, so the button greys out once you’ve added it.

The details are signed into the code itself, which is what makes it permanent: it keeps verifying long after your event and its data are gone, which is usually when a university or employer gets round to asking.

Two things to get right when you place one:

  • Box size (pt) stops at 99 pt, which the editor labels as 35 mm printed. That is the floor for the squares staying large enough to scan.
  • Keep the backing colour light and the code colour dark. Athena always paints the backing rectangle behind the QR, so it is what the scanner sees rather than your background artwork, but nothing stops you picking two colours too close together, or the wrong way round, and the editor warns you when you do.

The Open Badge button gives the recipient the same award as an Open Badges 3.0 credential, a file for universities and badge wallets that accept them. The recipient’s email is hashed rather than written in the clear. It is signed by the same Athena key as the QR, but it is a separate credential file: an Open Badges verifier checks it, not cert.athena-ctf.com/verify.

Was this page helpful?