Rego Config

Overview

Rego Config is the product and access model for attendee registration. It defines when registration opens, what attendees can choose, how much each choice costs, what capacity limits apply, what inclusions are attached, and whether attendees can later upgrade, transfer, or register as a group.

This page should be handled like a store setup page and an access-control page at the same time. A tier is not only a price. It can also grant event access, inclusions, Discord roles, Telegram tags, ZEP access, pickup items, and eligibility for later upgrades or transfers.

Dashboard route

• /ems/manage/rego-config?id=:eventId

Global rego settings

Input or option	What it does	Notes for operators
Rego opens / closes	Sets the default public registration window.	Leave open blank for immediate availability. Leave close blank only when staff intentionally want registration to remain open until the event ends.
Prefills open / close	Lets attendees save choices before real registration opens.	Prefills are useful for launch readiness, but attendees cannot pick payment methods or pay during prefill-only periods.
Max capacity	Caps the whole event.	Use this when venue or staffing capacity is the true limit. Tier-level limits can still be lower.
Minimum age	Blocks attendees below the required age by event start date.	Confirm the policy and date basis before saving.
Reference prefix	Prefix for new rego reference numbers.	Must be unique across events and should be short enough for staff to read during check-in.
Require fursona info	Makes fursona fields required.	Useful when badge or community identity workflows depend on this information.
Ask if attendee will be fursuiting	Adds fursuiting intent to registration.	Use when headless lounge, handlers, storage, or venue planning depends on fursuit counts.
Add-ons enabled	Controls whether add-ons are available for attendee selection.	Keep disabled until add-on names, prices, inventory, and windows are ready.

Page sections and editor actions

Section or action	What it controls	Before saving
Rego settings card	Event-wide registration windows, prefills, capacity, age, upgrades, transfers, gifting, reference prefix, and attendee profile requirements.	Review this first because tier and add-on overrides inherit from it.
Rego tiers card	Main registration products and access levels.	Every event with registration should have at least one usable tier before opening.
Add-ons card	Optional attendee selections.	Keep the Enabled switch off until add-on inventory, prices, and windows are ready.
Inclusions card	Items bundled into tiers and later reusable as shop source items.	Confirm fulfillment and claim behavior before attaching inclusions to tiers. Configure separate shop pricing and availability in Shop Config.
Bot assignment card	Discord and Telegram integration targets for entitlements.	Select the correct server or chat before assigning roles or tags to products.
ZEP access card	Protected online-space access rules.	Configure only after the ZEP app and space identifiers are known.
Group rego card	Multi-person registration behavior.	Keep group size within what support and payment review can handle.
Floating save bar	Saves or reverts all changed config areas.	Revert if a product, entitlement, or window was changed in the wrong event.

Upgrade and transfer options

Input or option	What it does	Operational impact
Attendee rego upgrades	Lets attendees move to a higher tier or add more add-ons to an existing rego. Existing add-ons stay locked and cannot be removed.	Enable only when staff can support capacity, payment, and entitlement changes.
Upgrades open / close	Optional window for upgrade requests. Blank open uses the toggle immediately; blank close keeps upgrades available until event end.	Use when upgrades should close before production lock, badge printing, or inventory packing.
Manual review then payment	Staff must accept an upgrade request before the attendee can pay/finalize.	Safer when stock, capacity, or payment proof needs review.
Direct pay and finalize	Attendee can submit, pay, and finalize without staff approval first.	Faster but should only be used when rules are simple and stock/capacity are reliable.
Payment window	Hours an accepted upgrade request stays payable. Defaults to 24 and is limited to 1-168 hours.	Keep short enough to prevent capacity from being held too long.
Attendee rego transfers	Lets attendees request moving a rego to another attendee account.	Keep off unless staff can review identity and ownership risks.
Transfers open / close	Optional window for transfer requests. Blank open allows requests once enabled; blank close keeps transfers available until event end.	Close before check-in if identity or badge production needs final records.
Manual review by staff	Staff must approve the transfer.	Safest for identity-sensitive events.
Direct confirm and transfer immediately	Transfer is applied immediately after submission.	Use only when the event accepts immediate ownership movement risk.

Gifting options

Input or option	What it does	Operational impact
Attendee rego gifting	Enables the public Gift a rego flow under Start Rego. Disabled by default.	Turn on only when staff are ready to review gift payments and support receiver redemption.
Gift capacity handling	Chooses whether paid, unredeemed gifts reserve event and tier capacity immediately or only when redeemed.	Default behavior reserves one event slot and one tier slot for each active gift. Change to redeem-only only when oversubscription is intentional.

Gift receivers redeem through the normal attendee rego flow. Their rego details, profile fields, forms, sizes, and event-specific custom inputs must come from the receiver, not the gifter. Gift checkout uses the same paged tier, add-on, payment, proof, and review pattern as regular rego and applies the same platform fee and configured payment-fee rules. Gift redemption is blocked until payment is confirmed according to the event’s rego confirmation behavior: manual review requires staff confirmation, good-faith confirmation can make the gift redeemable immediately after required payment details are submitted, and hybrid follows the supported payment method path. Before redemption, gifts are non-refundable and non-transferable. After redemption, the resulting rego follows the event-wide refund, transfer, and upgrade policy.

