> For the complete documentation index, see [llms.txt](https://docs.bitpers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitpers.com/feature-modules/events.md).

# Events

### TL;DR

**Events** anchor Bitpers in real‑world moments. From road trips to festivals, events provide context and access control for capturing and sharing—and they power both Memory Boards and Murals.

***

### 1) What are Events?

Events define a time‑bound context (and optional location/attendance) that routes media to the right boards and murals, with appropriate permissions.

**Why it matters:** Shared moments deserve shared context—without the chaos of chat threads and random folders.

***

### 2) Value Proposition

* **Clear boundaries:** Date/time windows auto‑organize media.
* **Right‑sized access:** From simple invites to barcode/ticket verification.
* **Better outputs:** Event murals and recap boards that just work.
* **Extensible:** Layer Collab for votes/polls and Face Hunt for people search.

***

### 3) Event Types

* **Simple (Trips/Birthdays):** Manual invites; optional RSVP.
* **Moderate (College Fest/Weddings):** Invite‑based + barcode presence verification for contributors; viewers allowed.
* **Highly Controlled (Concerts/Festivals):** Ticket integration → event key → mural access. Organizer bulk uploads; audience contributions if allowed.

***

### 4) Core Features (v1 & v1.1)

* **Creation:** Title, dates, optional location; invite list.
* **Access control:** Viewer vs contributor; presence verification (barcode) for mid‑tier events.
* **Auto‑routing:** Media during event → linked Memory Board and/or Mural.
* **Recaps:** Quick share pages and highlight reels.

**Polish (v1.1)**

* Organizer dashboards; guest analytics (views, contributions).
* Smart reminders and nudge flows.

***

### 5) Use Cases

* **Friends:** Road trip album that builds itself.
* **Families:** Wedding recap with curated selects.
* **Organizers:** Festival wall + attendee contributions.
* **Brands:** Campaign content capture and live polls via Collab.

***

### 6) Roadmap (Illustrative)

* **Q1:** Core creation, routing, and access controls.
* **Q2:** Barcode/ticket integrations; organizer tools.
* **Q3:** Featured public event hubs; discovery partnerships.

***

### 7) Metrics

* Event creations; active attendees; contribution rate.
* % events linked to murals/boards; recap shares.

***

### 8) Risks & Mitigations

* **Attendance spoofing:** Barcode/ticket verification; device checks.
* **Over‑sharing/noise:** Contribution roles and rate limits.
* **Onboarding friction:** Templates; one‑tap "Create from calendar dates."

***

### 9) Integrations

* **Murals:** Event‑specific shared walls.
* **Memory Boards:** Auto‑log moments into a story.
* **Collab:** Votes, polls, and campaign tools on top of event media.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.bitpers.com/feature-modules/events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.