> ## Documentation Index > Fetch the complete documentation index at: https://docs.orriven.com/llms.txt > Use this file to discover all available pages before exploring further. # Certificates > Certificates of attendance: who is eligible, how session credits are set on the agenda, and where the attendee prints one. A certificate of attendance shows that a person arrived — and, when the agenda carries credits, which sessions they attended and how many credits that earned. It is rendered from check-in records: nothing is issued, stored, or designed. The attendee prints it from their [entry pass](/en/events/hosted-pages). Certificates need the **Onsite** module. Enable it from **Onsite** in the event navigation — see [Check-in](/en/onsite/check-in). ## Set credits on the agenda Credits are a property of each session. Open **Program & venue → Agenda**, open a session, and fill in **Credits** — a decimal such as `1` or `1.5`. Leave it empty for a session that earns none. See [Agenda](/en/program/agenda). A certificate lists every session the person checked in to, whether or not it carries credits. The credits column shows "—" for a session without any. ## Who is eligible A certificate is available when four things are true at once: 1. the event is **published**; 2. the event has **Onsite** enabled; 3. the person's registration is **confirmed**; 4. the person was checked in at the **Event arrival** door. When any of them is missing, the **Certificate of attendance** link does not appear on the entry pass, and the certificate address says "Not available yet — your certificate appears here once you have checked in at the event." Session check-ins alone do not qualify. The certificate proves attendance at the event. Front-desk arrival is that proof. ## What the certificate shows * the heading **Certificate of attendance** and the event name; * the attendee's name — or their email when the registration has no name; * the time of their arrival check-in, in the event's time zone; * a table of the **sessions they checked in to**, in agenda order, with each session's start time and credits; * **Total credits**, shown only when the total is above zero. The page is printable: **Print / Save as PDF** opens the browser's print dialog. The layout is fixed — there is no certificate designer. ## Where the attendee gets it On the entry pass, an eligible person sees a **Certificate of attendance** link beside their QR code. The entry pass is the page the platform's ticket email links to, protected by the [email check](/en/events/hosted-pages#the-email-check). To point people at it after the event, use the **Entry pass link** variable in an [email template](/en/marketing/email-templates). There is no separate certificate email and no bulk printing from the console. ## Rules to know * **Eligibility is four facts, not a switch**: published event, Onsite enabled, registration confirmed, event-door check-in. There is no per-person "issue certificate" action. * **Only session-door check-ins earn credits.** Arriving at the event without attending any session still produces a certificate — with no credit total. * **Credits are live, not a snapshot.** Editing a session's credits changes every certificate rendered afterwards, including for people who already printed one. * **Check-ins are live too.** Undoing a session check-in removes that line. Undoing the arrival check-in removes the certificate. A deleted session no longer appears. * **One credit per session per person**, matching the one-entry-per-door rule of check-in. There is no attendance-duration threshold. * **No issuance registry or verification link.** A certificate is a rendering of attendance, not a record of its own. ## Related The arrival and session check-ins a certificate reads. Sessions, and the credits field on each. The entry pass the certificate is linked from. Attendance per session.