# Project Plugins
Project Plugins allow users to share custom content. Users are able to create self-contained content plugins, iterate on them and publish them to users.
{% hint style="warning" %} Project Plugins cannot reference content in any other project plugin or the project content. They must be self-contained or only dependent on engine content.
{% endhint %}
## Guides
Create a new Project Plugin Assets
1. Create a new project plugin that will contain all your content\
\
\\
2. Click `Assets` to open the Assets upload modal\
\
\\
3. Ensure the upload type is set to `Plugin`.
4. Select the plugins you would like to upload. Each one will be uploaded as a separate project plugin.
5. Click `Upload`.\
\
\\
6. You will not be able to see and manage your Project Plugin via the dashboard\
\
Upload a new Project Plugin Assets Version
To upload a new Project Plugin Assets Version, follow from Step 2 the same process used to [Create a new Project Plugin](#create-a-new-project-plugin-assets).
The upload will be a new Assets Version for the existing Assets.
Consume a Project Plugin Assets
Project Plugins are consumed via the [Launcher](/platform-documentation/apis-and-tooling/launcher/msquared-launcher/plugins.md)
---
# Agent Instructions: 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:
```
GET https://docs.otherside.xyz/platform-documentation/apis-and-tooling/dashboard/assets/project-plugins.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.