# The Admin Panel ## Structure The Admin Panel can be accessed at `/admin`. It is made of two parts: * The **monitoring** section * The **configuration** section ### The Monitoring section Here you can create and run batches of games and monitor player statuses. ### The Configuring section Here you can create factors and treatments before creating batches. ## Clearing Players: How players can play again, even if they were led to the exit steps. Players can only play once. If there is a problem (e.g., the lobby timed out or the game was full), or if you want players to play again, you can *clear* them, which allows them to play again. In the **monitoring section**, in the **players tab**, you can see the status of every Player. A button called `Clear`, to the right of each player line, allows you to clear them one by one. Once *retired*, players can refresh their page/return to the link of your game, and they will be randomly allocated to a game with the same treatment as before. They are allocated to a game with the same treatment, so they don't discover a game with different conditions or instructions. ## Treatments and factors settings The treatments and factors are saved in a `.empirica/treatments.yaml`. It is often shared by simply committing it to your code versioning system (e.g., Git). You can edit treatments and factors manually in that file (make sure to reload the admin page after edits). Alternatively, you can edit these directly in the admin UI, which will update the `.empirica/treatment.yaml` file. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.empirica.ly/guides/the-admin-panel.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.