# Step3: Extra Settings

### Recurrence

After setting the details of task requirements, you need to set **`Recurrence`**.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FXMvt2FBg7JQXX5BfPLXS%2Frecurrence.png?alt=media&#x26;token=f5ecbe11-00c2-46c4-bb8e-fcecda884ccd" alt=""><figcaption></figcaption></figure>

Recurrence means the number of times your task will cycle. Currently, you can set tasks to occur Once, Daily, Weekly, or Monthly.

* `Once:` Users can only complete this task once.
* `Daily`: The daily task will reset at 12am UTC time everyday. Users can participate again after the task reset, regardless of whether they have completed it yesterday.
* `Weekly`: The weekly task will reset at 12 am UTC every Sunday. Users can participate again after the task reset, regardless of whether they have completed it in the previous week.
* `Monthly`: The monthly task will reset at 12 am UTC on the first day of each month. Users can participate again after the task reset, regardless of whether they have completed it in the previous month.

### **Set Rewards**

Points are linked to the user's level within your Community, reflecting their level of engagement with your Community.&#x20;

`Level design` is entirely at your discretion, including the names (points), and criteria for each level, and if you have already designed your own level system on another platform or Discord group, you can seamlessly migrate that system here (if in your level system, "XP" refers to points, you can directly modify it).

