> 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/admin-doc.md).

# Admin doc

- [Install](https://docs.onyxia.sh/admin-doc/readme.md): Convinced by Onyxia? Let's see how you can get your own instance today!
- [Kubernetes](https://docs.onyxia.sh/admin-doc/readme/kubernetes.md): Provision a Kubernetes cluster
- [GitOps](https://docs.onyxia.sh/admin-doc/readme/gitops.md): Let's install ArgoCD to manage and monitor our Onyxia Datalab deployment!
- [User authentication](https://docs.onyxia.sh/admin-doc/readme/user-authentication.md): Using Keycloak to enable user authentication
- [Data (S3)](https://docs.onyxia.sh/admin-doc/readme/data-s3.md): Enable S3 storage via MinIO S3
- [Vault](https://docs.onyxia.sh/admin-doc/readme/vault.md)
- [S3 Explorer Standalone Deployment](https://docs.onyxia.sh/admin-doc/readme/s3-explorer-standalone-deployment.md): Deploy a standalone S3 browser with OIDC login and STS-based temporary credentials
- [Theme and branding](https://docs.onyxia.sh/admin-doc/theme.md): Customize your Onyxia instance with your assets and your colors, make it your own!
- [Catalog of services](https://docs.onyxia.sh/admin-doc/catalog-of-services.md): How Onyxia catalogs map to Helm repositories and how to customize them.
- [values.schema.json overrides](https://docs.onyxia.sh/admin-doc/catalog-of-services/override-schema-for-a-specific-instance.md): Instance Level Customization of the Service Catalog
- [Custom Catalogs](https://docs.onyxia.sh/admin-doc/catalog-of-services/custom-catalogs.md): Declare your own repository of charts
- [x-onyxia](https://docs.onyxia.sh/admin-doc/catalog-of-services/custom-catalogs/onyxia-extension.md): Onyxia's JSON Schema extention
- [Declarative User Profile](https://docs.onyxia.sh/admin-doc/catalog-of-services/custom-catalogs/declarative-user-profile.md)
- [JSON Schema Support](https://docs.onyxia.sh/admin-doc/catalog-of-services/custom-catalogs/json-schema-support.md): This section describes JSON Schema support in the launcher.
- [OpenID Connect Configuration](https://docs.onyxia.sh/admin-doc/openid-connect-configuration.md)
- [S3 Configuration](https://docs.onyxia.sh/admin-doc/s3-configuration.md)
- [AI Integration](https://docs.onyxia.sh/admin-doc/ai-integration.md)
- [Setting up group projects](https://docs.onyxia.sh/admin-doc/setting-up-group-projects.md): Enabling a group of users to share the same Kubernetes namespace to work on something together.
- [Security considerations](https://docs.onyxia.sh/admin-doc/security-consideration.md): Information about security considerations
- [Offline / airgap considerations](https://docs.onyxia.sh/admin-doc/offline-airgap-considerations.md)
- [Custom Pages](https://docs.onyxia.sh/admin-doc/custom-pages.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onyxia.sh/admin-doc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.