> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/product/features/tasks/task-sharing.md).

# Sharing tasks

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/product/features/task-sharing.md).
{% endhint %}

People share a **task** with someone who can't open it in Snapfix, such as a contractor, a manager or a guest, in two ways: as a PDF **task report**, or as a read-only **share link** that expires. Anyone with the link sees the task's page without signing in: its details, image, note, checklist, tags, users and chat. Assets of an **asset register** are shared the same way, with their attributes in place of tags. Snapfix also makes share links on its own for contractors assigned to a task and for people who report a problem through a QR form.

## Rules

### Sharing from a task

* "Share" is on every task: in the web's title bar, and as the first item of the apps' task menu ("Share Task Report"). Everyone who can open the task may use it; Android hides it outside the task's time range ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#header-and-status)).
* It offers "Task Report" and "Task URL", on assets with asset wording ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task)).
* Sharing needs a connection on every platform ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task)).

### Task report

* "The Task Report contains the task summary including tags, cost & time, checklist summary, images and the entire audit trail including messages." ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task)).
* The web builds the report in the background ("The report is being generated.") and lists it with the user's [task reports](https://docs.snapfix.com/product/features/reports/task-reports.md) ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task)).
* The apps build it at once and hand the PDF to the phone's share sheet. A task with more than 50 photos, videos and drawings, or more than 100 checklist items, gets "This task is too large. Please generate the Task Report using the web app: …" instead ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task)).
* The report pages behind both need only the task's ID.

### Share links

* A link works until the end of the lifetime chosen when it was made: 1 day, 1 week, 1 month (the default) or 1 year on the web; 1 day, 1 week or 1 month in the apps, where Android starts on 1 day ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#where-links-come-from)).
* The web shows the link with "Copy URL" and "Open in new Window"; the apps open the phone's share sheet ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task)).
* On the web, the API makes a link only for the group's admins, members with "View All Tasks", and the task's followers and assignees; being the creator isn't enough on its own ([`POST /v1/app/tasks/generate-url`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksgenerate-url)).
* The apps' link action checks nothing and records the user named in the request ([`?action=generate_task_url`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-actiongenerate_task_url)).
* Links can't be listed, revoked or extended; each one simply expires ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#where-links-come-from)).
* Assigning a contractor emails them a link that lasts 1 year ([`POST /v1/app/tasks/notify-contractor`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksnotify-contractor)).
* A QR form whose success page has the share link turned on shows a 1-year link on its confirmation page and emails it when the guest gives an address ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#where-links-come-from), [QR forms](https://docs.snapfix.com/product/features/qr/qr-forms.md)).

### The shared page

* Anyone with the link opens the page without signing in, and everyone sees the same page; signed-in Snapfix users aren't recognized ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md)).
* The page shows "Access expires" with the expiry, the group, site and title, the image, "Note", the checklist with its percentage, tags or attributes, "Users" and "Messages" ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#layout)).
* Nothing on it can be changed; the checklist checkboxes do nothing ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#inputs)).
* The chat leaves out "Created Task", title and checklist item changes, time and cost entries, and every newer kind of activity, such as due dates, rooms, areas, assets, approvals, copies and moves ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#layout)).
* The page signs in to the API with a login built into it, and the answer carries the contact details of everyone on the task and the deleted messages.
* An expired, unknown or switched-off link, and any other failure, shows "Access to this task has expired." ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#states)).

## Flow

```mermaid
flowchart TD
  share["Share on a task"] --> choice{"Task Report or Task URL"}
  choice -- "Task Report, web" --> bg["Built in the background"] --> reports["Task reports"]
  choice -- "Task Report, apps" --> size{"Too large?"}
  size -- yes --> useweb["Use the web app"]
  size -- no --> sheet["Phone's share sheet"]
  choice -- "Task URL" --> life["Choose how long it works"] --> link["Link made"]
  link --> send["Copy or share the link"]
  send --> page["Shared task page"]
  page --> expired{"Still valid?"}
  expired -- no --> msg["Access to this task has expired."]
  expired -- yes --> view["Read-only task"]
```

## Platforms

| Capability          | Web                                           | iOS                                           | Android                                    |
| ------------------- | --------------------------------------------- | --------------------------------------------- | ------------------------------------------ |
| Where               | "Share" in the title bar                      | task menu, "Share Task Report"                | same as iOS; hidden outside the time range |
| Task report         | built in the background, then in Task reports | built at once, share sheet                    | same as iOS                                |
| Large tasks         | yes                                           | refused above 50 media or 100 checklist items | same as iOS                                |
| Link lifetimes      | 1 day, 1 week, 1 month (default), 1 year      | 1 day, 1 week, 1 month                        | same as iOS, 1 day by default              |
| After making a link | "Copy URL", "Open in new Window"              | share sheet                                   | share sheet                                |
| Shared page         | any browser                                   | any browser                                   | any browser                                |

## Screens

* [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md)
* [Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md)
* [Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md), which shares assets the same way
* [Task reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/task-reports.md), where the web's task reports appear

## API and data

* Links: [`POST /v1/app/tasks/generate-url`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksgenerate-url) (web), [`?action=generate_task_url`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-actiongenerate_task_url) (apps), [`POST /v1/app/tasks/notify-contractor`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksnotify-contractor) (contractor emails).
* The shared page reads [`GET /g-job/{jobToken}`](https://docs.snapfix.com/engineering-reference/api/tasks.md#get-g-jobjobtoken), which calls [`?action=guest_job_data`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-actionguest_job_data) and answers with a [shared task object](https://docs.snapfix.com/engineering-reference/api/tasks.md#shared-task-object-php-apis).
* Reports: `?action=job_report_v2` (web) and `?action=get_job_report` (apps) ([Reports API](https://docs.snapfix.com/engineering-reference/api/reports.md)).
* Tables: [`url_job_token`](https://docs.snapfix.com/engineering-reference/db/tables/url_job_token.md), one row per link with the task, the expiry, `{"read-only": true}` and who made it.

## Depends on

* [Tasks](https://docs.snapfix.com/product/features/tasks/tasks.md): who can open the task, and the time range.
* [Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md): the PDF and the web's list of reports.
* [QR forms](https://docs.snapfix.com/product/features/qr/qr-forms.md): tracking links for guests who report a problem.
* [Asset registers](https://docs.snapfix.com/product/features/assets/asset-registers.md): sharing an asset.
* [Time and cost](https://docs.snapfix.com/product/features/tasks/time-and-cost.md): included in the task report.

## Edge cases

* **Offline:** sharing refuses without a connection in the apps; the shared page treats a failed load as an expired link.
* **Deleted or moved tasks:** a link keeps showing the task, or the original of a moved task, with its chat until it expires; contractor and QR form links last a year.
* **Expired links:** there is no way to renew one; the owner makes a new link ([Shared task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/shared-task.md#where-links-come-from)).
* **Missing permission:** on the web, someone who can open the task only as its creator, without following it, gets "Access denied" for a link ([`POST /v1/app/tasks/generate-url`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksgenerate-url)). The creator follows every new task, so this is rare.
* **Display:** photos show at 200 px instead of filling the image, and asset dates near New Year can show the wrong year; the small-screen "Log In" link points at `/sign-in`.
* **Several sites:** a link belongs to one task and shows its site's name; nothing on the page depends on the viewer's sites.
* **Time zones and clocks:** "Access expires" shows in the viewer's local time. The web works out the expiry from the browser's clock, and the server doesn't compare it with the current time, so a wrong clock gives a wrong lifetime ([`POST /v1/app/tasks/generate-url`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksgenerate-url)).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/product/features/tasks/task-sharing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
