> For the complete documentation index, see [llms.txt](https://documentation.opencollective.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencollective.com/collectives/creating-a-collective/linking-connected-collectives.md).

# Linking Connected Collectives

When a Collective or initiative takes off, it’s not uncommon for local projects or separate Collectives to branch out from it.

You have the ability to display these “Connected Collectives” on your Collective page, so that people can view and potentially support these spinoff initiatives. These are displayed on the Collective’s page under “More Ways to Contribute”.

Connected Collectives:

* Don't share a budget
* They can have different Fiscal Hosts, with different currencies
* Admins of one Collective are not automatically admins of the other\
  \
  This feature can also be used by Organizations to show Collectives and users who are part of their group.

{% hint style="warning" %}
This option needs to be enabled manually by the Open Collective team.

Please ensure you have received approval from the admins of the Collectives you would like to connect with before reaching out to our team.
{% 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://documentation.opencollective.com/collectives/creating-a-collective/linking-connected-collectives.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.