# Event Proof Of Presence

Create an event and automatically issue proof of presence attendance with a QR code shared with invitees. This feature tracks and rewards community participation, making it easier to identify active members. As their reputation grows over time, these dedicated individuals will earn more trust, bounties, and important responsibilities within the community.

Founders, to issue proof of presence, you will need to have already minted a [badge](/jur-society-knowledge-base/get-started-product-tutorials/founders/create-badge.md). Once completed, you are now ready to create an event.&#x20;

In addition to the selection of the badge that will be issued to attendees, the event creation form requires an:

* event description
* start date/time&#x20;
* event type (virtual or physical)
* unique event PIN&#x20;

Once, the event is created, an event link is generated. During the scheduled time of the event, that link displays a page with a QR Code, which updates every 30 seconds, and PIN access.

<figure><img src="/files/SyWkHGyPGJtq2Uz9M4kU" alt=""><figcaption></figcaption></figure>

When an attendee scans the QR code and enters the PIN, a proof of presence badge will automatically be issued on the attendee's passport.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook.jur.io/jur-society-knowledge-base/get-started-product-tutorials/founders/event-proof-of-presence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
