> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-college/first-setup.md).

# First Setup

`/collegeadmin` opens the setup panel for server staff and the principal. Its **Setup** page lists what the school still needs and checks that the jobs exist.

1. **Campus**: draw the school grounds as a box or a polygon. Security, hall passes and the campus lock work inside it.
2. **Classrooms**: draw each room; lessons are held in them.
3. **Student Affairs desk**: place the clerk where students come for their paperwork.
4. Optional: the detention room, its exit and chore spots, scholarship machines, school ATMs, gate guards, and the spot where students outside without a pass are brought back.

Places are put down with a free camera: click to place, drag the corners, scroll to turn. Every change is kept in **History** and can be undone.

## Roles

`Config.Roles` in `config/main.lua` maps jobs to roles:

| Role      | Default job                   | Can                                                                  |
| --------- | ----------------------------- | -------------------------------------------------------------------- |
| Student   | `student`                     | Attend lessons, sit exams, use the desk, spin the scholarship press  |
| Teacher   | `teacher` (and the principal) | Run lessons and exams, give points and sanctions                     |
| Principal | `principal`                   | Everything a teacher can, plus approvals, hiring and the setup panel |
| Security  | `school_security`             | Security Center, alerts, hall pass checks, campus lock               |

Server staff (the ACE `daddy.admin.college` or `daddy.admin`, or a framework admin) can use the setup panel and the admin commands.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-college/first-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.