> ## Documentation Index
> Fetch the complete documentation index at: https://docs.huntlytic.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Managing Events
> Create, manage, and track attendance for meetings, workdays, and other organization events.
The **Events** page is your hub for scheduling organization events, tracking who attended, and running kiosk-based check-in. Navigate to **Events** in the sidebar to get started.
## Event Types
Events are organized by type — for example, **Meetings**, **Workdays**, or **Orientation**. Each type appears as a tab across the top of the Events page. The active tab determines which events are shown and which type is assigned when you create a new event.
If you don't see any tabs yet, your organization hasn't configured any event types. Click **Configure Types** to add them first.
### Configuring Event Types
Click the **Configure Types** button (gear icon, top-right) to manage your organization's event types.
| Field | Description |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | The label shown on the tab and in event forms (e.g., "Meeting", "Workday"). |
| **Quota / yr** | Optional. The number of times per year a member is expected to attend this event type. Leave blank for no quota. |
| **Required** | Only available when a quota is set. When enabled, members who don't meet the quota will be flagged in the compliance report and may incur a non-compliance fee at renewal. |
| **Attendance** | Allows property managers to record attendance for events of this type held at their properties, without needing admin access. Events of a type with this turned off never appear in a property manager's list. See [Recording Attendance as a Property Manager](/events/pm-attendance). |
| **Registration** | Allows members to register for upcoming events of this type. Turning this on is the prerequisite for the registration count chip on events of this type and for the attendance quick-pick described below. |
To add a new type, enter a name in the **New type name** field at the bottom and click **Add**. Changes to existing types are tracked per-row — a **Save Changes** button appears when you have unsaved edits.
Deleting an event type is permanent and cannot be undone. Events of that type are not automatically deleted, but the type will no longer appear as a tab.
***
## Creating an Event
1. Select the tab for the event type you want to create (e.g., click the **Meeting** tab).
2. Click **New \[Type]** in the top-right corner.
3. Fill in the event details:
| Field | Description |
| --------------- | --------------------------------------------------------------------------------- |
| **Title** | A short, descriptive name for the event (required). |
| **Start** | Date and time the event begins (required). |
| **End** | Date and time the event ends. Optional — leave blank for open-ended events. |
| **Location** | A property from your organization's property list, or a named location (address). |
| **Description** | Optional rich-text notes, agenda, or directions visible to members. |
4. Click **Save**.
The event appears in the list under its type tab, alongside events that have not yet passed, soonest first. An event that has started but hasn't ended yet still counts as upcoming. Use the **Show past events** toggle above the list to reveal past events alongside upcoming ones.
***
## Editing an Event
Click the **pencil icon** in the event's row to open the edit form. All fields can be updated. Click **Save** to apply changes.
***
## Cloning an Event
Click the **copy icon** in the event's row to open a pre-filled "Clone Event" form. All details from the original event are carried over — update the title, date, and any other fields as needed, then click **Save** to create the new event. The original event is not affected.
This is useful for recurring events like monthly meetings where the format stays consistent.
***
## Deleting an Event
Click the **trash icon** in the event's row. You will be asked to confirm before the event is permanently deleted. Deleting an event also removes its attendance records.
***
## Managing Attendance
Each event row shows an attendee count chip. Click it to open the Attendance dialog.
### Viewing Attendees
The dialog lists everyone currently marked as attending, along with their email address. To remove an attendee, click the trash icon next to their name.
### Adding Members Manually
If the event type has **Registration** enabled and members have registered, the dialog opens with a **Registered (N not yet marked)** section above the search field. Check the box next to each person who showed up, or click **Select all** and uncheck the no-shows, then click **Add**. Anyone you mark attending drops off this list automatically, so it always reflects who's still outstanding.
For walk-ins or members who never registered, use the **Add Members** search field to find members by name, email, or member ID. Check the box next to one or more members, then click **Add** to record their attendance. This is useful for retroactively logging attendance or handling members who didn't check in via kiosk.
For self-service check-in at in-person events, use the kiosk feature instead. See [Kiosk Setup](/events/kiosk-setup) for instructions.
***
## Registrations
When an event's type has **Registration** enabled, each event row shows a second chip alongside the attendee count — a person-with-check icon carrying the current registration count. Click it to open that event's **Registrations** dialog, whose title bar shows the event name.
From there you can view everyone currently registered, add registrants the same way you add attendees manually (search by name, email, or member ID, then click **Register**), and remove a registrant with the trash icon next to their name.
Members register for events themselves from the **Calendar** page or the **Upcoming Events** dashboard widget, using a button that reads **Register** and flips to **Registered** once they've signed up.
Registering is an expression of intent, not a record of attendance — a member can register and still not show up, or attend without ever registering. The attendance quick-pick described above is the bridge between the two: it turns each registration into a one-click attendance mark once the event has happened.
***
## Kiosk Check-In
Each event can have a unique PIN that members use to check themselves in via the kiosk page on a shared tablet or computer.
Click the **tablet icon** in the event's row to open the Kiosk PIN dialog.
* If no PIN exists, click **Generate PIN** to create one.
* If a PIN already exists, it is displayed and can be copied with the copy button.
* Click **Regenerate** to replace the current PIN with a new one (the old PIN stops working immediately).
* Click **Clear PIN** to disable kiosk check-in for the event.
The dialog also shows your organization's **Kiosk URL** — this is the address members navigate to on the check-in device.
When a PIN is active, the tablet icon in the events list turns blue and hovering over it shows the current PIN for quick reference.
For full setup instructions, see [Kiosk Setup](/events/kiosk-setup).
***
## Compliance Report
Click the **Compliance** button (top-right) to view a member-by-member compliance summary for required event types.
The report shows a grid of every active member against every event type that has a quota and is marked **Required**. Each cell shows the member's attended count vs. the required count for the selected year:
* **Green** — the member has met or exceeded the quota.
* **Red** — the member has not yet met the quota.
Use the year selector in the dialog title bar to view past or future years.
If the compliance report is empty, make sure at least one event type has a **Quota / yr** set and the **Required** toggle enabled. Types without both settings are not included in the report.