Gift discounts are controlled per coupon and per affiliate record. Enabling rego gifting does not automatically make existing coupons or affiliate codes valid for gifts. Open Attendee Coupons and Affiliates Tracking and enable gift applicability only for the specific programs that should discount or attribute the gifter’s purchase.

Before turning on gifting, verify:

Check	Why it matters
Payment review staffing	Manual-confirmation events must confirm gift payments before receivers can redeem.
Capacity mode	Default gift capacity handling reserves one event slot and one tier slot for each paid unredeemed gift.
Receiver forms	The receiver must still answer all required event forms and custom inputs during redemption.
Notifications	Receiver email and inbox copy must respect the gifter’s anonymity setting and optional markdown-ext message.
Discount eligibility	Coupons and affiliates need explicit gift applicability before they affect gift checkout.

Tiers

Tiers are the main registration choices. A tier usually represents an access level such as regular attendee, sponsor, staff equivalent, or special package. Each tier can have a name, image, description, price, capacity, included items, entitlement rules, and date overrides.

Per-tier overrides are important when a tier launches earlier, closes earlier, has a different prefill schedule, or grants different online access. If the event uses ZEP, Discord, or Telegram integrations, confirm the tier entitlements before the event goes active.

Tier field	What it changes	Notes
Tier image	Visual shown with the tier where used.	Upload only public-safe JPG, PNG, or WebP images.
Name	Required tier label.	Use attendee-facing wording.
Description	Markdown-ext tier explanation.	Explain what the attendee receives and any limits.
Price	Required tier price in PHP. Use 0 for free.	Payment-enabled state changes how prices are presented to attendees.
Capacity	Optional per-tier cap. Blank means unlimited at the tier level.	Still constrained by event max capacity if set.
Included in this tier	Selects inclusions bundled with the tier.	Confirm claim, inventory, and fulfillment impact.
Discord entitlements	Assigns Discord roles when the tier becomes active.	Requires a selected Discord server in Bot assignment.
Telegram entitlements	Applies a Telegram member tag when the tier becomes active.	Requires a selected Telegram chat in Bot assignment; tag length is capped at 16 characters.
ZEP access override	Changes how the tier handles event default ZEP spaces.	See ZEP access modes below.
Rego window override	Optional tier-specific opens/closes dates.	Use for early bird, sponsor, or staff-only timing.
Prefill window override	Optional tier-specific prefill dates.	Use when one tier should preview before another.

Tier editor actions and states

Action or state	What it does	Operator impact
Add tier	Creates a new tier draft.	Configure name, price, capacity, access, and included items before opening registration.
Upload tier image	Adds public-facing tier artwork through the crop/upload flow.	Use only images the event can publish.
Active/available controls	Decide whether the tier can be selected.	Inactive tiers can remain for planning without accepting new attendees.
Move controls or custom ordering	Changes how tiers appear to attendees.	Put common or recommended choices where attendees can find them easily.
Remove tier	Deletes the tier draft.	Avoid removing a tier after registrations exist unless staff have confirmed the data outcome.

Add-ons and inclusions

Add-ons are optional purchases or selections attached to a registration. Inclusions are items bundled into tiers or made available for fulfillment. Both support item types such as general item, wearable, print/poster, plushie/figurine, digital download, event access, and voucher/meal.

Wearable items can carry size lists and size-guide behavior. Physical or print items can carry dimensions. Digital items can carry delivery notes. Add-ons and inclusions can be made available as shop listings from Shop Config, where shop price, category, fulfillment, selling limits, and purchase windows are managed.

Use the image field when staff or attendees need a visual check. Use descriptions for attendee-facing clarity, not staff shorthand.

Item type	Additional fields or behavior
General	Basic name, image, description, price/window behavior.
Wearable (Shirt / Hoodie)	Available sizes, optional size guide, custom size guide URL, and editable size guide table.
Print / Poster	Optional dimensions with width, height, and units.
Plushie / Figurine	Optional dimensions with width, height, and units.
Digital Download	Delivery notes for how the attendee receives the item.
Event Access	Used when the item represents access rather than merch.
Voucher / Meal	Used for claimable voucher or meal entitlement.

Add-on field	What it changes	Notes
Available to attendees	Controls whether the add-on can be selected.	Keep unavailable for drafts or sold-out items.
Add-on price	Required price in PHP. Use 0 for free.	Check fee calculator behavior if payments are enabled.
Discord/Telegram entitlements	Assign roles or member tags when the add-on is attached to an active rego.	Use for access that is optional or add-on-specific.
Rego window override	Optional add-on-specific opens/closes dates.	Use for limited campaigns or production cutoffs.

Add-on and inclusion editor actions