[*For more information on designing membership levels, please refer to this tutorial.*](https://taskoncommunitys-organization.gitbook.io/guide-book/community-hub/level-settings-points-based-level-system)

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FqSyKOPUeGq8qusUZNjaw%2Frewards.png?alt=media&#x26;token=e00bd052-c2e3-4bf4-924f-2d5b049d50c5" alt=""><figcaption></figcaption></figure>

### **Time Frame**

A timeframe setting allows a task to start or end at a designated time. Please note that in the TaskOn community, time frames are not mandatory; you can set `long-term tasks` without any time constraints.

* For `long-term` tasks, such as following X(Twitter) or interacting with a specific product feature, you can set the date at `Start Time` and choose '`Never Expired`' when set `End Time`.
* If you want to set a `time-limited` task, simply specify the start and end times.
* If you want the task to start immediately after publishing, select "`Immediately After Task Published`".

*Time-limited tasks will automatically be categorized into the `expired sector` after the specified time has elapsed.*

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FVc8pjBrPAgJhU4Tu7mIZ%2F%E6%88%AA%E5%B1%8F2024-03-14%2017.00.00.png?alt=media&#x26;token=6e0b9f03-4308-4cfe-ae9f-b6524ee79fc6" alt="" width="563"><figcaption></figcaption></figure>

### **Set Task Condition**

When designing tasks, you also have the option to set task conditions.&#x20;

#### **Meet All Conditions & Meet Any Condition**

**Meet All Conditions:** For Web3 projects, requiring all conditions to be met means that members need to be fully committed. This enhances security and trustworthiness and reduces fraud risks and boosting credibility.

**Meet Any Condition**: Allowing members to participate after meeting any single condition, such as holding specific NFTs or project tokens, attracts more users, fosters community interaction, and strengthens the project's community impact and sustainability. This is crucial for Web3 projects due to their decentralized nature.&#x20;

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FFTSz55eFfK0lLOSVuOGZ%2F%E6%88%AA%E5%B1%8F2024-03-14%2018.22.25.png?alt=media&#x26;token=9f1e9848-d80c-46a4-ac93-8259fa273e06" alt="" width="375"><figcaption></figcaption></figure>

#### Conditions Category

Currently, the community supports `Member Level`, `Discord Role`, `NFT Holder`, `Token Holder`, and `Task Completed`.

If you want your task to be available only to members who meet specific criteria, select the "`Condition`", and choose the condition, so that only members who meet the criteria can participate. This can effectively motivate the qualified members and enhance their loyalty.

**Member Level:** Setting a Member Level condition helps identify and differentiate users based on their activity levels, allowing for tailored privileges and rewards for `higher-level` members and increasing activity and loyalty.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FSvqD979S0NHE8mQHGTRZ%2F%E6%88%AA%E5%B1%8F2024-03-14%2017.34.11.png?alt=media&#x26;token=c5b17ef2-b0d5-48b0-9b07-fd418e5e608e" alt="" width="372"><figcaption></figcaption></figure>

1. Click "`Add`" and enter the number of member level.

**Discord Role:** This condition simplifies member authentication and management processes and limits  exclusive tasks/quests and rewards to specific members, thereby fostering interaction and belonging among community members.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FgvB4IjGAmGMIrVQ6j6fg%2F%E6%88%AA%E5%B1%8F2024-03-14%2017.34.19.png?alt=media&#x26;token=385deb72-6e34-40ee-ba1a-29f532f2d2ea" alt="" width="375"><figcaption></figcaption></figure>

1. Before setting the Discord role, please ensure that you have [**added the TaskOn bot to your server**](https://taskoncommunitys-organization.gitbook.io/guide-book/community-hub/bot-integration/discord-integration/how-to-add-taskon-discord-bot)**.**
2. Select Discord role.

**NFT Own:** Enforcing an NFT Holder condition promotes NFT projects, and incentivizes members to hold specific NFTs.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FcrPH6xAVM3pDs2xTIwxL%2F%E6%88%AA%E5%B1%8F2024-03-14%2017.34.25.png?alt=media&#x26;token=2269eb86-2dd8-4391-99f9-fe54be57bd10" alt="" width="375"><figcaption></figcaption></figure>

1. Choose the network, select NFT and enter the number.

**Token Own:** By requiring the Token Holder status, users are encouraged to hold tokens. This increases their value and provides holders with additional rewards and participation opportunities.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FqpjABOWWowfIDtFH181k%2F%E6%88%AA%E5%B1%8F2024-03-14%2017.34.32.png?alt=media&#x26;token=d15b1640-1fbb-4db1-b1bd-856cb0404bc3" alt="" width="375"><figcaption></figcaption></figure>

1. Choose the network, select token, and enter the number.

**Task:** Setting a Task Completed condition guides users to fulfill specific tasks or activities, increasing participation and offering rewards or recognition upon completion.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FgvfKAsd2uEeLjDUV8KIz%2F%E6%88%AA%E5%B1%8F2024-03-14%2017.34.38.png?alt=media&#x26;token=f91ca81a-9632-4326-ac0f-1a82632ff97c" alt="" width="375"><figcaption></figcaption></figure>

1. Select task.

### Claim Limit

`Claim limit` refers to the maximum number of times a user can complete a specific task. For instance, if you set the limit to 100, a user can complete the task at most 100 times.

For users who haven't purchased the `EE plan`([*Billing & Plans*](https://taskoncommunitys-organization.gitbook.io/guide-book/billing-and-plans)),  the total number of tasks the community can claim per month is fixed. If this limit is exceeded, additional purchases or `plan upgrades` are required. You can utilize this feature while setting up tasks to control excessive claim.&#x20;

1. Click "`Add`" and enter the `number`.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FAMjKDp2u68fuaXfg8z8I%2F%E6%88%AA%E5%B1%8F2024-03-18%2014.56.38.png?alt=media&#x26;token=204f2213-d87b-4b86-b3c6-d8cd57762ff9" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FcUUbejCeCJKNgncNtgvO%2F%E6%88%AA%E5%B1%8F2024-03-18%2014.56.30.png?alt=media&#x26;token=c26f42d0-78c6-46cc-bdde-5f99653bf978" alt="" width="563"><figcaption></figcaption></figure>

### Retry

If user fail to complete a task within a short period, you can set up a retry option to allow users to attempt later.

<figure><img src="https://3435385094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhotRGhsA7iGGmOsMlF0%2Fuploads%2FoQSXzGlKubLqIjxrOXzg%2F%E6%88%AA%E5%B1%8F2024-03-18%2015.07.54.png?alt=media&#x26;token=f5fdfd26-b1f7-4e49-bfcd-da6191b7d8c2" alt="" width="563"><figcaption></figcaption></figure>

After all task settings are done, click “`Publish`”. Or, you can click “`Save as Draft`”, if you need to edit it later.