Organisation settings

Use this editor to view and change the profile, custom fields, modules and connections of an organisation in your group. It is the full-screen dialog you open from the organisations list; the settings themselves are explained row by row on Organisation.

One shared editor

The fullscreen dialog and the Organisation page (Configurations > Organisation) are two shells around the same editor — the dialog opens on top of the organisations list, while the page edits the organisation or group you currently have selected. Either way you work with identical tabs and fields.

The dialog is opened from the organisations list — use the eye icon to edit an organisation of your group, or select one row and use Clone selected organisation to copy it as a starting point for a new one.

The editor has three tabs: Profile, Modules and Fields. The dialog always shows the full editor of an organisation, also when you open the group's own row from the list. To edit the connections the group shares with its organisations, select the group and open Configurations > Organisation: for a group, that page shows only the shared connections, because module switches are set per organisation. A green Save button and a help button sit in the toolbar; the close button (Any changes will be discarded), pressing Escape or trying to leave with unsaved changes prompts you to confirm before discarding. Without the right to change the configuration, every field is read-only.

Profile

The Profile tab holds the organisation's identity and presentation:

• Name — required, up to 20 characters, with a live character counter.
• Telephone — entered with a country-code selector.
• Addresses — the organisation's postal addresses, kept as a list with add, edit and delete.

Below these, the Profile tab shows:

• Texts — multi-language text blocks used in client-facing content. Which language rows appear is driven by the Languages selection below.
• Images — upload a logo, profile image and pan (banner) image.
• Languages — a multi-select of the languages this organisation supports, shown as chips. Default language is a single select limited to the languages you selected; removing the current default from Languages makes the first remaining language the new default. A previously stored language that is no longer in the list is still shown as selected.
• Attributes — a table of the organisation's general settings under the headings Locale, Calendar, Finance, Booking and Audit — among them currency, country, time zone, working days and VAT rates. Settings owned by a module are not in this table — they are edited under that module's switch on the Modules tab. Numeric rows only accept values within their allowed range and clamp what you type to it.
• Tags — free-form tags for grouping and filtering.
• A delete icon at the bottom right of the tab deletes the organisation when you save; it arms at once, without a confirmation, and clicking it again unmarks it. It appears only for an organisation of a group, never on the group's own row, only with Manage for Organisation or Configuration & settings on that organisation, and not in a clone. What a deletion does is described under Saving and permissions.

Fields

The Fields tab chooses which custom fields the dashboard shows for this organisation, and in which order. Choose an entity at the top — Client, Journal or Appointment — then tick Use field for the fields to show and drag them into order; with none ticked, all are shown. The definitions themselves are edited under Configurations > Templates, see Template fields.

Modules

The Modules tab combines the module switches with each module's own settings and connections.

The modules are, in this order:

• Payments
• Wallets
• Vouchers
• Products
• Promotions
• Feedback forms
• SMS
• Video
• Weather
• Treatments
• Sessions
• Aggregate resources
• Emails
• Waitlist

What each switch shows or hides, in the dashboard and on the booking site, is listed on Organisation. There is no module for recording client data and none for water temperature.

Wallets, Vouchers, Products and Promotions require Payments: they are disabled and shown as off while Payments is off, and while disabled they show a Requires payments hint. Turning Payments off also switches all four off; switch them on again after turning Payments back on.

Where a module has settings of its own, they appear as a small attribute table directly beneath its switch — the refund and desk-payment rules under Payments, voucher validity under Vouchers, wallet credit expiry and the wallet adjustment limit under Wallets, discount stacking and the default early-access lead under Promotions, the credentials under SMS and Video, and the location coordinates under Weather. The tables stay visible while a module is off; their values take effect only while it is on. The waitlist itself has no settings here: how long a waitlisted client may claim a freed place is the booking template's Waitlist promotion timeout (min), see Edit a booking template.

The connections sit directly beneath their module switch:

• Payments — a Payment provider dropdown, shown while Payments is on. It offers Saferpay, the only provider connected to checkout. Use the pencil button next to it to open its credentials in a separate dialog — Customer ID, Terminal ID, API username, API password (with show/hide) and URL. Clearing the dropdown removes the configured provider. How to check the setup without a real charge is described in Payments: provider and checks.
• Twilio SMS (under SMS) — Account SID, Auth token, Sender and From number for outgoing text messages.
• Twilio Video (under Video) — Account SID, API key and API secret for video appointments.

The secrets among these — the SMS Auth token, the video API secret and the payment API password — are stored once and never shown again: a saved value appears as a row of dots with the hint Stored — type a new value to replace it, or clear it and a clear button. Leave it as it is to keep the current value, type to replace it, or clear it to remove it.

A Use group integration settings checkbox at the top of the tab (shown for a single organisation in a group of more than one) copies the group's payment provider, SMS and video credentials down and locks the credential forms, so the organisation inherits from its group. It also takes the group's SMS and Video switches, which leaves SMS off for that organisation — see Sharing connections across a group.

Cloning an organisation

Clone selected organisation opens the editor on a copy of the selected organisation, named New organisation, with a new URL code and offline. It is offered only in a tenant with several organisations, to users with Manage for Organisation or Configuration & settings on the group. The copy takes the selected organisation's settings and module switches, but not its texts, and not its stored passwords and tokens: after saving the clone, enter the payment API password, the SMS Auth token and the video API secret again, or tick Use group integration settings. Until the clone has been saved and synchronised, those fields may still read Stored.

Saving creates the copy as a new organisation of your group, with its own email templates, header, footer and signature and the standard fields. Everyone who holds Organisation: Manage on the group receives the rights of an organisation administrator on it; if you created it with Configuration & settings alone, you receive the rights you hold on the group. Give other colleagues their rights on it in the user dialog. Nobody is signed out. The new organisation has no booking template yet: create one under Configurations > Templates before you share its booking site.

Saving and permissions

The toolbar Save button stays disabled until you make a valid change — the editor compares against the original state and only enables saving once something has actually changed, the name is not empty and work days are present. Saving is also blocked while a synchronisation is in progress. After saving, the dialog closes and the organisations list reloads.

A change is written to the local store on this device and then synchronised. Credentials changed on the group (through Configurations > Organisation with the group selected) are passed on to every organisation that uses the group integration settings.

With the delete icon armed, Save deletes the organisation at once instead of saving your other changes; this needs a connection. go flow refuses the deletion, and the dialog stays open with the reason, for the group itself ("The group itself cannot be deleted.") and while the organisation has bookings that are not over ("This organisation still has … booking(s) that are not over. It can be deleted once they are over or cancelled."). When go flow cannot be reached, it shows "The organisation could not be deleted. Please check your connection and try again." After a deletion:

• The organisation disappears from the dashboard on every device. Colleagues lose their rights on it; nobody is signed out.
• Its clients, bookings, orders and history are kept.
• Its booking site answers that it cannot be found, and booking pages still open in a browser stop working.
• go flow sends nothing new for it — no no-show emails, follow-ups, waitlist offers or new reminders — but completes what is owed: refunds and their notices for cancellations already made, the expiry of open reservations and receipts for paid orders. Messages already waiting to go out are sent.

To confirm that a change arrived, follow Check after changing.