> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/events-engine-overview/setup-public-event.md).

# How to Set Up an Event for Members and Public Registration

A "public-facing" event allows guests or non-members to register in the portal and gain access to public events. Events can have different ticket tiers for non-members versus members — member tickets can be discounted or have a different inventory than what is available to the public.

### Before you begin (Prerequisites)

* **Enable Public Registration must be turned ON** on your portal so non-members can create an account at checkout. This is a Peoplevine-managed setting — contact your Account Manager or Support to enable. See: [Admin Settings Managed by Peoplevine](/products/portal-overview/portal-admin-settings.md).
* **Payment processor**: Active processor required for ticketed events. See: [Stripe — Operator Manual](/products/integrations-overview/setup-stripe.md) or [GoCardless — Operator Manual](/products/integrations-overview/setup-gocardless.md).

### How non-member registration works

When **Enable Public Registration** is ON, the portal shows a **stripped-down view** to non-members:

* Non-members entering the portal see **only the home page and the events page** (member-only content stays hidden as long as you've configured visibility correctly on each piece of content).
* When a non-member clicks **Register** for a ticketed event, they're prompted to create an account using their email. The system creates a CRM record so the ticket can be attached to a person.
* Non-members can only see and register for events whose **Visibility** is set to **Public**.

### Instructions

#### 1. Confirm portal-level settings

Have your Account Manager confirm that **Enable Public Registration** is **ON** for your portal. Without it, non-members hit the login wall with no path to register.

If you also want to keep members-only content (blogs, directory cards, member-only events) hidden from non-members, confirm those individual pieces of content have **Visibility = Active Members** set on each one.

#### 2. Create the event

Follow the standard flow in [How to Set Up an Event](/products/control-panel-overview/events-engine-overview/create-event.md). When you reach Visibility and Permissions:

* **Visibility (Calendar Settings)**: **Public** — the event appears on the public events calendar and is visible to non-members who have created an account on the portal.
* **Who Can Register?**: **Anyone (Public)** — allows non-members to register.

#### 3. Configure ticket tiers

If you want different pricing or inventory for members vs the public, create **two ticket types**:

| Ticket type               | Price                                            | Visibility                                  | Inventory             |
| ------------------------- | ------------------------------------------------ | ------------------------------------------- | --------------------- |
| **Member**                | Member-tier price (may or may not be discounted) | Restrict to your active membership programs | Linked to main pool   |
| **Public** / *Non-Member* | Public rate                                      | *Anyone*                                    | Main pool (or linked) |

Always link the second ticket back to the main ticket so both tiers draw from the same total capacity. See: [How to Set Up & Manage Event Tickets](/products/control-panel-overview/events-engine-overview/setup-manage-tickets.md).

#### 4. Test before publishing

Before flipping the event to Approved:

* Log in with an Active member test account → confirm the *Member* tier shows at the discounted price.
* Log in with a non-member test account → confirm only the *Public* tier shows and the registration prompt asks the user to create an account at checkout.
* Confirm the event is visible on the public events page.

#### 5. Share the event link

For non-member promotion:

* Direct non-members to enter their email into the portal login field and click **CONTINUE**. The system prompts them to create an account.
* They're then routed to the events page where they can register.

If you don't want non-members to land on a login page first, link directly to the event detail URL — registration prompts at checkout.

### Best Practice

* **Combine Enable Public Registration with audience-restricted content.** Without per-content visibility settings, opening the portal to non-members can expose member-only blog posts, directory cards, or other events.
* **Use the on-sale date to phase access.** If you want members to buy first and the public to get the remainder, set the *Public* ticket's **Date On Sale** later than the *Member* ticket's.

### What Happens Next

* **On the member side**: Active members see the *Member* tier at the discounted price. Non-members can register through the same event link, are prompted to create an account, and pay the *Public* tier price.
* **On the admin side**: Both registrations appear in **ATTENDEE LIST** with their ticket type.
* **Next step**: [How to Manage Event Registrations](/products/control-panel-overview/events-engine-overview/manage-registrations.md) · [How to Set Up & Manage Event Tickets](/products/control-panel-overview/events-engine-overview/setup-manage-tickets.md) · [How Members Sign Up for Events](/products/control-panel-overview/events-engine-overview/members-sign-up-for-events.md).

*Last updated: 2026-05-24*


---

# 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://help.peoplevine.com/products/control-panel-overview/events-engine-overview/setup-public-event.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.