> For the complete documentation index, see [llms.txt](https://questn.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://questn.gitbook.io/docs/launch-airdrops/create-a-collection.md).

# Create a Collection

{% hint style="info" %}
**What is the difference between a Quest and a Collection?**

The Collection feature is designed to accommodate a wide range of scenarios, serving as an extension of the quest template, which is commonly used for large-scale joint activities. it is well-suited for partnerships involving multiple project stakeholders. Each event is equipped with a dedicated landing page and a comprehensive set of final rewards for participants. [Click here for a sample collection](https://app.questn.com/event/887681732169277738).
{% endhint %}

<figure><img src="/files/pyMl6MF3utgcf8t1naKL" alt="" width="563"><figcaption></figcaption></figure>

## Step 1 - Fill out Basic Info

Same as it is in the [Quest Settings](https://questn.gitbook.io/docs/create-airdrops/create-quest), just a banner is needed in addition!

<figure><img src="/files/7XWjzYYCi9WBcGfUks96" alt="" width="563"><figcaption></figcaption></figure>

## Step 2 - Set Up Reward

Same as it is in the [Quest Settings](https://questn.gitbook.io/docs/create-airdrops/create-quest)

<figure><img src="/files/zRyzsT4AsVHPIcEVWSj2" alt="" width="563"><figcaption></figcaption></figure>

## Step 3 - Select Quests

1. Quest Collection, as a collection of quests, you can select the quests created by your community into the collection.

<figure><img src="/files/iWU9R7s8Jlk2Cz3KqfQM" alt="" width="563"><figcaption></figcaption></figure>

2. By `Enter Quests amount`, you can set the number of the quests that must be completed to be in the draw of the final rewards of the Collection.

<figure><img src="/files/YJDyA0zkumYSP3DZg7Vh" alt="" width="563"><figcaption></figcaption></figure>

## Step 4 - Invite [<mark style="color:purple;">Co-host</mark>](#user-content-fn-1)[^1] (Optional)

1. Turn on `Co-host Feature` and click `➕ Add Co-host`

<figure><img src="/files/Js9zL20ggnQShzCkLfrD" alt="" width="563"><figcaption></figcaption></figure>

2. Search your co-host’s QuestN community by using their link and click `Invite` to select. After you finish adding or co-hosts, click `Confirm` to send out invitations to your partners

<figure><img src="/files/hcvwP7KukEWcNAarJJBO" alt="" width="563"><figcaption></figcaption></figure>

3. Ask your partners to accept co-host invitation
4. Check the notification system, all invitation requests will be there. Click ✓ or X to accept invitation or reject

<figure><img src="/files/qw00HU8h4M2gy1yFHNZo" alt="" width="563"><figcaption></figcaption></figure>

[^1]: You can invite other project parties to co-host the event with you. Their community information, including logos, will be displayed on the landing page. See examples below. The event will also appear on their community homepage.


---

# 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://questn.gitbook.io/docs/launch-airdrops/create-a-collection.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.