> For the complete documentation index, see [llms.txt](https://docs.nuvolos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvolos.com/how-to-guides/workflows-for-instructors/setting-up-group-projects.md).

# Set up group projects

<mark style="color:$primary;">**Outcome**</mark>\
You set up a separate group-work space with one instance per group, and group members are invited as Instance Editors.

<mark style="color:$primary;">**Before you start**</mark>

* You hold the Organisation Faculty or Organisation Manager role (required to create a new space). If you are a TA without those rights, ask the course instructor to create the space for you.
* You have a list of group memberships (which students belong to which group).
* You have decided whether to use shared editing (most reliable in JupyterLab 4.0.0 or later - see *Collaborative editing in JupyterLab* below).

Group projects work best as a **separate space** from regular coursework. Distributing two threads of workflows on top of each other tangles individual and group work - keeping them apart prevents that. The space hierarchy for group projects looks like this:

* A **group-work space** containing one instance per group.
* A **regular coursework space** with one instance per student.
* Students see both spaces in their Dashboard.

### Create the group-work Space

Follow the procedure in [Create a new course](/how-to-guides/workflows-for-instructors/create-a-new-course.md), but give it a name that clearly distinguishes it from the regular coursework space (for example: *Statistics 101 — Group Work*).

### Create one Instance per group

For each group, create an instance and invite its members as editors.

{% stepper %}
{% step %}
Navigate to the group-work space.
{% endstep %}

{% step %}
Click the cogwheel icon and select **Project Users / Instances**.
{% endstep %}

{% step %}
Click **+ ADD NEW INSTANCE**.
{% endstep %}

{% step %}
Choose whether to start from a snapshot or create an empty instance.
{% endstep %}

{% step %}
Name the instance after the group.
{% endstep %}
{% endstepper %}

### Invite group members as Instance Editors

{% stepper %}
{% step %}
In **Project Users / Instances**, open the **Instances** tab.
{% endstep %}

{% step %}
Find the group Instance you just created and click **+ INVITE USERS**.
{% endstep %}

{% step %}
Select **Option 1 - User Invitation** and **Invite to an existing shared instance**.
{% endstep %}

{% step %}
Choose **Instance Editor** as the role.
{% endstep %}

{% step %}
Enter the email addresses of the group members and click + INVITE.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
When entering email addresses for users already on Nuvolos, use the email listed under their name in the Members list. If the invitation is sent to a different email, the student will not be able to accept it with their existing Nuvolos account.
{% endhint %}

### Upload files and distribute

Once the space and instances are in place, upload group-work files to the Master Instance of the group-work space and distribute as usual. Since group and individual workspaces are separate, new groups added later can also be initialised from the Distributed Instance.

As the course proceeds, you can use cumulative distribution to push new material to all group instances, and you can bridge information between regular and group-work spaces via cross-distributing between spaces.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nuvolos.com/how-to-guides/workflows-for-instructors/setting-up-group-projects.md?ask=<question>
```

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.