> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/uploading-assets-admin.md).

# Uploading Assets (Admin)

### Upload Assets to Marketing Center Team Library

Admins can now upload JPG, PNG, PDF, MP4, and GIF files to the Marketing Center team library to share them with other teams' agents.

The new "Add" button located at the top-right of the Marketing Center page allows the admins to select the teams or agents and upload the desired files.

After each asset is labeled by name and category, it will be available in the agents' Marketing Center.

Agents can also download and share the assets through SMS and URL.

{% embed url="<https://rechatq.wistia.com/medias/k8e4nhz6l7>" %}

### **Tags and Smart List** on Board View

This new update is found on the Contacts page. You now have the following options in the Board View style:

**Tags**: This option allows you to filter your contacts by a single tag, any contacts that have the tag will be shown on the boards.

**Lists**: You can also set multiple filters and save them as a list to use in your contact boards.

You are able to utilize these filters and tags to organize any contact to display them on the boards.

{% embed url="<https://rechatq.wistia.com/medias/6ybkpnydd1>" %}


---

# 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://help.rechat.com/whats-new/uploading-assets-admin.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.