> 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-a-research-project.md).

# Join a research project

<mark style="color:$primary;">**Outcome**</mark>\
You accept an invitation to an existing research project as a Space Administrator or Instance Editor.

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

* The project Space Administrator has sent you an invitation.
* You have read the invitation and confirmed the role it grants is appropriate.

Joining a research project is by invitation only. The acceptance flow is identical to any other Nuvolos invitation - see [How-to › Common Workflows › Accepting an invitation](/how-to-guides/common-workflows/accepting-an-invitation.md).

{% hint style="info" %}
Check the role in the invitation before accepting. Common roles for research collaborators are Space Administrator (full control over the project, including the ability to invite others) and Instance Editor (works in one specific instance only). \
For the full role definitions, see [Concepts › Roles, secrets and identity](/concepts/roles-secrets-and-identity.md).
{% endhint %}


---

# 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-a-research-project.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.