---
title: Configure player sign-in
description: Athena accounts come as standard on new events; add Google, GitHub, or CTFtime and choose your verification rules.
---

How players sign in to your event is configured in the **Sign-in** section of the event creation form. Players can always register with email and password. The form says so directly: *"Players can always sign in with email and password. Enable a provider to add its Client ID and secret."* Every event you create also offers Athena accounts with no setup from you. On top of that you can enable Google, GitHub, and CTFtime sign-in, and decide whether email verification is required.

:::warning[Most sign-in settings are locked at creation]
Email verification, team mode, and your OAuth providers can't be changed after the event is created (unlike most other settings, which you can edit later in **Settings**). Set up your OAuth apps and decide on verification and team mode before you submit.

Athena sign-in is the one exception: it is on for every new event, and you can turn it off afterwards from **Settings**.
:::

## Choose your baseline rule

**Require email verification** sits at the top of the **Sign-in** section, on by default. When enabled, players who register with email and password must verify their address before they can sign in. Turning it off raises a warning in the form: *"Recommended on for competitive events"* / *"With verification off, one person can register unlimited unverified accounts."* That warning is the whole argument for leaving it on.

(**Enable team mode** is a related create-time choice, but it lives in **Basic details** at the top of the form, not here. It's equally permanent; see [Event settings](/organizers/reference/event-settings).)

## Athena accounts on every new event

Above the provider toggles sits a short block you can't act on, **Athena accounts**: *"Every event offers Athena sign-in, so a player who already has an Athena account joins without registering again. It needs no credentials from you, and you can turn it off later in Settings."*

An [Athena account](/players/how-to/use-your-athena-account) is one identity a player uses across every event on the platform. Your event gets **Continue with Athena** on its sign-in page and **Sign up with Athena** on its registration page, and you supply nothing: no OAuth app, no client ID, no secret. There is nothing to configure at creation; the only control is the switch in **Settings** described below.

What it means for you in practice:

- Returning players from other Athena events join yours without filling in your registration form.
- Their name, handle and avatar arrive from their Athena account. The handle is adjusted to your event's own rule (lowercase letters, numbers and underscores), and if it's already taken here they get a numbered variant of it (`neo` → `neo_2`), so your scoreboard never has a collision.
- Nothing else crosses between events. Solves, points, teams and bans stay in your event.
- Your rules still hold. Closing registration blocks new Athena players, and a ban you issue still keeps that person out.

:::note[It doesn't count toward the section summary]
The **Sign-in** header still summarizes only the three social providers, so an event with Athena and nothing else reads as **Email sign-in only**. Athena is present regardless of what the header says.
:::

## Turn Athena sign-in off

Once the event is running, **Settings → Athena sign-in** carries one switch, **Allow Athena accounts**, with what your event asks for listed beneath it as *"Scopes: openid, profile, email"*. There is no **Save** button: the switch takes effect the moment you click it.

Turning it off is the control to reach for if you need to stop Athena players joining mid-event:

- No further sign-in with Athena succeeds, and the platform drops the access it had granted your event.
- Players already signed in **keep their session**. Your event holds its own login, independent of Athena, so nobody is kicked out. To remove someone, ban them from the **Players** page.
- Everyone who already joined keeps their account, solves, points and team. Nothing is deleted.
- Turn the switch back on and Athena sign-in works again, with no reconfiguration.

Enabling and disabling it are both recorded in the workspace **Audit log**, not the event's own **Audit log** page.

## Enable social sign-in

Under **Social sign-in providers**, each of the three has its own toggle, off by default. Turning one on reveals a **Client ID** and **Client Secret** field for it. You create the OAuth app with the provider and paste the credentials in. Turning a toggle back off clears its fields, and the form won't submit while a provider is enabled with empty credentials (*"Client ID is required when Google sign-in is enabled."*).

:::warning[Google, GitHub and CTFtime sign players **in**; they don't sign them **up**]
Enabling one of these three does not add a second way to register. Every account using them is created through the registration form; **Continue with Google / GitHub / CTFtime** only works for a player who already has an account on your event site. They appear on the sign-in page only, never on the registration page.

This is the most common support question these buttons generate, so it's worth saying plainly in your own event's FAQ: *register first, then link.*

**Athena is the exception.** It appears on both pages, and **Sign up with Athena** does create an account on your event. That is the point of it: a player who already has an Athena identity should not have to register again.
:::

Each toggle's help card links to the provider's own setup guide; follow it for the provider-side steps, then paste the resulting credentials into the form.

**Google**

Create OAuth 2.0 web-application credentials in the Google Cloud
Console, following [Google's OAuth 2.0 web server
guide](https://developers.google.com/identity/protocols/oauth2/web-server).
The form's help card links that guide alongside Google's OAuth 2.0 overview.

Paste the generated credentials into **Google Client ID** (it ends in
`.apps.googleusercontent.com`) and **Google Client Secret** (it starts
with `GOCSPX-`).

**GitHub**

Register an [OAuth App](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app)
under your GitHub account or organization (GitHub → Settings → Developer
settings → OAuth Apps), then generate a client secret for it.

Paste the app's credentials into **GitHub Client ID** and **GitHub Client
Secret**.

**CTFtime**

Request an OAuth2 client from CTFtime for your event. The form's help
card links [CTFtime's OAuth2 configuration
page](https://ctftime.org/for-organizers/oauth). This is required if you
want participants to sign in with their CTFtime accounts, which is a
natural fit for CTFtime-listed events.

Paste the client CTFtime issues you into **CTFtime Client ID** and
**CTFtime Client Secret**.

## What registration looks like for players

The account form asks for a **Display name** (up to 80 characters), a permanent **Handle** (3–32 characters, lowercase letters, numbers, and underscores, checked for availability as you type), an **Email**, and a **password of at least 8 characters**. There's no complexity requirement beyond that length. If you want stronger passwords at your event, say so in your rules rather than expecting the form to enforce it.

Sign-ups are protected by an automated anti-abuse check, so a player who clicks through too fast may see *"Captcha verification failed. Please try again."* and simply need to resubmit.

## Closing registration

**Registration open** is on by default and, unlike everything else on this page, stays editable for the life of the event, in **Settings → Registration &amp; teams**. Turning it off closes sign-ups completely: the registration form greys out with *"Registration is closed"* and a line telling visitors your event isn't accepting new accounts right now, but that existing players can still log in.

It closes **every** route to a new account, social sign-in included, while leaving existing players able to log in and play. That makes it the right lever for locking your roster once the event is underway.

## Before you submit

Double-check the section against how you plan to run the event:

- If you enable a provider, test that you can complete its setup guide end to end; a typo'd secret only surfaces when a player tries to sign in.
- If your event is invite-light and competitive, keep **Require email verification** on.
- Decide team versus individual play now; [team mode](/organizers/tutorials/host-your-first-ctf) changes how players experience the whole event and can't be flipped later.
