> 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/how-the-apps-work/screens/compliance/mobile-notice.md).

# Comply

{% 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)). Platforms: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/compliance/mobile-notice.md).
{% endhint %}

A notice that Comply is live in the web app for account admins, with the support email address. It is the only Comply screen in the apps, and it calls no API.

* **Where:** iOS: the Plan page's "Comply" button, which the side menu's "Comply" item also opens. Android: the "Comply" chip on the Plan tab, which the side menu's "Comply" item also opens. iOS hides the button when the planner is opened from a task list, and Android hides the chip in a group's planner.
* **Who:** any signed-in user who opens the Plan page. Neither app checks a role, although the notice says Comply is "available to your Account Admins" and the web shows "Comply" to site admins only \[[ASK-114](https://github.com/snapfix/docs/blob/main/ASK.md#ask-114-who-should-see-comply-in-the-mobile-apps)].
* **Feature:** [Comply](https://docs.snapfix.com/product/features/compliance/comply.md)

## Layout

**iOS:** the Plan page's top bar and its page buttons, with "Comply" selected; a trial banner above the notice when the site's trial banner shows. Then the title "Comply", the subtitle "IS LIVE ON WEB", the message with the support address, and a sign-off with the founder's name and "Snapfix Founder".

**Android:** the Plan tab's chip row ("Planned Tasks", "Asset registers", "Comply", "Housekeeping") with "Comply" selected. Then "COMPLY", the subtitle "IS LIVE ON WEB" (the string "Is live on web" in capitals), the message, "Thank you,", the founder's name and "Snapfix Founder".

The message reads "We are working hard to create the simplest and best Compliance solution for you. It is now live on your Snapfix Web, and available to your Account Admins. Please contact" the support address "and we will be happy to help." iOS has "we will he happy to help." instead.

## Inputs

None.

## Actions

| Action                                                  | Who              | What happens                                                                                          | API |
| ------------------------------------------------------- | ---------------- | ----------------------------------------------------------------------------------------------------- | --- |
| Side menu "Comply", or the Plan page's "Comply" control | Anyone signed in | Shows the notice                                                                                      | -   |
| Tap the support address                                 | Anyone signed in | Opens a new email to the support address                                                              | -   |
| Another Plan page button or chip                        | Anyone signed in | Shows that page. On Android, tapping the Plan icon while Comply is open switches to another Plan page | -   |

## States

* **Loading, Empty, Error:** none; the notice is static text.
* **No permission:** none; every user can open it \[[ASK-114](https://github.com/snapfix/docs/blob/main/ASK.md#ask-114-who-should-see-comply-in-the-mobile-apps)].
* **Offline (mobile):** works, since it makes no requests.

## Dialogs and sheets

### Coming soon dialog (Android)

`ComplyDialog` shows "COMPLY", the subtitle "COMING SOON", a message that asks for suggestions for the compliance solution with a staff email address, and a sign-off. The address opens an email app, or the alert "No email app founded in this device." when none is installed; "×" closes the dialog. It opens only from the bottom bar's Comply tab, which is hidden, so no visible control reaches it \[[ASK-10](https://github.com/snapfix/docs/blob/main/ASK.md#ask-10-which-differences-between-the-ios-and-android-apps-are-intended)].

## Platform differences

* The iOS intro coach mark still lists "COMPLY: Coming soon", which contradicts the notice.
* iOS shows a trial banner above the notice when one applies; Android does not.
* Android keeps the old "Coming soon" dialog ([above](#coming-soon-dialog-android)).
* Neither app has compliance systems, contractors, documents, a dashboard or a timeline. They can link a compliance system to a task ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#compliance-system)) and pick one for a planned task ([Planned task](https://docs.snapfix.com/how-the-apps-work/screens/planner/planned-task.md)).


---

# 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/how-the-apps-work/screens/compliance/mobile-notice.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.
