> For the complete documentation index, see [llms.txt](https://docs.onyxia.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyxia.sh/docs.onyxia.sh/v10/admin-doc/setting-up-group-projects.md).

# Setting up group projects

The user interface of onyxia enables to create projects for groups of Onyxia users.  

Users will be able to dynamically switch from one project to another using a select input in the header.

<figure><img src="/files/DmSN2VjDTCCYXu4ra9j7" alt=""><figcaption></figcaption></figure>

This select doesn't appear when the user isn't in any group project. &#x20;

All users of a group project share:

* The Kubernetes namespace, in "My Services" you can see everything that's running, including services launched by other person of the group. &#x20;
* Project settings. If a user change a project setting, it affects every member of the group.
* Secrets
* S3 Bucket (or an S3 subpath)

As of today, new group can only be created by Onyxia instance administrator, on demand and the procedure to create group is not publicly documented yet because we're still actively working on it.  \
However, if you want to enable this feature for your users, reach us, we will guide you through it! &#x20;

{% embed url="<https://join.slack.com/t/3innovation/shared_invite/zt-1hnzukjcn-6biCSmVy4qvyDGwbNI~sWg>" %}


---

# 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.onyxia.sh/docs.onyxia.sh/v10/admin-doc/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.