> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/archive/jupyterhub/github-classroom-instructor-guide/prerequisites.md).

# Getting Started

## Step 1: Request an organization for your class

You can follow instructions [GitHub's instruction](https://help.github.com/articles/creating-a-new-organization-from-scratch/) to create your organization. Plese note that you should create a different **organization per class per year,** for example CS50-spring19. Also will be requesting a **free plan and applying for a classroom discount** that will allow you to have unlimited private repositories. To request the discount, follow directions [here](https://help.github.com/articles/applying-for-a-classroom-discount/).

{% hint style="info" %}
Often CIS can perform this step for you. Check-in with us!
{% endhint %}

## Step 2: Create a classroom

Visit <https://classroom.github.com/classrooms> to create your classroom. You will be asked to select an organization fro your classroom. Follow link to grant access to your newly created organization, after that, you will be able to select it

![](https://2883398872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLCCXzhzhO5fUT5UTHC-887967055%2Fuploads%2Fgit-blob-75445ee70b1bd443e5efb6b8b0967e7dc0c8bbc2%2Fimage%20\(11\).png?alt=media)

After selecting your organization, you will be asked to name your classroom, invite admin members and add a class roster. **Skip steps to set up your roster** for the moment.

Congratulations! You are now ready to start using your classroom to distribute assigments and if desired, your lecture.


---

# 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://docs.ccv.brown.edu/archive/jupyterhub/github-classroom-instructor-guide/prerequisites.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.