---
title: Your account, reports and feedback
description: Sign in, keep your profile current, report a problem to the organizers and leave feedback on an attack/defence event.
---

An attack/defence event site has its own accounts, like any Athena event. This page covers the parts that aren't about the game itself.

## Sign in

The sign-in page offers an email and password, plus whichever of **Continue with Athena**, **Continue with Google**, **Continue with GitHub** and **Continue with CTFtime** the organizers turned on. These buttons sign in to an account you already have. To join an event for the first time with Athena, Google or GitHub, use **Sign up with Athena**, **Sign up with Google** or **Sign up with GitHub** on the registration page; see [Use your Athena account](/players/how-to/use-your-athena-account). Your handle is taken from that account and gets a number added if another player already has it.

If you already registered with an email and password, signing in with Google or GitHub for the same email may say an account already exists. Sign in with your password, then click **Connect** next to the provider under **Account** on your **Profile**. The provider has to report the same email, verified.

If the organizers require it, a new account must open the verification link emailed to it before it can sign in. That applies to a Google or GitHub sign-up too when the provider hasn't verified the email. A verification link expires after an hour; when sign-in says your email isn't verified, enter your email under **Send a new verification link** on that page to get a fresh one. A forgotten password is reset from **Forgot your password?** on the sign-in page. The new-password page tells you if the link has expired or was already used; request another one then.

A suspended account can't sign in. The message names the organizers' Discord or contact link when the event has one, which is where to appeal.

## Your profile

**Profile** shows your **Display name**, which you can change and save with **Save changes**, and your handle, email and user ID, which are fixed. Your display name is how you appear on your team's roster.

When the event runs a Discord server, **Get a link code** under **Discord** gives you a one-time code to link your Discord account with the bot's `/link` command. See [Discord commands](/players/attack-defence/reference/discord-commands).

## Report a problem

Open **Reports**. Under **Report a problem**, choose **What is affected**, either one of the event's services or a part of the platform, then **What went wrong**, add any **Details** and click **Send report**. The organizers see it straight away.

Each report is a thread on the same page, with the organizers' replies. While it's open, **Add update** adds to it. Reporting the same service or area again while a report is open adds to that thread rather than starting another.

Report broken services and platform problems here. Questions about your own exploits or patches aren't something the organizers can answer.

## Leave feedback

**Feedback** opens at the time the page shows, which the organizers set. It asks **How was the event overall?** with a rating and an optional comment. You send one entry, and sending again updates it.

The game itself keeps running when feedback opens: the scoreboard keeps updating and flags keep scoring until the event ends.
