> 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/staff/customer-admin.md).

# Customer administration

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

**Customer administration** is the set of tools in the [staff admin app](https://docs.snapfix.com/product/features/staff/staff-admin.md) with which Snapfix staff change a customer's data directly. Staff find a **site** (the admin app calls it an **account**, and its help texts sometimes a "business") and set its details, **customer type**, dates and **site admins**. They link sites to **organizations**, which hold the customer's HubSpot, Stripe and Xero records. They manage a site's **groups**, the **group members** and their permissions, upload groups, schedules, tasks, assets, checklists, tags and members in bulk, find any user to change their details or password, move a task to another group, and set up a new site with its admin, users and groups in one form. The roles these tools set are the customer's own: see [Site users](https://docs.snapfix.com/product/features/console/site-users.md) and [Group members](https://docs.snapfix.com/product/features/groups/group-members.md).

## Rules

### Who can use the tools

* No page checks a role beyond the admin app's session, and no page is limited to listed staff ([Staff admin app](https://docs.snapfix.com/product/features/staff/staff-admin.md#rules)).
* On the server, the organization routes and the site create check the staff flag. Most other calls behind these pages, php-apis actions and apipy routes, check only that the caller is signed in, so any signed-in Snapfix user could make them. Among them: changing or deleting any site, adding any account to any group with any rights, setting any user's password, moving any task and onboarding a site for any email address or phone number ([php-apis actions](https://docs.snapfix.com/engineering-reference/api/staff.md#php-apis-actions)).
* Pages that work on one site pick it with the shared account picker, which also lists deleted sites; a page opened with a site's name in its address picks the first site whose name matches, which may be another site ([Account picker](https://docs.snapfix.com/how-the-apps-work/screens/staff.md#account-picker)).

### Sites

* The Account page lists every site, paged on the server, 10 rows at a time by default, with a name search and a customer type filter ([Account](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md)).
* Adding a site needs a name, an address, a country, a time zone and a customer type, which starts at "Uncategorised". Editing needs the name, address, time zone and type, and adds three dates: the customer type change date, the first invoice date and the next renewal date. The name is not checked for duplicates \[[ASK-125](https://github.com/snapfix/docs/blob/main/ASK.md#ask-125-must-site-names-be-unique)] ([Add Account and Edit Account](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#add-account-and-edit-account)).
* The customer types are "Customer", "Sales Trial", "Churn", "Test", "Investor / Pro Bono" and "Uncategorised". The edit dialog's help text names types the form does not use, and the table shows stored types under other names.
* The type matters beyond reports: an "Uncategorised" or "Churn" site can change task statuses only while it holds 100 tasks or fewer ([Subscriptions](https://docs.snapfix.com/product/features/billing/subscriptions.md)), and only such a site can buy the iOS per-user plan ([In-app purchase](https://docs.snapfix.com/product/features/billing/in-app-purchase.md)) (api\_php\_live\_v2 @ ef3c4319f6, `app/Http/Controllers/v1/Versions/v1_0/App/ParentController.php:60`, `:233-235`; ios @ aa31967ac8, `SnapFix/IAPPlanVC.swift:203-209`).
* The Account page warns about live paying sites with a gap: no email key, no email key admin, no first invoice date, no site admin, no renewal date, or a renewal date that has passed. The counts are read once, when the page opens ([Account](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#layout)).
* A site made on the Account page gets no admin. The page says an "Account Superadmin" must be added before a payment link is sent; nothing enforces it \[[ASK-212](https://github.com/snapfix/docs/blob/main/ASK.md#ask-212-what-is-an-account-superadmin-and-should-a-payment-link-wait-until-the-site-has-one)].
* In "Business User(s)" staff move a site's users between "Admin User(s)" and "Normal User(s)", or mark them deleted. An admin must be an existing Snapfix user, and the site always keeps one live admin: the last one cannot be moved or deleted ([Business User(s)](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#business-users)).
* Deleting a site is a box in the edit dialog, behind a question, and meant for sites made in error. A deleted site stays in the list, marked, and opens read-only ([Add Account and Edit Account](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#add-account-and-edit-account)).
* The site's Guestline login is stored from the Account page: "Save" tests the login with Guestline first, and the password is typed on every save because the saved one is never shown. The Guestline service can turn stored passwords back into plain text ([Guestline Detail](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#guestline-detail), [PMS integrations](https://docs.snapfix.com/product/features/integrations/pms-integrations.md)).
* The task creation email service is set per site, with an email key and an existing user as the admin of what the service creates. The server refuses a key that another site already has, with "email\_key exists" ([Task Creation Email Service](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#task-creation-email-service)).
* "View Graphs" shows the task chat messages created each day in the site's groups over 10 to 90 days, against the same number of days just before; the labels call them sales ([View Graphs](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md#view-graphs)).

### Organizations

* An organization groups sites and holds at most one HubSpot, one Stripe and one Xero record. A record belongs to one organization only: the server refuses a second link with "The account ID is already connected to another organization." ([Organization mapping](https://docs.snapfix.com/how-the-apps-work/screens/staff/org-mapping.md), [`connect-account`](https://docs.snapfix.com/engineering-reference/api/staff.md#put-v1adminorganizationsuuidconnect-account)).
* Staff link by dragging on the mapping board: a site or a record onto an organization, or a record onto a site. A linked site or record cannot be dragged again, and an organization that already has a record of that kind refuses another with " connection found" ([Organization mapping](https://docs.snapfix.com/how-the-apps-work/screens/staff/org-mapping.md#actions)).
* The site create and update routes refuse an organization that another site uses, but the connect route lets several sites share one, and staging data has organizations with many sites. Which rule is meant is open \[[ASK-204](https://github.com/snapfix/docs/blob/main/ASK.md#ask-204-should-an-organization-have-one-site-or-several)].
* Deleting an organization unlinks each of its sites and soft-deletes it. Its HubSpot, Stripe and Xero links are fields of the organization, so the records themselves are not changed and show as unlinked again ([Organization details](https://docs.snapfix.com/how-the-apps-work/screens/staff/org-mapping.md#organization-details)).
* The connect routes store record IDs without checking that they exist.

### Groups

* A group belongs to one site and is a task group or an asset group (an asset register). Staff add, edit, deactivate, delete, copy and export a site's groups ([Groups](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md)).
* A group made here records the text "admin" as its creator \[[ASK-77](https://github.com/snapfix/docs/blob/main/ASK.md#ask-77-who-should-be-recorded-as-the-creator-of-groups-users-and-sites-made-through-the-staff-admin-routes)]. A deleted group stays listed, and its tasks and members are left as they are \[[ASK-80](https://github.com/snapfix/docs/blob/main/ASK.md#ask-80-what-should-deleting-a-group-do-to-its-tasks-and-members)] ([Add Group and Edit Group](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md#add-group-and-edit-group)).
* "Copy Group Details" copies a group's users, schedules and settings, as chosen, into other groups of the site; the chosen member, or else the source group's admin, becomes the copy's admin ([Copy Group Details to Other](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md#copy-group-details-to-other)).
* "Create Random Tasks" makes 1 to 10 real tasks in a live task group, as a member staff pick, with no confirmation \[[ASK-221](https://github.com/snapfix/docs/blob/main/ASK.md#ask-221-should-create-random-tasks-be-offered-for-live-customer-groups)]. The server takes any count and the creator from the request ([Create Random Tasks](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md#create-random-tasks)).

### Bulk uploads

* Every upload is checked in the browser first, and "Upload" stays off while the review has an error or a repeated entry ([Groups](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md#dialogs-and-sheets), [Group users](https://docs.snapfix.com/how-the-apps-work/screens/staff/group-users.md#dialogs-and-sheets)).
* Row limits in the browser: 100 groups per CSV, 150 schedules per workbook and 100 users per CSV. The multi-group user upload has no row limit, in the browser or on the server.
* The uploads cover groups, schedules (which the server creates in the groups the file names, whatever site is picked), tasks with checklists, assets with attributes, tags, a checklist for one task, users for one group, and users for several groups ([Groups](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md), [Group users](https://docs.snapfix.com/how-the-apps-work/screens/staff/group-users.md)).
* In the task upload, the checklist sheets are never checked, and a checklist sheet after an empty one gives the later tasks the wrong checklist. In the asset upload, removing a row misaligns the attributes.
* In the multi-group user upload, a `groups` cell that names no known group adds the user to every group of the type, and blank phone numbers are sent as 0. Its passwords are stored in clear in the server's request log, and it saves row by row with no transaction, so a large sheet can stop part way with some users saved.
* A tag folder marked "Delete" in the tag upload soft-deletes every tag of the folder; the folder stays ([Upload Tags](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md#upload-tags)).

### Group members

* Staff look a person up by email, staff username or mobile number with "Check User". A new person is created with a generated 10-character password shown on screen; an existing person joins with the chosen role and permissions. A failed check is treated as "no such person" ([Add User](https://docs.snapfix.com/how-the-apps-work/screens/staff/group-users.md#add-user-and-edit-user-group-permission)).
* A membership is "Admin" or "User" with fifteen permissions; a new member starts as "Admin" with "View All Tasks", "Create New Tasks", "Access Document" and "Assign User" on \[[ASK-219](https://github.com/snapfix/docs/blob/main/ASK.md#ask-219-should-a-member-added-in-the-admin-app-start-as-admin)] ([Add User](https://docs.snapfix.com/how-the-apps-work/screens/staff/group-users.md#add-user-and-edit-user-group-permission)).
* Adding a new person also gives them a normal membership of the group's site when they have none; an existing person added to a group gets no site membership ([`admin_save_user`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_save_user)).
* "Users Permissions" sets permissions for many members of one type at once. Changes made on the other type are dropped with no warning, and "Apply to All Users" copies a row to every member but saves only the ticked rows ([Users Permissions](https://docs.snapfix.com/how-the-apps-work/screens/staff/group-users.md#users-permissions)).

### Users

* The Users page searches every Snapfix user. Staff change a user's names, address, user type ("Normal", "Snapfix" or "Snapfix Test"), verified and developer flags, and deleted flag, and see the user's sites and groups with each role \[[ASK-222](https://github.com/snapfix/docs/blob/main/ASK.md#ask-222-what-are-the-snapfix-user-types-for-and-who-may-set-them-and-the-verified-flags)] ([Users](https://docs.snapfix.com/how-the-apps-work/screens/staff/users.md)).
* A search that matches nothing keeps showing the previous rows, whose buttons then act on those users.
* "Reset password" sets a new password at once, as typed or generated, with no rule, and the server writes it into a log. The dialog is shared with Group users ([Reset Password](https://docs.snapfix.com/how-the-apps-work/screens/staff/users.md#reset-password)).
* "Temp Password" creates a password for one sign-in within 10 minutes, copies it to the clipboard and shows it. Only this action checks that the caller is staff. The generator is not cryptographic ([Users](https://docs.snapfix.com/how-the-apps-work/screens/staff/users.md#actions)).

### Task move

* Staff pick a user, a site and two of the user's groups in it, and drag a task from one to the other ([Task move](https://docs.snapfix.com/how-the-apps-work/screens/staff/task-move.md)).
* The server checks the move first. A missing tag folder stops it; missing tags or people open a confirmation whose "Move users" and "Move tags" boxes start ticked, and the move goes ahead even with both cleared \[[ASK-220](https://github.com/snapfix/docs/blob/main/ASK.md#ask-220-should-a-task-move-go-ahead-when-neither-box-is-ticked)] ([Move confirmation](https://docs.snapfix.com/how-the-apps-work/screens/staff/task-move.md#move-confirmation)).
* The move copies the task into the target group under a new ID, with no sub-status, and marks the original deleted, with "admin" as who deleted it ([`migrate_job_v1`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionmigrate_job_v1)).
* The user picker leaves out users who have no legacy name.

### Onboarding a new site

* "Onboard" creates a site, its account admin, its other users and its groups in a three-step form sent as one request. The site's name and address need at least 4 characters, and a live site's name is refused; each user needs a first and last name, a password and an email or a mobile number; each group needs a name and an admin from the form, and can start from a template ([Onboard account](https://docs.snapfix.com/how-the-apps-work/screens/staff/onboard.md)).
* The form also goes ahead with no group at all \[[ASK-199](https://github.com/snapfix/docs/blob/main/ASK.md#ask-199-should-onboarding-require-at-least-one-group)].
* The site gets the customer type `admin_quick_onboard`, which the type list does not offer \[[ASK-200](https://github.com/snapfix/docs/blob/main/ASK.md#ask-200-which-customer-type-should-a-site-made-by-onboard-have)]. It starts in the Europe/Dublin time zone whatever zone was chosen.
* Only the account admin gets a site membership; the other users get only their group memberships.
* A failed request keeps the form's entries, but can leave a half-built site that blocks a retry.
* A new customer can also be set up from a HubSpot deal, through the setup link ([Billing setup](https://docs.snapfix.com/product/features/staff/staff-billing.md), [Setup form](https://docs.snapfix.com/product/features/onboarding/setup-form.md)).

## Flow

```mermaid
flowchart TD
  find["Account: find the site"] --> what{"What to change"}
  what -- "details, type, dates" --> edit["Edit Account: save or delete"]
  what -- "admins" --> admins["Business User(s): keep one admin"]
  what -- "links" --> org["Organization mapping: drag to link records and sites"]
  what -- "groups" --> groups["Groups: add, edit, copy, export, upload"]
  groups --> members["Group users: check, add, permissions, upload"]
  members --> users["Users: details, password, temporary password"]
  what -- "a task" --> move["Task move: check, confirm, copy and delete the original"]
  newcust["New customer"] --> onboard["Onboard: site, users and groups in one request"]
  onboard --> find
```

## Platforms

| Capability                                             | Web                   | iOS | Android |
| ------------------------------------------------------ | --------------------- | --- | ------- |
| Sites, customer types, dates and admins                | Yes, in the admin app | No  | No      |
| Organizations and their HubSpot, Stripe and Xero links | Yes, in the admin app | No  | No      |
| Groups and bulk uploads                                | Yes, in the admin app | No  | No      |
| Group members and permissions                          | Yes, in the admin app | No  | No      |
| Users, passwords and temporary passwords               | Yes, in the admin app | No  | No      |
| Task move                                              | Yes, in the admin app | No  | No      |
| Onboarding a new site                                  | Yes, in the admin app | No  | No      |

## Screens

* [Account](https://docs.snapfix.com/how-the-apps-work/screens/staff/accounts.md): the sites, with their details, graph, admins, Guestline login and email service.
* [Organization mapping](https://docs.snapfix.com/how-the-apps-work/screens/staff/org-mapping.md): organizations and their links to sites and records.
* [Groups](https://docs.snapfix.com/how-the-apps-work/screens/staff/groups.md): a site's groups and the bulk uploads.
* [Group users](https://docs.snapfix.com/how-the-apps-work/screens/staff/group-users.md): a group's members, permissions and user uploads.
* [Users](https://docs.snapfix.com/how-the-apps-work/screens/staff/users.md): every user, with details, passwords and groups.
* [Task move](https://docs.snapfix.com/how-the-apps-work/screens/staff/task-move.md): moving a task between two of a user's groups.
* [Onboard account](https://docs.snapfix.com/how-the-apps-work/screens/staff/onboard.md): the three-step form for a new site.

## API and data

* Sites: [`GET /v4/parents`](https://docs.snapfix.com/engineering-reference/api/staff.md#get-v4parents) (the list and the picker), [`POST /v1/admin/parents`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-v1adminparents) (add), [`admin_modify_parent`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_modify_parent) (edit, delete, email service), [`admin_list_parent_user`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_list_parent_user) and [`admin_save_parent_user`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_save_parent_user) (admins), [`kpi_job_chats_created_day`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionkpi_job_chats_created_day) (the graph).
* Guestline: [`admin_read_gl_parent`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_read_gl_parent), [`admin_guestline_login`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_guestline_login) and [`admin_modify_gl_parent`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_modify_gl_parent).
* Organizations: [`GET /v1/admin/organizations`](https://docs.snapfix.com/engineering-reference/api/staff.md#get-v1adminorganizations) and the other `/v1/admin/organizations` routes, with [`connect-organization`](https://docs.snapfix.com/engineering-reference/api/staff.md#put-v1adminparentsuuidconnect-organization) and [`disconnect-organization`](https://docs.snapfix.com/engineering-reference/api/staff.md#put-v1adminparentsuuiddisconnect-organization) for sites.
* Groups: [`admin_read_pri_business`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_read_pri_business), [`POST /group`](https://docs.snapfix.com/engineering-reference/api/groups.md#post-group), [`modify_pri_business`](https://docs.snapfix.com/engineering-reference/api/groups.md#post-actionmodify_pri_business), [`POST /copy-group-data`](https://docs.snapfix.com/engineering-reference/api/groups.md#post-copy-group-data) and [`POST /v4/random-jobs`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-v4random-jobs).
* Bulk uploads: [`admin_create_businesses_v2`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_create_businesses_v2), [`POST /schedule-upload`](https://docs.snapfix.com/engineering-reference/api/planner.md#post-schedule-upload), [`admin_create_jobs`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_create_jobs), [`admin_create_assets`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_create_assets), [`admin_create_checklist`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_create_checklist), [`admin_read_jobs`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_read_jobs), [`admin_read_group_tag_settings`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_read_group_tag_settings), [`admin_update_group_tag_settings`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_update_group_tag_settings), [`admin_save_users`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_save_users) and [`POST /v1/admin/user-relations/multiple`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-v1adminuser-relationsmultiple).
* Members: [`admin_read_pri_user_business_v2`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_read_pri_user_business_v2), [`admin_check_user`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_check_user), [`admin_save_user`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_save_user) and [`PUT /v1/admin/user-relations/multiple`](https://docs.snapfix.com/engineering-reference/api/staff.md#put-v1adminuser-relationsmultiple); a membership edit uses `save_pri_user_business_v2` in the [Users API](https://docs.snapfix.com/engineering-reference/api/users.md).
* Users: [`GET /v4/users`](https://docs.snapfix.com/engineering-reference/api/staff.md#get-v4users), [`admin_reset_user_password`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_reset_user_password) and [`create_temp_password`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actioncreate_temp_password); the user edit uses `save_pri_user_v7` in the [Users API](https://docs.snapfix.com/engineering-reference/api/users.md).
* Task move: [`webcust_list_jobs`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-actionwebcust_list_jobs), [`migrate_job_v1_validate`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionmigrate_job_v1_validate) and [`migrate_job_v1`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionmigrate_job_v1).
* Onboarding: [`admin_onboard_parent`](https://docs.snapfix.com/engineering-reference/api/staff.md#post-actionadmin_onboard_parent) and [`webcust_list_templates_jwt`](https://docs.snapfix.com/engineering-reference/api/onboarding.md#post-actionwebcust_list_templates_jwt).
* Tables: [`tPri_Parent`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_parent.md) (sites, with the customer type and dates), [`tPri_Org`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_org.md) with [`tPri_Org_Hubspot`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_org_hubspot.md), [`tPri_Org_Stripe`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_org_stripe.md) and [`tPri_Org_Xero`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_org_xero.md), [`tPri_Business`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_business.md) (groups), [`tPri_UserParent`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userparent.md) (site memberships), [`tPri_UserBusiness`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userbusiness.md) (group memberships and permissions), [`tPri_User`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_user.md), [`tPri_UserHashSalt`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userhashsalt.md) and [`tPri_UserHashSalt_Temporary`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userhashsalt_temporary.md) (passwords), and [`tPri_Job`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_job.md) (tasks).

## Depends on

* [Staff admin app](https://docs.snapfix.com/product/features/staff/staff-admin.md): the sign-in, the menu and the account picker.
* [Site details](https://docs.snapfix.com/product/features/console/site-details.md), [Site users](https://docs.snapfix.com/product/features/console/site-users.md), [Groups](https://docs.snapfix.com/product/features/groups/groups.md) and [Group members](https://docs.snapfix.com/product/features/groups/group-members.md): the customer's own versions of what staff change here.
* [Tasks](https://docs.snapfix.com/product/features/tasks/tasks.md), [Planned tasks](https://docs.snapfix.com/product/features/planner/planned-tasks.md), [Checklists](https://docs.snapfix.com/product/features/checklists/checklists.md), [Asset registers](https://docs.snapfix.com/product/features/assets/asset-registers.md) and [Site tags](https://docs.snapfix.com/product/features/console/site-tags.md): what the uploads and the task move create.
* [Subscriptions](https://docs.snapfix.com/product/features/billing/subscriptions.md) and [In-app purchase](https://docs.snapfix.com/product/features/billing/in-app-purchase.md): what the customer type changes.
* [Billing setup](https://docs.snapfix.com/product/features/staff/staff-billing.md), [Payment links](https://docs.snapfix.com/product/features/billing/payment-links.md) and [Setup form](https://docs.snapfix.com/product/features/onboarding/setup-form.md): the payment side and the setup link of a site.
* [PMS integrations](https://docs.snapfix.com/product/features/integrations/pms-integrations.md): the Guestline login stored per site.
* [Sign-in](https://docs.snapfix.com/product/features/account/sign-in.md) and [Password reset](https://docs.snapfix.com/product/features/account/password-reset.md): how a user signs in with a reset or temporary password.
* [Username logins](https://docs.snapfix.com/product/features/console/username-logins.md): the "Staff Username" a user may have, made in the customer's Site Console.
* Outside services: HubSpot, Stripe and Xero hold the records that organizations link to.

## Edge cases

* **Deleted items:** deleted sites stay listed and read-only and can still be picked \[[ASK-223](https://github.com/snapfix/docs/blob/main/ASK.md#ask-223-should-deleted-accounts-be-selectable-for-card-payments-and-support-logs)]; deleted groups keep their tasks and members \[[ASK-80](https://github.com/snapfix/docs/blob/main/ASK.md#ask-80-what-should-deleting-a-group-do-to-its-tasks-and-members)]; the task move lists no archived tasks.
* **Two sites with one name:** pages opened by name pick the first match.
* **Failed organization links:** the board can say "Success" after a failed link, and "Create connection" can stop half way, leaving a new organization half linked.
* **Names in dialogs:** site, organization and record names go into HTML strings in the mapping dialogs; Angular strips scripts, so only markup gets through.
* **Failed lists:** most lists show no message, so a failed load looks empty.
* **Several sites:** each page works on one site at a time; the group and member pickers list only that site's groups.
* **Time zones:** a site added on the Account page takes the chosen zone; a site made by Onboard does not.
* **Offline:** not applicable; the admin app is web only.


---

# 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/staff/customer-admin.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.
