Event settings
How an event is configured, covering the create form, what's locked at creation, and what you can change later in Settings.
An event’s configuration starts on the Create Event form. After creation, most of it stays editable from the event’s Settings page, but a handful of choices are locked in at creation and can’t be changed. This page walks through every field, where it lives, and whether you can change it later.
Basic details
- Event Name: 3–32 characters. As you type, the slug and flag prefix auto-fill from the name until you edit them yourself.
- Start date (UTC) and Start hour (UTC): a calendar picker plus an hour select (00:00 UTC through 23:00 UTC). The entire schedule is UTC (there is no local-time conversion), and the start must be in the future (“Start time must be after the current time.”).
- Duration (in hours): how long play runs; minimum 1 hour, maximum 720 hours (30 days), default 48. The duration sets the scoreboard freeze: once date, hour, and duration are valid, a preview line shows “Freeze at … UTC · End at … UTC”. The freeze lands at start + duration, and the event ends after the wind-down below it; that closing window is when feedback, writeups, and certificates happen. See The event lifecycle.
- Wind-down (in hours): how long the event stays up after the freeze so players can read solutions and download certificates; minimum 1 hour, maximum 72 hours, default 24. It is part of the event’s runtime, so it counts towards the credit hold.
- Estimated credit hold: a panel below the size and duration fields. It shows what creating the event will reserve: the live window priced at the size’s hold rate prorated over your duration, the wind-down after the freeze at the same rate, the gap between creating the event and its start at half that rate, and your wallet balance. That gap counts whole hours, so creating an event less than an hour before it starts adds nothing. When the balance falls short the panel names the shortfall, links to Add credits, and Create event stays disabled. See Usage, credits, and event sizes.
- Slug: the identifier that forms your event’s web address. 3–32 characters, lowercase letters, digits, and dashes only, starting and ending with a letter or digit. The field checks availability as you type, showing a spinner while “Checking slug”, then “Slug available” or “Slug already taken”. When taken, up to three clickable suggestions appear after “Try:”. Locked at creation.
- Flag format prefix: the prefix players’ flags start with; letters and numbers only, at most 8 characters. A live sample shows the resulting format, e.g.
athena{s0me_s3cr3t_fl4g}. Auto-derived from the slug until you edit it. Locked at creation. - Event size: the select only lists sizes your plan allows; capacities and quotas per size are in Plans and limits. Choosing Extra Small shows the reminder “Extra Small CTF is for static challenges only.” Locked at creation.
- Enable team mode: “Players create or join teams. Leave off for individual competition. This is fixed when the event is created and cannot be changed afterwards.” Off by default; when off, players compete individually. Locked at creation.
- Max team size: appears only when team mode is on. Leave it blank for no limit. This one is editable later, in Settings → Registration & teams.
The event name, description, and schedule set here can all be changed later in Settings.
Everything below sits in an Optional configuration accordion, introduced with “Every section below has a working default and can be changed from event settings later.” That is accurate except for the permanently-badged fields called out above.
Branding
All optional and all editable later in Settings → General; they shape the player-facing landing page (see Brand your event for the full effect of each):
- Hero Title: the headline on the landing page. Leave it empty and the event name is used; everywhere else keeps the event name either way. Saved as Landing page title in Settings.
- Logo URL: must be a valid URL. There’s no file upload.
- Landing Description: the one-liner under the landing page’s headline; it also serves as the site’s meta description. Saved as Description in Settings.
- Event theme: one of eight themes, with a live preview of the one you’ve selected.
Rules & FAQ
A Rules & FAQ section on the create form lets you author both up front; the form notes that “You can edit these anytime from event settings.” Both start empty on the form, so fill them in now or leave them for later; either way they stay editable in Settings → Rules & FAQ.
- Rules: a rich-text editor for the event rules shown to players (placeholder “Write the event rules…”). Leave it blank and the event is created with a default rules document covering fair play and a plain-language summary of what the platform records to review suspected collusion. Anything you type replaces that default entirely, so if you write your own rules, carry the data-collection section across; it is what discloses the collection to your players.
- FAQ: an Add question button builds a list of question-and-answer entries; remove any row with its trash button.
Marketing
Free-text details shown on the landing page, all optional and editable later in Settings → Marketing: Hosted by, Prize pool, Categories (comma-separated tags, e.g. web,pwn,crypto,forensics), and three footer links (Discord, Writeups, and Contact).
Integrations
- Discord integration: lets players link their Discord account and lets the Athena bot serve your event’s server. Turn it on here, then connect the server on the event’s Discord page once the event is provisioned. That page is also where you change the toggle later. See Discord bot commands.
Sign-in
Everything you set here is locked at creation. Covered in full in Configure player sign-in:
- Require email verification: on by default; players must verify their email before signing in with email and password. Switching it off raises the warning “Recommended on for competitive events”.
- Athena accounts: a note, not a field. Every event you create offers Athena sign-in and it needs no credentials from you. It is the one sign-in choice you can change afterwards, from Settings → Athena sign-in.
- Under Social sign-in providers sit Google, GitHub, and CTFtime, each off by default. Enabling one reveals a Client ID and Client Secret field for your own OAuth app, both required while that provider is on; turning it off clears them.
The section header summarizes itself as Email sign-in only or N provider(s), counting only the three social providers; Athena isn’t included in that count and is available either way.
Registration & notifications
Three switches and one field (all editable later in Settings):
- Registration open: whether new players can sign up. On by default; turn it off to close signups (for example, mid-event). Editable in Settings → Registration & teams.
- Upcoming challenges banner: shows players a banner counting down to challenges that haven’t released yet. On by default. Editable in Settings → Organizer alerts.
- Solve notification emails: the event-wide switch for emailing players when they solve a challenge. On by default. Note that each player also has their own preference for these, so this switch enables the feature rather than guaranteeing delivery. Editable in Settings → Organizer alerts.
- Report notification emails: up to ten addresses emailed whenever a player opens a new report; type one and press Enter or comma to add it, or paste a comma-separated list. Follow-up messages on an already-open report don’t send email. Empty by default, which turns the emails off. Editable in Settings → Organizer alerts.
Limits
- Retry cooldown (minutes): a positive number of minutes, default 5. This is how long a team must wait between attempts to launch a challenge instance; it is unrelated to the wrong-flag submission cooldown below. Locked at creation.
Under the sub-heading Submission integrity, the wrong-flag throttle (editable later in Settings → Submission cooldown):
- Wrong attempts before cooldown: how many wrong flags a player may submit before the cooldown kicks in.
0disables the throttle. - Cooldown duration (seconds): how long the player must then wait. Both values must be above 0 for the cooldown to take effect.
Creating the event
Create event stays disabled while the name is invalid, the slug is taken or still being checked, the size isn’t allowed on your plan, or your wallet balance can’t cover the estimated credit hold. If your balance changes between opening the form and submitting, creation stops with “Not enough wallet credits to create this event. Add credits and try again.” (see Manage billing and credits). From there, the provisioning progress screen takes over; the walkthrough is in Host your first CTF.
Changing settings later
Every event has a Settings page in its dashboard. It’s organized into independent sections, most with their own Save button, and you edit and save one section at a time. Save only appears once you’ve changed something in that section. The sections are:
- General: “Event identity and branding shown to participants.” Event name, description, landing page title, theme, and logo.
- Schedule: “Start, scoreboard freeze, and end times.” Shown and edited in your local time zone, with a footer naming the zone. The create form, by contrast, is UTC throughout.
- Submission cooldown: “Throttle repeated wrong flag submissions.”
- Registration & teams: “Control who can join and how large teams may be.” Registration open and max team size.
- Organizer alerts: “Organizer email notifications for this event. Player-facing posts live on the Announcements page, and the Discord bot has its own page.” Report-notification emails, the upcoming-challenges banner, and solve-notification emails.
- Marketing: “Details surfaced on the event landing page.” Hosted by, prize pool, categories, and the footer links.
- Rules & FAQ: the rich-text rules and the FAQ list.
- Data export: “Event data exports are downloaded from the organization dashboard, which stays reachable after this event ends. One is produced automatically when the event ends.” One switch, Include participant email addresses, off by default: players are always identified by username, and turning it on adds their email address to the archive as well. It applies to archives built after you save it; see Export event data.
- Overage spend cap: “Stop this event drawing more than a set amount of wallet credit for runtime overage.” A Cap overage spend switch, off by default, and a Cap (USD) amount it reveals. New instance launches are refused once the event’s charged plus reserved overage would pass the cap; included instance-hours are never affected. Instances already running finish their session, so the cap can be exceeded by whatever was in flight when it was reached. See Usage, credits, and event sizes.
- Athena sign-in: “The Athena account button on this event’s sign-in page, and the scopes it may ask for.” One switch, Allow Athena accounts, on by default, with the scopes listed under it as “Scopes: openid, profile, email”. There is no Save button here: the switch applies as soon as you click it. Turning it off stops new Athena sign-ins and drops the access the platform had granted your event; players already signed in keep their session. See Configure player sign-in.
- Danger zone: ending the event; see The event lifecycle.
Only the fields listed above are editable here; the choices called out as locked at creation don’t appear on this page.
Saved changes reach the player site within moments: no redeploy, and nothing to restart on your side.
If someone else on your team saves a change while you have the page open, your save is rejected so you don’t overwrite their edit: “Settings were updated elsewhere. Retry your change.” Reload and reapply.
Version history
The Settings header has a Version history button. It opens a panel listing every saved version, newest first, with the current one marked and each version labeled by which fields changed and when. Any earlier version has a Revert button: reverting restores that version’s settings immediately and discards any unsaved edits on the page, after a confirmation that lists the fields it will change. A revert that restores a different End moves teardown to that End, under the same rules as editing the Schedule directly.