> For the complete documentation index, see [llms.txt](https://help.rhinonature.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhinonature.com/manual/ecosystems.md).
# Ecosystems
## Overview
The Ecosystems rollout provides complete control over ecosystem management.
**Name** - Specifies the name of the ecosystem.\
**Preview** - Controls whether the ecosystem should be previewed in the viewport.\
**Render** - Controls whether the ecosystem should be present in the render.
## Buttons Strip
**Add Ecosystem** - Adds a new ecosystem.\ 
**Delete Ecosystem** - Deletes the selected ecosystem.\ 
**Duplicate Ecosystem** - Duplicates the selected ecosystem.\ 
**Bake Ecosystem** - Bakes the selected ecosystem to the document.\ 
**Ecosystem Statistics** - Shows the selected ecosystem population metrics.
**Open Preset** - Opens the selected preset file.\ 
**Save Preset** - Saves the selected ecosystems to a preset file.\ 
**Library Browser** - Opens the [Library Browser](/manual/library-browser.md) window.
## Ecosystem Properties
**Global Seed** - Specifies the seed value used for distribution evaluation. Changing this value allows creating different variations of the selected ecosystem.
---
# 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://help.rhinonature.com/manual/ecosystems.md?ask=&goal=
```
`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.