> 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/console/site-details.md).

# Site details

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

**Site admins** keep their **site**'s name, image, address and country up to date. They choose whether members' email addresses or phone numbers show next to their names, and they switch the **Snapfix Recommends** task field suggestions on or off, optionally limited to the site's own tags. Only the web sets the site's default currency. It is the first tab of the web **Site Console**; in the apps every member can open it from the side menu, read-only unless they are a site admin. In the **Multi-Site Console** the same form edits any site of the multi-site where the user is a site admin.

## Rules

### Who can change it

* Only site admins change the details. On the web, the Site Console admits role "Admin" and group admins; group admins see every field disabled, with no "Save". Anyone else goes to `/fix`. The guard checks the site stored as current, not the site in the address ([Site details](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md)).
* In the apps every member opens the screen; only site admins can change it ([Site details](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#ios-and-android)).
* The web's save needs a site admin; a blocked site admin still passes ([`PUT /v1/app/parents/{uuid}`](https://docs.snapfix.com/engineering-reference/api/console.md#put-v1appparentsuuid)). The iOS address and image saves check no membership at all.

### Fields

* The site name is required and cannot be only spaces. The web and Android stop at 60 characters; iOS sets no limit, and neither does the server ([Inputs](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#inputs)).
* The web saves a name that another live site already uses; the apps' save refuses it with "account name already exists". Whether names must be unique is open \[[ASK-125](https://github.com/snapfix/docs/blob/main/ASK.md#ask-125-must-site-names-be-unique)] ([`webcust_update_parent_v2`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionwebcust_update_parent_v2)).
* The country is required on the web only. The web's list has no empty choice ([Inputs](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#inputs)).
* Address lines hold up to 100 characters each, postal code up to 10, city and county up to 60 on the web ([Inputs](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#inputs)).
* The default currency is one of the currencies marked as Snapfix-supported. Only the web shows and saves it: iOS hides its currency row and sends none, and Android has no field ([Platform differences](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#platform-differences)).
* "Display contact info" is off for a new site. When on, the apps and the web show members' email address or phone number next to their name. The server returns members' contact details whatever the switch says \[[ASK-133](https://github.com/snapfix/docs/blob/main/ASK.md#ask-133-should-the-server-hide-members-contact-details-when-display-contact-info-is-off)] ([`webcust_parent_detail`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionwebcust_parent_detail)).
* The suggestion switch shows only where the site may use AI suggestions. On the web that is every site outside production, and in production the sites that Firebase Remote Config allows (all sites, or a list). The apps use the same Remote Config values in every environment ([Site details](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#web), [Snapfix Recommends](https://docs.snapfix.com/product/features/ai/snapfix-recommends.md)).
* "Restrict to My Tags" shows only while suggestions are on, and turning suggestions off turns it off. When on, the web says suggestions "will only include tags you have created" (`aiUseOnlyExistingTag`) ([Inputs](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#inputs)).
* The image is cropped before it is saved: freely on the web, to a square on Android, and to a square of 600 by 600 pixels on iOS ([Platform differences](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#platform-differences); web\_app\_v2 @ 0989b8e685, `dropzone.component.html:49`).

### Saving

* The web sends the whole form in one request with "Save". The answer becomes the stored current site, which reports the user's tag and checklist permissions as off until the site list reloads ([Actions](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#web-1)).
* The apps have no "Save": leaving the screen saves what changed. iOS saves in turn the image, then the name, contact display and AI switches, then the address; Android saves the image, then everything else in one call ([Actions](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#ios-and-android)).
* The web, iOS and Android each save the address through a different call, so they can store it differently ([`webcust_update_parent_v2`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionwebcust_update_parent_v2)).
* Every web save adds a new address row, even when the address did not change. Readers take the newest, and the old rows stay ([`PUT /v1/app/parents/{uuid}`](https://docs.snapfix.com/engineering-reference/api/console.md#put-v1appparentsuuid)).
* In the apps the screen lists the site's admins. The data behind it holds every member's sign-in email and phone, and any member can read it \[[ASK-133](https://github.com/snapfix/docs/blob/main/ASK.md#ask-133-should-the-server-hide-members-contact-details-when-display-contact-info-is-off)] ([`webcust_parent_detail`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionwebcust_parent_detail)).

## Flow

```mermaid
flowchart TD
    open["Open Site Details"] --> platform{"Platform"}
    platform -- web --> role{"Role on the current site"}
    role -- "Admin" --> edit["Edit the form"]
    edit --> save["Save: one request, the answer becomes the stored site"]
    role -- "group admin" --> readonly["Form disabled, no Save"]
    role -- other --> fix["Sent to /fix"]
    platform -- "iOS or Android" --> member["Every member sees the form"]
    member --> appadmin{"Site admin?"}
    appadmin -- yes --> appedit["Edit the fields"]
    appedit --> leave["Leaving the screen saves the changes"]
    appadmin -- no --> locked["Fields locked"]
```

## Platforms

| Capability                      | Web                                                                                                    | iOS                                                  | Android                                               |
| ------------------------------- | ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------- | ----------------------------------------------------- |
| Open the page                   | Role "Admin" and group admins                                                                          | Every member, "Site Administration" > "Site Details" | Every member; site admins under "Site Administration" |
| Change it                       | Role "Admin", with "Save"                                                                              | Site admins, saved on leaving                        | Site admins, saved on leaving                         |
| Site name limit                 | 60                                                                                                     | None                                                 | 60                                                    |
| Country required                | Yes                                                                                                    | No                                                   | No                                                    |
| Default currency                | Yes                                                                                                    | No (row hidden)                                      | No                                                    |
| Contact display and AI switches | Yes                                                                                                    | Yes                                                  | Yes                                                   |
| Image crop                      | Free                                                                                                   | Square, 600 by 600                                   | Square                                                |
| Admins list                     | No (see [Site users](https://docs.snapfix.com/product/features/console/site-users.md))                 | Below the form                                       | "Account Admin" below the form                        |
| Edit any site of a multi-site   | Yes, see [Multi-Site Console](https://docs.snapfix.com/product/features/console/multi-site-console.md) | No                                                   | No                                                    |

## Screens

* [Site details](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md): web, iOS and Android.
* [Site details (multi-site)](https://docs.snapfix.com/how-the-apps-work/screens/console/multi-site-details.md): the same form for a multi-site's sites, on the web.

## API and data

* [`GET /v1/app/parents/{uuid}`](https://docs.snapfix.com/engineering-reference/api/console.md#get-v1appparentsuuid) and [`PUT /v1/app/parents/{uuid}`](https://docs.snapfix.com/engineering-reference/api/console.md#put-v1appparentsuuid): the web reads and saves the site. The read checks no membership.
* [`webcust_parent_detail`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionwebcust_parent_detail): the apps read the site and its admins.
* [`webcust_update_parent_v2`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionwebcust_update_parent_v2): the apps save the name, contact display and AI switches, and Android also the address.
* [`update_parent_image`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionupdate_parent_image): the apps save the image. [`update_parent_address_basic`](https://docs.snapfix.com/engineering-reference/api/console.md#post-actionupdate_parent_address_basic): iOS saves the address.
* The country and currency lists: [Reference API](https://docs.snapfix.com/engineering-reference/api/reference.md).
* Tables: [`tPri_Parent`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_parent.md) (the site), [`tPri_Address`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_address.md) and [`tPri_ParentAddress`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_parentaddress.md) (its addresses), [`tPri_SettingsParent`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_settingsparent.md) (the AI switches) and [`time_tPri_Parent`](https://docs.snapfix.com/engineering-reference/db/tables/time_tpri_parent.md) (the log of site changes).

## Depends on

* [Switching sites](https://docs.snapfix.com/product/features/groups/site-switching.md): the form edits the site stored as current, and the site switcher's "Site Console" button opens it.
* [Snapfix Recommends](https://docs.snapfix.com/product/features/ai/snapfix-recommends.md): the AI suggestion switches.
* [Site tags](https://docs.snapfix.com/product/features/console/site-tags.md): the tags that "Restrict to My Tags" keeps to.
* [Site users](https://docs.snapfix.com/product/features/console/site-users.md): the site admins, and the Users tab beside this one.
* [Multi-Site Console](https://docs.snapfix.com/product/features/console/multi-site-console.md): the same form for each site of a multi-site.
* [Username logins](https://docs.snapfix.com/product/features/console/username-logins.md), [Rooms and areas](https://docs.snapfix.com/product/features/rooms/rooms-and-areas.md), [Checklist templates](https://docs.snapfix.com/product/features/checklists/checklist-templates.md) and [Subscriptions](https://docs.snapfix.com/product/features/billing/subscriptions.md): the other tabs of the Site Console.

## Edge cases

* **Blank name:** the web keeps "Save" off; iOS shows "Please enter account name" in an alert, and Android under the field ([Inputs](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#inputs)).
* **Failed saves:** the web shows the API's message. A failed iOS address save leaves "Updating..." on screen, and a failed Android image upload leaves its "Updating..." dialog open ([States](https://docs.snapfix.com/how-the-apps-work/screens/console/site-details.md#states)).
* **Offline (apps):** iOS keeps the changes on the phone and calls the server on leaving, with no connection check. Android asks to retry; its "Cancel" closes the screen and drops the changes without a warning.
* **iOS "Delete account":** the code has a menu with "Delete account", but its button is hidden and the sheet's delete calls an empty function.
* **Several sites:** each save changes one site. In the Multi-Site Console the sites reload after a save ([Site details (multi-site)](https://docs.snapfix.com/how-the-apps-work/screens/console/multi-site-details.md#actions)).
* **Country list:** "Congo" and "Korea" each appear twice, and accented names sort last.


---

# 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/console/site-details.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.
