Store event-specific details as Attributes
Define the details that change per recipient — team, track, college, role, session — and insert them into the design, forms, and emails.
A certificate usually needs more than a name. A hackathon certificate may need the track and team; a university certificate may need the programme and graduation year; a conference certificate may need the session and role.
Keeping those details in separate spreadsheet columns works until the certificate has to display them. Then someone starts duplicating designs or editing PDFs.
Certificate Attributes are the structured version of those columns.
How they work
Define an Attribute on the certificate, give it a label and a type, and use it in the design. When recipients are imported or added, each person gets a value for that Attribute. The design stays the same; the values change per recipient.
Open a certificate and go to Configure to manage its Attributes. Use the design editor to insert an Attribute into the layout, and map spreadsheet columns to the same Attribute during import.
Concrete uses
A hackathon can keep one participation design and vary the track, team name, and award. A university department can show the programme and year without creating a design per cohort. A volunteer programme can show the role and activity. A conference can show whether the person attended as an attendee, speaker, or volunteer.
The limit
An Attribute is only useful if the value is available. If a column is missing from the spreadsheet, the certificate cannot invent it. Use the Issue Request Form to collect missing details, or add the recipient individually.
Importing and defining Attributes do not spend credits.
Related