> 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/common-workflows/accepting-an-invitation.md).

# Accepting an invitation

<mark style="color:$primary;">**Outcome**</mark>\
You accept an invitation to Nuvolos, completing the sign-up if needed, and land in the right place to start working.

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

* You have received an invitation email from your institution's manager, your instructor, or a project lead.
* You know which email address you use (or want to use) for Nuvolos.
* You have decided which identity provider to use for sign-in if this is your first time on Nuvolos - institutional SSO, Google, or Nuvolos.

Nuvolos is an invitation-only platform. Every user - instructor, student, researcher, reviewer, collaborator - joins by accepting an invitation. The click-flow below is identical regardless of the role being granted; what differs is what you can do *after* you accept.

### Accept the invitation

{% stepper %}
{% step %}
Open the invitation email.
{% endstep %}

{% step %}
Click **Review Invitation**. This takes you to Nuvolos in your browser.
{% endstep %}

{% step %}
*Inspect the roles included in the invitation (see Common roles below). The role determines what you can do once inside.*
{% endstep %}

{% step %}
If you have never signed up for Nuvolos, complete the sign-up process now. Use the recommended login option for your institution.
{% endstep %}

{% step %}
Click **Accept Invitation**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
First-time sign-up may take up to a minute to complete. Wait for the sign-up to finish before clicking anything else.
{% endhint %}

{% hint style="warning" %}
**Login option matters - SWITCH cannot be added later.** For Swiss higher education users, choose the SWITCH option on first sign-in. If you sign up with email and password authentication instead, the SWITCH option will no longer be available for this account. The same applies to other institutional identity providers - pick the one that matches your institution on the first sign-in, not later.
{% endhint %}

### Common roles you might be invited with

* **Member -** typical for students. Cannot create courses or projects.
* **Faculty -** typical for instructors and researchers who manage their own courses or projects.
* **Manager -** Faculty plus organisation-wide management capabilities.
* **Space Administrator** - full privileges within a specific course or project.
* **Instance Editor** - read/write access to a single Instance only; cannot create Instances or invite others.

For the full role and capability matrix, see [Concepts › Roles, secrets and identity](/concepts/roles-secrets-and-identity.md).

### If you were invited with the wrong email address

Your invitation must be sent to the email address you already use for Nuvolos. If your colleague or instructor sent the invitation to a different address, you cannot accept it with your existing account. Ask them to re-send the invitation to the email address listed under your name in the project's Members list.

{% hint style="info" %}
This is the most common reason an invitation seems "broken". If you click Accept Invitation and end up on a Nuvolos sign-up page even though you already have an account, it almost always means the invitation went to a different email than your account email. Cancel the sign-up and ask the inviter to re-send.
{% endhint %}

### Where you land after accepting

Where the platform takes you depends on what you were invited to:

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Invitation type</strong></td><td valign="top"><strong>Where you land</strong></td></tr><tr><td valign="top">Organisation invitation (Faculty / Manager)</td><td valign="top">Organisation Dashboard. Create your first course or project from here.</td></tr><tr><td valign="top">Course invitation (instructor as TA / co-instructor)</td><td valign="top">Course space, in the Master Instance you were invited to.</td></tr><tr><td valign="top">Course invitation (student)</td><td valign="top">Your personal course instance, with distributed material already present.</td></tr><tr><td valign="top">Research project invitation (Space Administrator)</td><td valign="top">Project space with full access to all instances.</td></tr><tr><td valign="top">Research project invitation (Instance Editor)</td><td valign="top">The single instance you were invited to.</td></tr><tr><td valign="top">Group project invitation (student)</td><td valign="top">The group's shared instance, separate from your personal course instance.</td></tr></tbody></table>

From here, continue with the role-specific onboarding for whichever invitation type you accepted. See the relevant role document for the next steps.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.nuvolos.com/how-to-guides/common-workflows/accepting-an-invitation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
