> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/plans-and-billing/for-classrooms.md).

# For classrooms

Apply for Felt's free Classroom plan for higher education. Set up a class workspace and invite students to create and share maps.

The free Classroom plan is for teaching in higher education. Instructors apply for their class and invite students to join. Anyone can also use the [Free plan](/plans-and-billing/free-plan.md).

The Classroom plan includes the Business plan's features, with different usage limits. Plan notes in this help center that include the Business plan cover the Classroom plan too. Students get seats, so they can create maps, upload and analyze data, and share their work with a link.

## Set up your classroom

{% hint style="info" %}
Create one workspace for each class you teach to keep each class's maps separate. Inside a workspace, use projects for units and group assignments.
{% endhint %}

### Step 1: Create a workspace

[Sign up for Felt](https://felt.com/signup) with your institution's email address, and create a workspace for your class. Felt uses your email address to verify that you're the instructor. You become the workspace's admin.

### Step 2: Apply for the Classroom plan

Fill out the classroom form. Verification takes up to two weeks. Felt emails you when your class is verified, and the workspace moves to the Classroom plan.

{% embed url="<https://docs.google.com/forms/d/e/1FAIpQLSdWVaz6EYMus2YW6RYHURcCNSeE6hUkLG1uY-TkNqdy-46H7g/viewform?usp=sf_link>" %}

### Step 3: Invite your students

1. Click your workspace name in the sidebar, then click **Invite members**.
2. Enter your students' email addresses, separated by commas. You can paste a whole list at once.
3. Select **Edit** so each student gets a seat.
4. Click **Send invites**. Each student gets an email invitation.

Give co-instructors and teaching assistants Admin access so they can manage members and settings. To manage students later, open **Workspace settings** and click the **Members** tab. See [Manage members](/administration/manage-members.md).

## Run assignments

Students submit a map by sharing its link. See [Share a map](/share/share-a-map.md). To give everyone the same starting point for an exercise, share a template map for students to duplicate. See [Duplicate and move maps](/maps/duplicate-and-move-maps.md).

Put the course materials you want every student to see in a project that's open to the workspace. Use private projects to prepare upcoming units or to give each group its own space. See [Organize maps](/maps/organize-maps.md).

When the Classroom plan ends, the workspace moves to the Free plan. Maps stay, and uploaded data is kept for 60 days. See [When a plan ends](/plans-and-billing/billing.md#when-a-plan-ends).

## Resources

* For instructors: the [Fundamentals of GIS](https://gisfundamentals.felt.com/) course materials, and an [example exercise for teaching spatial analysis](https://felt.com/blog/spatial-analysis-for-education).
* For students: [Felt's YouTube channel](https://www.youtube.com/@feltmaps), this help center, and the [Felt developer docs](https://developers.felt.com/) for more technical units.


---

# 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://help.felt.com/plans-and-billing/for-classrooms.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.