|Click the _Admin_ link in the UI|
|Close out the ticket|
|Commit all files and push to https://pagure.io/fedora-badges[fedora-badges] (or make a PR)|
|Congratulations, you just pushed your very own Fedora Badge!|
|Create an invitation|
*Creation Date*: Optional.
It defaults to the current date.
*Criteria*: link to the issue in https://pagure.io/fedora-badges[fedora-badges]
*Description*: badge description text (ensure there is _no_ hanging whitespace)
|Double-check all entered information is *correct and accurate*|
|Double-check the artwork is actually the final version from ticket|
|Download artwork and rule file (if applicable):|
|Ensure artwork is *approved* by Design Team|
|Ensure name and description of badge are clear|
|Ensure one of these requirements is met:|
|Enter FAS password and https://docs.pagure.org/infra-docs/sysadmin-guide/sops/2-factor.html[2FA token]|
|Enter in all information as provided in the badge ticket (see xref:badge-metadata[Badge metadata] below.)|
*Expiration Date*: Optional, but you probably want to specify one.
It defaults to 2 hours from the current time.
For instance, at the Flock 2013 conference, we set the expiration date at the end of the conference.
Anyone who tried to claim the badge with the QR code after that time would be denied, with the message _this invitation is expired_.