> 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/commands-and-permissions.md).

# Commands & Permissions

## Commands

| Command                                                    | Who                     | What it does                                          |
| ---------------------------------------------------------- | ----------------------- | ----------------------------------------------------- |
| `/schooltablet`                                            | Staff                   | School tablet (the `school_tablet` item opens it too) |
| `/collegeadmin`                                            | Server staff, principal | Setup panel                                           |
| `/lesson`, `/startlesson`, `/endlesson`                    | Teachers                | Announce, start and end a lesson                      |
| `/attendance`, `/grade`, `/timetable`                      | Teachers                | Open those tablet pages                               |
| `/exams`                                                   | Teachers                | Exams on the tablet                                   |
| `/myexams`                                                 | Students                | Report card                                           |
| `/notebook`                                                | Anyone with the item    | Open the notebook                                     |
| `/discipline`, `/disciplinelog`                            | Staff                   | Discipline on the tablet                              |
| `/exit`                                                    | Students                | Use a hall pass                                       |
| `/myscholarship`                                           | Students                | Own scholarship                                       |
| `/schoollock open\|close\|auto`                            | Security                | Campus lock override                                  |
| `/closelessons`                                            | Server staff, principal | End every running lesson                              |
| `/scholarshipopen`, `/scholarshipreset`, `/scholarshipset` | Server staff, principal | Scholarship of a player by id                         |
| `/noteauthor`, `/notedelete`                               | Server staff, principal | Who wrote a page in the world; remove it              |

Command names are set in the `Commands` table of each file in `config/`.

## Keys

Players can change these in the game's key settings.

| Key           | What it does                                           |
| ------------- | ------------------------------------------------------ |
| **O**         | School notice history                                  |
| **J**         | Security alert history (security)                      |
| **G** / **H** | Mark the classroom / the teacher from a lesson notice  |
| **G**         | Call campus security when hurt on campus (`DownedKey`) |
| **X**         | Stop a job in hand (signing, detention chores)         |

## Permissions

```cfg
add_ace group.admin daddy.admin.college allow   # College only
add_ace group.admin daddy.admin allow           # every Daddy Studio resource
```


---

# 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/commands-and-permissions.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.