Action or field	What it does	Before saving
Add add-on	Creates an optional attendee selection.	Confirm price, availability, inventory impact, and whether it grants access or only merchandise.
Add inclusion	Creates a bundled item that can be attached to tiers and optionally reused as a shop source item.	Confirm whether it should be claimable or fulfilled with the registration. Configure standalone shop sale rules in Shop Config.
Image upload	Adds a product image.	Use when visual identification helps attendees or fulfillment staff.
Description	Explains the product in markdown-ext.	Write public copy for attendee-facing products.
Available sizes	Defines size options for wearable items.	Keep size labels consistent with fulfillment stock.
Size guide	Adds sizing help for wearables.	Use a custom URL or table only if it is accurate for the product.
Dimensions	Stores width, height, and units for physical items that need dimensions.	Use for prints, posters, plushies, figures, or production-sensitive items.
Delivery notes	Explains how digital downloads are delivered.	Use for digital items only.

Inclusion field	What it changes	Notes
Inclusions sort	Sorts by most tiers first, fewest tiers first, alphabetical, or custom order.	The displayed order becomes the tier inclusion table order after saving.
Shop listing source	Inclusions can be selected from Shop Config when they should be sold outside registration.	Shop Config owns category, price, image reuse, fulfillment, quantity caps, and shop availability.

Upgrades, transfers, and groups

Attendee upgrades let a person move to a higher tier or add more add-ons after the original registration. Manual review is safer when stock, capacity, or payment proof needs staff approval. Direct pay is faster when the rules are simple and inventory is reliable.

Transfers let a registration move to another attendee account. Keep this disabled unless staff are ready to review identity, payment, and misuse risks. Direct confirmation is only suitable when the event accepts the operational risk of immediate transfer.

Group rego lets one organizer create a shared registration flow for multiple attendees while still producing independent attendee records afterward. The max group size should reflect what staff can support at payment, check-in, and exception handling.

Group rego max size accepts 2-10 people, including the organizer. The default is 3. Set the value based on how many people staff can support in one shared payment and support conversation.

The group discount can be disabled, a percentage, or a fixed PHP amount. Set the minimum eligible group size and, if needed, a maximum discount cap. The dashboard preview uses a PHP 1,000 example; the API recalculates the authoritative discount for the actual accepted group and stores each attendee’s allocated discount in that rego’s totals snapshot. Submitted groups therefore keep their historical total even if settings change later.

Tier, add-on, and inclusion custom questions use the visual question builder. Public registration scopes each question to the selected item, and tier inclusions appear in the canonical inclusion order saved here rather than in the tier’s internal ID order.

Bot assignment and access entitlements

Bot assignment connects the event to Discord servers and Telegram chats where the organizer has admin access. Tiers and add-ons can then assign Discord roles or Telegram member tags. This is powerful because registration changes can affect community access outside the dashboard.

Before enabling entitlements, confirm the bot is installed, the selected server or chat is correct, and roles or tags match the event policy.

ZEP access

ZEP access defines online event-space access tied to confirmed or onsite regos. The page can download the FPH ZEP app zip, add ZEP instances, set default event access, and let tiers or add-ons override that default.

ZEP control	What it changes	Notes
Download app zip	Downloads the FPH ZEP app bundle.	Upload this in ZEP as a Normal App on protected maps.
Add ZEP instance	Adds a ZEP space tied to the event.	Use one entry per protected space or map access target.
Event default access	The baseline ZEP spaces every confirmed or onsite rego receives.	Tier and add-on overrides can inherit, replace, add, or remove this access.
Access starts / ends	Optional access windows for tier or add-on effective ZEP spaces.	Leave blank to rely on the ZEP instance visibility window.

ZEP access mode	Meaning
Inherit event defaults / current access	Use the event-level ZEP access baseline.
Replace	Replace the baseline with the tier or add-on’s selected ZEP spaces.
Add	Add selected ZEP spaces on top of the baseline.
None / Remove all ZEP access	Remove ZEP access for that tier or add-on.

Review before saving

1. Confirm global rego windows and event capacity.
2. Confirm every tier has the correct price, capacity, inclusions, and access entitlements.
3. Confirm add-ons and inclusions have clear names, images, registration availability windows, and item types.
4. Confirm upgrades, transfers, and group rego are enabled only if staff can support them.
5. Save, then test the attendee registration path from the public event page.

Flowchart context

The Create an Event flowchart points to Rego Config for the registration product setup sequence: global registration windows, ZEP access, inclusions, tiers, add-ons, upgrades, transfers, and group registration. Active Event Workflow points back here when public registration behavior or attendee-facing product setup needs verification.

Related pages: Create an Event, Active Event Workflow, Regos, Rego Analytics, Inventory Tracking.

Common mistakes

Do not treat a tier as only a price. Tiers can affect capacity, access, inclusions, Discord roles, Telegram tags, ZEP access, and later upgrade paths. Do not open registration until at least one usable tier, payment behavior, public dates, and attendee-facing copy have been tested together.