> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/missions/how-to-guides/share-a-mission-with-external-users.md).

# Share a Mission with External Users

Taskmaverick lets you share Missions with people outside your organization - customers, patients, or guests - via a QR code or direct link. No login required. Responses flow straight into your team's board and reporting.

## Why use this feature?

Some feedback and requests should come from people who don't have a Taskmaverick account. Instead of paper forms or separate survey tools, you can share any existing Mission as a public link.

**Hospital** — patients scan a QR code in their room to request extra blankets or water. Staff see the request instantly on their team board and respond.

**Restaurant** — QR codes on tables or receipts link to a quick dining experience survey. Managers see feedback in real time and can act before the customer leaves.

**Hotel** — guests receive a link after check-in to share feedback. Issues are flagged while the guest is still on-site.

## How it works

1. Create a [Mission](/missions/how-to-guides/build-a-mission.md) as usual ([Survey](/missions/what-are-missions/survey.md), [Checklist](/missions/what-are-missions/checklist.md), [Media](/missions/what-are-missions/media.md), or [Test](/missions/what-are-missions/test.md))
2. Generate a **public interface** for that Mission - this creates a QR code and a shareable link
3. Print the QR code or share the link with external users
4. External users open the link in their browser, complete the Mission, and submit
5. The response appears on your team's mobile board as a closed Mission marked "Public request"
6. Managers can review responses, see contact info (if collected), and respond directly

## How to set it up

{% stepper %}
{% step %}

### Create a public interface

1. Open a **Published** Mission (Survey, Checklist, Media, or Test)
2. Go to **Actions → Public Interface** (or click the Public Interface button in the Mission preview)
3. Fill in the configuration:

<table><thead><tr><th width="191.666748046875">Field</th><th width="108.333251953125">Required</th><th>What it means</th></tr></thead><tbody><tr><td><strong>Destination</strong></td><td>Yes</td><td>Which team board receives the responses</td></tr><tr><td><strong>Title</strong></td><td>Yes</td><td>Name for this link (shown in reporting)</td></tr><tr><td><strong>Form Header</strong></td><td>No</td><td>Text displayed at the top of the form before the first question</td></tr><tr><td><strong>Tag</strong></td><td>No</td><td>For organizing and filtering your public links</td></tr><tr><td><strong>Text after completion</strong></td><td>No</td><td>Message shown after the user submits</td></tr><tr><td><strong>Reference Unit</strong></td><td>No</td><td>Connect this link to a specific reference unit (only from folders with Designation = All)</td></tr><tr><td><strong>Contact information</strong></td><td>Yes</td><td>Enable or disable personal info collection</td></tr></tbody></table>

4. Click **Save & Generate QR**

{% hint style="info" %}
**Contact information options:** When enabled, you choose which fields to show (first name, last name, company, phone, email) and which are mandatory. You can also enable **Confirmation email** — the respondent receives a copy of what they submitted.
{% endhint %}
{% endstep %}

{% step %}

### Manage existing public interfaces

Go to the Mission → **Public Interface** tab in the sidebar. From here you can:

* **Copy** the public link
* **Preview** how the form looks on mobile
* **Open QR code** — download or print it
* **Edit** any configuration
* **Delete** a public interface

You can create **multiple public interfaces** for the same Mission — each with a different destination, tag, or reference unit. Useful for tracking responses by location.
{% endstep %}
{% endstepper %}

## What external users see

External users open the link in their browser (mobile or desktop). The page shows:

* Your organization's logo and name
* The form header (if configured)
* All questions displayed on a single scrollable page (no step-by-step navigation)
* Personal info fields at the bottom (if enabled)
* A submit button

After submitting, they see your completion message.

## How managers review responses

On the **mobile** [**team board**](/mobile-app/your-mobile-boards.md#team-board), public responses appear in the **Closed** tab with "Public request" shown instead of an employee name.

Opening the Mission details shows the full response. If contact info was collected, phone numbers and email addresses are **tappable** — managers can call or email the respondent directly.

In **Overview** and **Reporting**, public responses are included alongside regular Mission data. A dedicated [**Public Interface report**](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#public-interface) lets you analyze response volume, completion rates, and average duration per link.

## Good to know

* Available only for **Surveys, Checklists, Media, and Tests** - must be **Published**
* External users **cannot** provide photo/video proof or complete Media quizzes
* The **Person** question type is not shown to external users
* Changes to the Mission content apply **instantly** to the public link - no need to regenerate
* If the destination team is **deactivated**, the public link stops working (no need to delete it — reactivating the team restores it)
* If the Mission is **archived**, all its public links stop working. Restoring the Mission reactivates them with the same URLs.
* If the Mission is **deleted**, all public links and QR codes are permanently removed
* Public Missions can trigger [**Tickets**](/missions/what-are-missions/ticket.md) (shown as "Public request" in trigger details) but cannot trigger related Media
* Some Mission [settings](/missions/how-to-guides/configure-mission-settings.md) still apply to public responses: Ticket on Timer, Stopwatch, Reporting settings, and Test settings


---

# 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://documentation.taskmaverick.com/missions/how-to-guides/share-a-mission-with-external-users.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.