How do I configure and manage Quest settings?

Quest settings explained

When you create or edit a Quest, you'll see a handful of settings that control how it behaves. Here's what each one does.

Setting	What it does
Title & description	What your team sees on the Quest's page. Description is optional but recommended — it's the difference between “Learn Something New” and someone actually understanding what counts.
Image	Optional. Adds a visual to the Quest's page and card.
Submission instructions	The prompt someone sees when submitting a completion (for example, “What book did you read?”). If you leave this blank, HeyTaco shows generic instructions instead.
Ask for proof	If turned on, the person submitting has to provide text evidence of completion before it can be approved.
Reward	How many tacos the Quest is worth. You can set a fixed amount, let the approver choose an amount at review time, or set it to zero if the Quest is just for recognition, not tacos.
Submission type	Whether people can self-submit, nominate a teammate, or both.
Approval required	If on, an admin has to approve a submission before tacos are awarded. If off, submissions are auto-approved the moment they're made.
Show completions publicly	If on, a completion feed and mini leaderboard appear on the Quest's page for everyone to see. If off, completions stay private.
Allow comments	If on, people can add a public comment along with their submission, which shows up in the completion feed. Only available if completions are shown publicly.
Limit per user	How many times one person can complete this Quest. Leave blank for unlimited.
Limit per team	How many times the Quest can be completed across your whole team. Useful for “first 10 people to ___” style Quests.
Wait time between submissions	The window in which one person can only complete this Quest once — daily, weekly, monthly, quarterly. Good for Quests you want to feel like a recurring habit rather than a one-off.
Timeframe	Optional open/close dates for Quests that you only want to run for a set period of time.

How completion and approval works

When someone submits a Quest completion (or nominates a teammate), it shows up under Admin → Quests as pending. From there, you can see who submitted it, who'll receive the tacos, any proof provided, and any public comment.

You can approve or deny the submission, with an optional note that gets sent to the person by DM. If approval isn't required for that Quest, submissions are approved automatically the moment they're made.

Anyone can see their own submission history under Profile → Quest Submissions — approved, denied, and pending. Nominations they've made for others show up there too, but nominations made about them don't (that's meant to stay a surprise until it's approved).

How limits work

Limits are always evaluated against the person who submits a completion, not nominees.

A pending completion counts against the submitter's user limit and wait time right away. This stops someone from submitting the same one-time Quest ten times while waiting on approval.
A pending completion does not count against the team cap. If it did, one submission sitting in the approval queue could block everyone else from submitting. Instead, the approval form flags when the team cap has already been reached, and it's the admin's call whether to approve or filter it out.

Frequently Asked Questions (FAQ)

Question	Answer
Can I require proof for some Quests but not others?	Yes — “Ask for proof” is a per-Quest setting, so you can require it for some and skip it for others.
What if I don't want to review every submission?	Turn off “Approval required” for that Quest. Submissions will be approved automatically as soon as they're made.
Can a Quest have no taco reward at all?	Yes — set the reward to zero if you want a Quest that's purely about recognition, with no tacos attached.
Does a denied or revoked submission count against someone's limit?	No — If one is denied, the person is free to submit again without it counting against their limit.