Buzz Settings

Buzz Settings is the single, site-wide control panel for your Buzz install. It is a Single DocType in Desk — there is only one record, and the values you set here apply across every event unless an individual event overrides them.

Open it in Desk at:

desk:/app/buzz-settings

You need the System Manager role to view or edit Buzz Settings.

The form is split into tabs. This page walks each tab and section field by field, in the order they appear, and tells you what each setting actually changes for your attendees, sponsors, and applicants.

General tab

General

• Support Email — the address Buzz links to in attendee-facing emails and similar communications. Set this to a monitored inbox so attendees have somewhere to reach you.

Ticketing

This section controls how long before an event your attendees are allowed to self-serve changes to their tickets. Each field is a number of days before the event start date:

• Allow Transfer Ticket Before Event Start (Days) — attendees can transfer a ticket to someone else only while at least this many days remain before the event.
• Allow Add Ons Change Before Event Start (Days) — attendees can change their add-on selections only while at least this many days remain.
• Allow Ticket Cancellation Request Before Event Start (Days) — attendees can raise a cancellation request only while at least this many days remain.

All three default to 7 and cannot be negative. The transfer window additionally cannot exceed 365 days.

How the window is read. The number is a cutoff, not a head start. A value of 7 means the action stays open until the event is 7 days away, then closes. Set a field to 0 to keep the action open right up to the event start date. These values back the can_transfer_ticket, can_change_add_ons, and can_request_cancellation checks the dashboard runs on each ticket; when a window has closed, the attendee sees a restriction notice instead of the action button.

If a field is left blank, the backing checks fall back to a default of 7 days.

For the attendee-side view of these actions and the notices they trigger, see Manage Your Ticket.

Proposals tab

This tab governs the public Propose an Event flow (people applying to host an event). It does not affect talk proposals.

Event Proposals

• Accept Event Proposals — the master switch. While this is off, the public event proposal page is closed and submissions are rejected. The remaining fields in this tab only appear once it is enabled.
• Allow Guest Submission — when on, visitors can submit an event proposal without logging in. When off, anyone reaching the form is asked to log in first.
• Banner Title — the heading shown at the top of the public proposal form. If you leave it blank, the form falls back to "Propose an Event".

Success

These two fields control the confirmation screen an applicant sees after submitting:

• Success Title — the heading on the thank-you screen. Falls back to "Thank you!" if blank.
• Success Message — the body copy on the thank-you screen, written in Markdown. Use it to explain what happens next (review timeline, who will be in touch, etc.).

For the applicant-facing flow these settings drive, see Propose an Event.

Login tab

Login Banner Config

• Login Banner — a promotional message shown inside the login / signup modal that attendees and applicants see when they are asked to sign in. It supports Markdown, so you can add a short pitch, a link, or formatting. Leave it blank to show no banner.

Communications tab

This tab sets the default email templates Buzz uses. Defaults set here apply to every event but can be overridden on the individual event.

Ticketing

• Default Ticket Email Template — the Email Template used for ticket confirmation emails when an event does not specify its own. If neither the event nor this setting names a template, Buzz uses its built-in default ticket email.

Sponsorships

• Auto Send Pitch Deck — when on, Buzz automatically emails the sponsorship pitch deck in response to enquiries. Turning this on reveals the sponsor email settings below. (An event can also enable auto-send on its own.)
• Default Email Template — the Email Template for pitch-deck emails. Required while Auto Send Pitch Deck is on; can be overridden per event.
• Default Reply To — the reply-to address applied to pitch-deck emails. Required while auto-send is on.
• Default CC — addresses to CC on pitch-deck emails (free text). Optional.

The matching per-event fields take precedence; these are the fall-backs used when an event leaves them empty.

Custom Fields

The form ends with a placeholder section marked "Custom Fields Go After This." Any custom fields you add to the Buzz Settings DocType (via Customize Form) render below this point, keeping your additions separate from the built-in settings above.

Where these settings take effect

Remember: Buzz Settings is the default layer. Wherever an individual event exposes the same option (ticket email template, pitch-deck auto-send and its email fields), the event's value wins.