> 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-researchers/join-an-organization.md).

# Join an organization

<mark style="color:$primary;">**Outcome**</mark>\
You accept an organisation-level invitation and receive the Faculty or Manager role required to create your own research projects.

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

* A Manager in your target organisation (typically a PI or lab admin) has sent you an invitation.
* You know which identity provider you want to use to sign in (institutional SSO, Google, or Nuvolos).

Researchers are invited in one of two ways: to a specific research space (if you are joining as a collaborator - see the next page) or to an entire organisation (if you will create and manage your own projects). This page covers the organisation-level case.

#### Roles to look for in the invitation

To create and manage your own research projects, you need one of these roles:

* **Faculty** - the standard role for researchers. Lets you create new spaces, manage project data, and control access for collaborators.
* **Manager** - has all Faculty permissions and can additionally manage organisation-wide settings and invite other Faculty members.

If your invitation grants only the Member role, you can't create new spaces. Contact the inviter and ask for a Faculty role instead. For the full role definitions, see [Concepts › Roles, secrets and identity](/concepts/roles-secrets-and-identity.md).

#### Accept the invitation

The procedure for accepting any Nuvolos invitation is the same regardless of the role. See the canonical procedure: [How-to › Common Workflows › Accepting an invitation](/how-to-guides/common-workflows/accepting-an-invitation.md).


---

# 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/workflows-for-researchers/join-an-organization.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.