Settings

This page lists your site’s general settings in Site ConfigWhere your site's settings live in the admin, gathered in one place and grouped into sections by the part of the product they affect. Most settings have a site-wide default and can be overridden for individual events; a few are managed by EventDrake and shown as read-only.. For how settings work in general, including site-wide defaults and per-event overrides, see Site configuration. Your web address and custom domains are set up separately, under Web.

Site Config

The General, Locale, Security, and Notifications settings.

General

• Organisation name: your organisation’s name, used where your identity is shown, such as in emails and legal text.
• Site name: your site’s name, shown around the site and in the browser tab.

Locale and language

The defaults for how dates, times, money, and language appear. Getting these right matters, because they decide how prices, times, and dates read to your audience. Several can be overridden per event.

• Default country: your site’s country, used as the starting point for addresses and formatting.
• Event timezone: the timezone times are shown in, so schedules and deadlines read correctly for your audience.
• Currency: the currency amounts are shown and charged in.
• Default language and Available languages: the language your site defaults to, and the languages people can choose from.
• Default locale and Available locales: how numbers and dates are formatted, such as day and month order and decimal marks.

Changing currency affects every price

The currency applies to every price across your whole site, so change it only when nothing is on sale, and with extreme caution. It does not convert existing amounts, so a price that was right in one currency becomes wrong in another. Before changing it, check that your payment processor supports the new currency for your account, as some, such as Stripe, limit which currencies you can accept. Orders already placed are not affected: they keep showing in the currency they were made in, so your records stay accurate.

Security

• CAPTCHA: requires a human-verification check on public forms to cut down spam and automated abuse. You set it separately for registration, the contact form, and surveys, and for guests versus signed-in people, so you can protect the forms most at risk without adding friction everywhere.

Turning CAPTCHA off raises your abuse risk

Disabling the check on a form makes it easier to abuse, such as spam contact-form messages and spam registrations, and can put your site at risk of fraud. Only turn it off for a form if you have another way to keep that form safe.

Notifications

• Slack notifications: send a Slack message when key things happen, so your team sees them in real time. Turn it on and set the webhook link for each kind: new registrations, merch orders, admin sign-ins, and support tickets.

Reporting

• Maximum report rows: caps how many rows a report returns, to keep exports manageable and quick.