> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/docs/platform/collaboratives/brand-resources.md).
# Brand Resources
Roll out a helpful new way to share logos, images, colors and other content with everyone in your collaborative, while easily keeping sponsor and member brand assets up to date.
## Sponsor Collection
Brand assets are made available to all members when they click into the sponsor's collaborative space.
A collection of logos, colors and brand imagery allow every member an easy way to view and use these assets—like adding the sponsor's logo to the footer of their site, for example.
## Member Collections
From property photos to seasonal images, hotels and resorts curate their own collection to share with the collaborative sponsor and other members.
And these assets are automatically synced from each members' platform account. That means there is no extra work for members and every asset is kept up to date.
---
# 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.flip.to/docs/platform/collaboratives/brand-resources.md?ask=&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.
