> 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/onboarding/configuring.md).

# Configuring Snapfix

{% 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/onboarding/configuring.md).
{% endhint %}

A progress screen while Snapfix creates the new site from the setup answers. The user makes no choice here.

* **Where:** iOS and Android: after [Grid or list](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/grid-or-list.md), the last setup step.
* **Who:** people finishing the app's setup flow, which the current apps do not open ([Start or join](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/start-or-join.md)).
* **Feature:** [Site setup in the app](https://docs.snapfix.com/product/features/onboarding/site-setup.md)

The screen sends one of two php-apis actions as soon as it opens:

| Situation                                    | Call                                                                                                                                                          | What comes back                                                          |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Starting, with one or more work types        | [`POST ?action=create_parent_with_templates`](https://docs.snapfix.com/engineering-reference/api/onboarding.md#post-actioncreate_parent_with_templates)       | The data the app needs for the new site, which it stores before going on |
| Starting with "I don’t know yet", or joining | [`POST ?action=create_parent_without_templates`](https://docs.snapfix.com/engineering-reference/api/onboarding.md#post-actioncreate_parent_without_templates) | The site record only                                                     |

iOS picks the call from the start-or-join choice and whether any work type is picked. Android picks the call without templates when `notes` and the opt-in are set and the work-type list is empty. The web setup form creates sites a third way ([Create your Snapfix account](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/setup-form.md)), and this screen reads the same whether the person starts a site or said they are joining one \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)].

## Layout

1. A looping Snapfix logo animation in the middle. There is no back arrow: iOS turns off the swipe back, and Android's back arrow is hidden.
2. A progress bar.
3. iOS: "Give us a moment, \nwe are configuring\nSnapfix for you." Android: "Give us a moment,\nwe are configuring \nSnapfix for you."

iOS also has an app version label ("v." and the version), but it is hidden. Android's layout has a "1/4" counter in a hidden frame.

The bar does not follow the request. iOS, each second, sets it to twice its value plus 0.05, so it is full after about five seconds; the branch meant for slow calls compares the timer's one-second interval with 10, so it never runs. On success iOS sets 0.65, then 1 a second later. Android adds 1 a second on the call with templates and jumps to 100 on success; on the call without templates the bar stays at 0 until it jumps to 100.

## Inputs

None. The screen sends what the earlier steps kept:

| Field                                 | From                                                                                                                                     | Sent with         |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| `user_uuid`                           | The signed-in user, from the app's storage, not from the token                                                                           | Both calls        |
| `parent_name`                         | [Company and role](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/company-and-role.md)                                    | Both calls        |
| `industry_uuid`, `industry_role_uuid` | [Company and role](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/company-and-role.md)                                    | Both calls        |
| `reg_task_view_preference`            | [Grid or list](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/grid-or-list.md): `grid` or `list`                          | Both calls        |
| `industry_template_uuids`             | [Work types](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/work-types.md)                                                | With templates    |
| `notes`, `notify_snapfix_team`        | [Let us help you](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/let-us-help.md); when joining, "joining a company" and 0 | Without templates |

What the server does is in the [onboarding API](https://docs.snapfix.com/engineering-reference/api/onboarding.md). In short: it renames the user's own placeholder site, unless the typed name is already taken, in which case the site keeps its old name; it saves the view and the notes; with templates it copies each work type into the site as a group; without templates it emails the Snapfix team on every call \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)]. Joining does not add the person to an existing site: it gives them their own empty site, named after the company they said they are joining \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)].

## Actions

| Action                    | Who       | What happens                                                                                                                                                                                                                                          | API      |
| ------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| Open the screen           | Automatic | Sends the call once. Android sends nothing when offline.                                                                                                                                                                                              | As above |
| Success with templates    | Automatic | iOS stores the returned data, sets the post-setup notice ([After success](#after-success)), clears `should_create_business` and opens Home about a second later. Android wipes the local database, stores the returned data and opens the group list. |          |
| Success without templates | Automatic | iOS does the same as above. Android clears `shouldCreateBusiness`, records a join when the note is "joining a company", and opens the group list.                                                                                                     |          |
| Failure                   | Automatic | See [Failure alert](#failure-alert).                                                                                                                                                                                                                  |          |

On Android an expired session refreshes the token and sends the same call again.

## States

* **Loading:** the animation and the bar above.
* **Empty:** not used; the screen always sends a call.
* **Error:** see [Failure alert](#failure-alert).
* **No permission:** none on the screen. The server acts on the `user_uuid` in the body.
* **Offline (mobile):** iOS sends the call and shows the failure alert. Android returns before the call and shows nothing; the bar stays where it is until the person goes back.

## Dialogs and sheets

### Failure alert

An alert with no title and the server's message, or "Something went wrong. Please try again." when there is none. The message can be an internal one, such as "invalid parent data to update!".

* iOS: "Ok" sends the same call again; "Cancel" removes the saved user, clears the local data and signs out.
* Android: one button that closes the alert. There is no retry on the screen. The system back button returns to [Grid or list](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/grid-or-list.md), where "Next" sends the call again.

A second call after the server already updated the site fails with "invalid parent data to update!", because the action finds the site by a marker that the first call overwrote.

### After success

iOS only, on the group list that Home opens:

* **Started a company:** "Your Snapfix account is now ready for you." and "Start getting things done by creating your first task!", with "Start a task", "Skip for now" and a close cross. "Start a task" checks location access and opens the camera; the task then goes to [First task group](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/first-task.md). "Skip for now" and the cross close the popup.
* **Joined a company:** "Your Snapfix account is now ready for you." and "You can now be added to groups by your company or team admin using your Snapfix login.", with "Go to my snapfix", "Share login with admin" and a close cross. "Share login with admin" opens the share sheet with "Hi, I registered for Snapfix. You can now add me to a Snapfix group using ", where the login is the email when it is verified, otherwise the phone when it is verified.

iOS also applies the grid-or-list choice to the task view of every group in the list.

Android shows none of these. Its start-a-task sheet (`SnapfixFirstTaskDialog`) has no callers, and the call that would show a joined-company dialog is commented out (`BusinessListingActivity.java:813-814`) \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)]. The grid-or-list choice stays only as the phone's default view.

## Platform differences

| Topic         | iOS                                  | Android                                                                                                                      |
| ------------- | ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| After success | Home, then a popup on the group list | The group list, no popup \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)] |
| Failure       | "Ok" retries, "Cancel" signs out     | One button; back to retry                                                                                                    |
| Offline       | The failure alert                    | Nothing sent, nothing shown                                                                                                  |
| Progress      | Full in about five seconds           | 1 a second with templates; 0 then 100 without                                                                                |


---

# 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/onboarding/configuring.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.
