Organisation

The organisation page is a three-tab editor for everything specific to one organisation: its public profile, its custom data fields, and its product modules together with their third-party connections. All three tabs share a single Save button in the top toolbar — your edits across every tab are written together when you save.

For a guided first setup, follow Set up your organisation. Which settings live here and which live on the booking template, a resource or a single session is explained in What is set where.

Overview

The page opens from Configurations > Organisation in the menu (you need the right to read the configuration; without the right to change it, every field is read-only). It edits whichever organisation you currently have selected — when your group is selected, you edit the group itself. A toolbar across the top holds the three tabs — Profile, Modules and Fields — and the green save button on the right. The save button stays disabled until you have an actual change to write, and saving pauses while a synchronisation is running; if you navigate away with unsaved edits, you are asked to confirm before they are discarded.

When a group is being edited, the Profile tab shows only the name, telephone and addresses, and the Modules tab shows only the shared connections (payment provider, SMS and video credentials), because module switches and the other settings are set per organisation rather than on the group.

Profile tab

The Profile tab holds the organisation's core details:

• Name — required, up to 20 characters.
• Telephone — entered with a country code.
• Addresses — the organisation's postal addresses, managed as a small list with add, edit and delete.

For individual (non-group) organisations the Profile tab also shows:

• Texts — short descriptive texts maintained per supported language.
• Images — uploads for the logo, profile and pan image types. See Add images and promotional video for where images appear.
• Languages and Default language — pickers just above the Attributes table. Languages is a multi-select: pick every language your organisation works in, shown as chips. Default language is limited to the languages you picked in Languages; if you deselect the language currently set as default, the first remaining selected language becomes the default automatically. A previously stored language that is no longer in the list is still shown as selected so it is not silently dropped.
• Attributes — a table of the organisation's general settings, one row per setting, under the headings Locale (currency, country, time zone), Calendar (first day of week, week rule, work days), Finance (VAT rates), Booking (group membership field) and Audit. Settings that belong to a module are not in this table: they sit on the Modules tab underneath their module switch. This page does not set treatment, session or product prices. Every row is explained in the attributes reference below.
• Tags — free-form tags for the organisation.
• A delete button deletes the organisation when you save. Selecting it arms it at once, without asking: the icon becomes a filled, warning-coloured bin, and selecting it again unmarks it. It is offered only in the editor you open from the organisations list, only for an organisation of a group — never on the group's own row — and only with Manage for Organisation or Configuration & settings on that organisation. The deletion needs a connection and is refused while the organisation has bookings that are not over; what it does is described in Organisation settings.

Work days must keep at least one day: with none selected, the save button stays disabled.

Fields tab

The Fields tab chooses which custom fields the dashboard shows for this organisation, and in which order, one entity at a time. A selector at the top chooses the entity — Client, Journal or Appointment — and the table lists that entity's fields: tick Use field for each field the dashboard should show, and drag the rows into order. While no field of an entity is ticked, the dashboard shows all of them. The field definitions themselves are created and edited on the Fields tab of Configurations > Templates — see Template fields; this tab only selects among them.

Modules tab

The Modules tab turns product features on and off for this organisation. Directly beneath each switch sit that module's own settings: a small table where the module has settings of its own, and — for Payments — the Payment provider row. For a group, no switches are shown, only the shared connection sections.

A module's settings table stays beneath its switch whether the module is on or off, so you can fill it in before you switch the module on; the values take effect only while the module is on. The Payment provider row is the exception: it is shown only while Payments is on. Switching a module off hides its pages elsewhere in the dashboard; the stored values and records are kept and return when the module is switched back on.

Wallets, Vouchers, Products and Promotions require Payments: while Payments is off they are disabled and show a Requires payments hint. Turning Payments off also switches these four off; when you turn Payments back on, switch each of them on again.

The switches, in the order the tab shows them:

Switch	Its settings	In the dashboard	On the booking site
Payments	Payment provider, Allowed refund destinations, Allow paying at the desk	Finance menu (Payments, Orders), price and VAT rows on resources, treatments and products, desk payments	Off: no prices are charged — every booking is taken without payment.
Wallets	Wallet credit expiry (days), Max wallet adjustment	Finance > Wallets	Wallet credit can be used and topped up.
Vouchers	Voucher validity (days)	Finance > Vouchers	Vouchers can be redeemed: the checkout's code field — for voucher and promo codes — is shown only while Vouchers is on. Whether voucher products are offered for sale follows Products.
Products	—	Configurations > Products	Voucher products are offered for sale. Wallet top-up products follow Wallets instead and stay on sale while Wallets is on.
Promotions	Allow discount stacking, Default early-access lead (minutes)	Configurations > Promotions	Automatic early-bird and last-minute prices apply; promo codes too, while Vouchers is also on.
Feedback forms	—	Configurations > Feedback forms, Analytics > Feedback insights	Clients receive and fill in feedback forms.
SMS	Twilio SMS credentials	SMS reminder switches on resources, SMS templates	SMS reminders are sent. Off by default. Switching it off stops reminders for bookings made from then on; reminders already scheduled for earlier bookings are still sent.
Video	Twilio Video credentials	The video option on treatments and availability, once all three credentials are stored	Video appointments can be booked.
Weather	Latitude, Longitude, Altitude (m)	—	A short forecast appears in the booking calendar.
Treatments	—	Configurations > Treatments (while the organisation has provider resources, or no resources yet)	No effect.
Sessions	—	The Sessions tab and button on the Resources page, session generation in the scheduler	No effect: existing session resources stay bookable.
Aggregate resources	—	The Aggregators tab and button on the Resources page	No effect.
Emails	—	The Emails menu (list of sent emails)	No effect: emails are still sent.
Waitlist	—	The waitlist switch on session resources, waitlist counts in the scheduler, the waitlist email template	No effect: a session resource whose waitlist was switched on keeps offering it.

Settings that are often looked for here but belong to the booking template — Client accounts, Reservation timeout (how long a place is held during checkout), Waitlist promotion timeout (min) (how long a waitlisted client has to claim a freed place) and OTP code length (the sign-in code emailed to clients) — are edited on Edit a booking template. There is no module for recording client data: the Clients and Journal menus depend only on the user's rights.

Payments: provider and checks

go flow takes online payments through Saferpay, the only provider connected to checkout. The Payment provider dropdown under Payments offers Saferpay only.

1. Switch Payments on and choose Saferpay in Payment provider.
2. Select the pencil icon (Edit) next to it. A dialog titled Saferpay opens with Customer ID, Terminal ID, API username, API password (with a show/hide toggle) and URL. Enter the values from your Saferpay account. For URL, enter Saferpay's address exactly, ending in /api/: https://www.saferpay.com/api/ for live payments, https://test.saferpay.com/api/ for a Saferpay test account.
3. Select the green tick (Done). It is enabled once every field holds a value; it accepts the details but does not save them. The Close button instead puts the previous values back.
4. Save the organisation with the toolbar button.

Clearing the dropdown removes the provider and its details: customers can then no longer pay online. To restore it, choose Saferpay again and enter every value again.

Payment methods. go flow does not choose the payment methods. The Saferpay payment page shows the methods activated on your Saferpay terminal — for example TWINT, Visa or Mastercard. To offer another method, have it activated on the terminal with Saferpay.

Check the setup without a real charge. A saved form does not prove that Saferpay accepts your details; go flow has no test button. After saving and synchronising:

1. On your booking site, book a paid session or treatment and continue to payment.
2. The Saferpay payment page should open with your amount and the payment methods your terminal offers. Reaching this page proves that the customer ID, terminal, API user, password and URL work.
3. Leave the payment page without paying (cancel it, or go back). Nothing is charged. The booking site reports that the payment did not go through, the place is released when its hold runs out, and the attempt shows as a Failed row on Payments — that row is expected.

If the booking site shows an error instead of the Saferpay page, the details or the URL are wrong or incomplete: open the dialog, re-enter them, save and try again. If Saferpay has given you a test account, you can also complete a payment with Saferpay's test cards while its credentials and the test URL are entered — do this only before your booking site is in use, because every customer payment goes to the test account during that time, and note that a completed test payment creates a real order and receipt in go flow. Then enter the live credentials and the live URL. What the payment states mean and how to check a payment afterwards is explained in Review orders and payments.

Credentials are write-only. The API password — like the SMS Auth token and the video API secret — is stored once and never shown again. A stored 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 at the end of the field. Leave the field as it is to keep the current value, type to replace it, or use the clear button to remove it; the change is written when you save the organisation.

Refund destinations

Allowed refund destinations limits where refunds may go: Card (payment provider), Wallet or Voucher. An empty list allows all three. go flow checks every refund against this list when it is made — refunds you make when cancelling a booking in the dashboard and the automatic refunds for customers who cancel online themselves. Those automatic refunds always go to the client's wallet: if you fill in the list without Wallet, a customer who cancels online is cancelled without a refund. Leave the list empty, or include Wallet, while customers may cancel online.

Both cancel dialogs offer only the destinations in this list (all three when it is empty), besides No refund. How refunds work when you cancel is described in Cancel or refund.

Connections

go flow connects to the outside services below. Each is set up on the Modules tab — of the organisation, or of the group when several organisations share one account. go flow does not synchronise with external calendars: the Outlook/Exchange calendar sync was retired and there is no Google calendar option.

Service	What you enter	What go flow exchanges	How to tell it is ready
Online payments (Saferpay)	Customer ID, Terminal ID, API username, API password, URL under Payments	The amount, currency, order reference and the customer's name, email and billing address go to Saferpay; Saferpay returns whether the payment was captured.	A test booking reaches the Saferpay payment page (see above).
SMS reminders (Twilio)	Account SID, Auth token, Sender, From number under SMS	The client's mobile number and the reminder text.	Once SMS is on and all four values are stored, every resource shows its SMS reminder switches; a reminder for your own test booking reaches your phone.
Video appointments (Twilio Video)	Account SID, API key, API secret under Video	Video rooms for video appointments: two participants, no recording.	Once all three are stored, the video option appears on treatments and availability. See Run video appointments.
Weather forecast	Latitude, Longitude, Altitude (m) under Weather — no account needed	The site's coordinates go to a public forecast service (MET Norway).	The booking calendar shows a forecast for the coming days. Nothing is shown while both coordinates are 0.

Disconnecting has these effects: clearing the payment provider stops online payments, and go flow can then neither confirm open payments with Saferpay nor refund to card — keep valid credentials while payments made with them can still be refunded. Switching SMS off, or clearing one of its four values, stops SMS reminders from being scheduled from then on; a reminder already scheduled for an earlier booking is still sent, with the credentials stored when it was scheduled, unless that client's bookings change before it is due. Clearing a video value removes the video option.

Sharing connections across a group

When your group has more than one organisation, the Modules tab of an organisation starts with a Use group integration settings checkbox. Ticking it copies the group's payment provider, SMS and video credentials into the organisation and locks those fields, so all organisations share one set; the stored passwords and tokens are copied by go flow when you save. Saving credential changes on the group passes them on to every organisation that uses the group settings.

The checkbox also takes the group's SMS and Video switches. The group editor has no module switches, so after ticking the checkbox SMS reads as off for the organisation and returns to off on every save. An organisation that must send SMS reminders keeps its own SMS credentials, with the checkbox unticked.

When a change takes effect

Most organisation settings are read at the moment they are used. A change therefore applies from the next booking, payment or message on — including for bookings made earlier — unless a value was copied onto a record when that record was created.

Setting	A change applies to
Currency	New prices, orders and payments. Existing orders, payments and vouchers keep the currency they were made in.
VAT rates	Only the list of rates offered on resources, sessions and products. Each resource and product keeps the rate chosen on it, and existing orders keep their VAT.
Time zone	Already generated sessions and existing bookings keep their moment in time, so their clock times shift by the difference between the old and the new zone. Set the time zone before you generate sessions.
Languages, Default language	The booking site and messages from then on.
Country	The date, time and amount format of emails sent from then on, the default dial code and country of new entries, and the law cited in erasures and data exports from then on.
Module switches	Immediately; switching a module off hides it but keeps its data. With Payments off, bookings made from then on are not charged.
Allow paying at the desk	Checkouts from then on. Bookings already made to pay at the desk stay open until the desk records the payment.
Allowed refund destinations	Every refund made from then on, also for earlier bookings.
Allow discount stacking	Checkouts from then on.
Default early-access lead (minutes)	Only early-access tiers added afterwards; it pre-fills a new tier in the generate dialog and in the session dialog. Tiers already saved on sessions keep their lead.
Voucher validity (days)	Vouchers sold or issued afterwards. Existing vouchers keep their expiry date.
Wallet credit expiry (days)	Credit added afterwards. Existing credit keeps its expiry date.
Max wallet adjustment	Manual adjustments made from then on.
Latitude, Longitude, Altitude (m)	The next forecast.
Payment provider, SMS and video credentials	The next payment or video appointment — including confirmations of open payments and card refunds. SMS reminders use the credentials stored when they were scheduled: reminders already scheduled for earlier bookings keep the old ones.
Audit settings	See Audit settings.

Check after changing

1. Save. The cloud icon in the top bar turns while go flow synchronises and then shows a tick. If it shows an exclamation mark, your change is stored on this device only: once you are online again, select the icon to synchronise. If the message Sync failed, please check your connectivity! appears with a setting name and a reason in brackets, the change was refused: correct that value and save again.
2. Reload the page and confirm that the values are what you entered.
3. Check what customers see: open your booking site in a private browser window and look at what the change should affect — prices and currency, offered languages, the payment page, the forecast. Get ready to take bookings lists the checks on the customer site.

Attributes reference

Every organisation attribute, wherever it is edited: Languages and Default language are dedicated pickers above the Attributes table on the Profile tab, the rest of the general rows sit in that table, and the module rows sit in the small tables under their module's switch on the Modules tab.

General settings (Profile tab)

Setting	What it does
Name	The organisation's name.
URL code	The organisation's identifier in booking and public URLs. Set when the organisation is created; this page has no field for it.
Public	The organisation's online flag, set with the online and offline actions on the organisations list. The booking site does not read it.
Tags	Free-form tags for the organisation, used to filter and group it in lists.
Languages	The languages your organisation works in, picked from a multi-select list of languages. They decide which languages you maintain texts and email content in, and which languages the booking site offers to clients.
Default language	The language used when no better choice is known — for example for a client who has not picked one. Limited to the languages selected in Languages.
Currency	The currency of all prices, orders, refunds and documents. Default CHF. Without a currency no desk payment can be recorded.
Country	The organisation's country, picked with the flag selector. It sets the format of dates, times and amounts in the emails go flow sends (for example 28.06.2026, 14:51 and 1'234.50 for Switzerland), and it is the default country for telephone numbers and addresses in the dashboard and at checkout. It also decides which data-protection law go flow cites when you erase a client or export a client's data: the GDPR for a country of the EU or EEA, the Swiss FADP for Switzerland, none elsewhere.
Time zone	The organisation's time zone. All appointment times, slots and reminder schedules are interpreted in it.
First day of week	Which weekday the dashboard's scheduler and date pickers start the week on.
First week of year rule	How week numbers are counted in the scheduler: from the year's first day, from its first four-day week, or from its first full week.
Work days	Your working days, shown as the default working week in the scheduler. At least one day is required.
VAT rates	Comma-separated list of VAT rates as decimal fractions (0.081 = 8.1%). These are the choices offered as the VAT rate on resources, sessions and products.
Addresses	The organisation's postal addresses, managed as a small list with add, edit and delete.
Telephone	The organisation's telephone number, entered with a country code.
Group membership field	Designates the client custom field whose options stand for your member groups. Group-restricted sessions and member early access check the client's value in this field when the client books; empty = no group gating anywhere.
Use group fields settings	On: a member organisation uses its group's custom field definitions instead of its own. This page has no control for it.
Use group integration settings	On: a member organisation takes the payment provider, the SMS and video credentials and the SMS and Video switches from its group on every save, instead of keeping its own. See Sharing connections across a group.

Audit settings (Profile tab)

The audit settings decide what is recorded about your organisation's records, on top of the platform's own security log. They are off by default and visible to your team only. Under the health care profile, record history and read logging stay on and records are kept for 120 months: choosing the profile sets these values, and a save that lowers any of them is refused.

Setting	What it does
Keep record history	On: every previous version of your organisation's records is kept, so a change can be reviewed and a record restored. Off (default): no history is kept.
Audit retention (months)	How long record history and access entries are kept, from 12 to 120 months (default 24). The audit log's other categories (sign-in, data, money and administration) keep their own period of 13 months whatever this says.
Log who reads client data	On: opening a client is recorded, and the client fields set to Logged when opened are loaded when the client is opened instead of arriving with the client list. Off (default): reads are not recorded, and such fields work like any other field. Fields set to Always logged are protected whatever this says.
Audit profile	Standard (default) leaves the three settings above to you. Health care, for care providers, switches record history and read logging on and fixes the retention at 120 months while it is set.

Payments

Setting	What it does
Allowed refund destinations	Which refund destinations you permit: Card (payment provider), Wallet or Voucher. Every refund is checked against this list; empty = all destinations allowed. Customer self-cancellations always refund to the wallet, so keep Wallet in a list you fill in. See Refund destinations. Payments module.
Allow paying at the desk	On: a client booking sessions or appointments online may choose to pay at the desk instead of online. The booking is confirmed at once with nothing paid, an unpaid order is written for each participant at checkout, and the amount stays open on the participant until the desk deals with it through Take payment in the session's participant list: taking the amount due settles the order, taking a different amount voids it and records a new order for what was taken, and Waive voids it — see Unpaid desk orders. Offered only for a cart of sessions with an amount due and no voucher or wallet credit applied. Off (default): every booking is paid online. Payments module.
Payment provider	The payment provider handling checkout — Saferpay — together with its credentials, edited in its own dialog. See Payments: provider and checks.

Promotions

Setting	What it does
Allow discount stacking	On: a promo code typed at checkout applies on top of the automatic early-bird and last-minute prices. Off (default): the cart's automatic savings are compared with the code's discount and only the larger applies; on a tie the automatic price wins. See Combining discounts. Promotions module.
Default early-access lead (minutes)	The default head start, in minutes, that members get when you generate early-access sessions — pre-filled into each new early-access tier in the generate dialog and in the session dialog; tiers already saved keep their own lead. From 0 to 525600 minutes; a value typed outside that range is clamped as you type. Promotions module.

Vouchers and Wallets

Setting	What it does
Voucher validity (days)	How many days a newly sold or issued voucher stays valid, unless the product sets its own validity. From 1 to 3650 days (default 365); a value typed outside that range is clamped as you type. Vouchers module.
Wallet credit expiry (days)	How many days newly added wallet credit stays valid. From 0 to 3650 days (default 365), where 0 means the credit never expires; a value typed outside that range is clamped as you type. When a credit expires, only the part of it not yet spent lapses (see Wallets). Wallets module.
Max wallet adjustment	The largest amount a single manual wallet adjustment may add or remove, in your currency (default 1000). A manual adjustment above this is refused, so a mistyped figure cannot move a large sum in one step. 0 means no limit of your own, leaving only the technical maximum. A debit is additionally limited by the client's own balance: a wallet can never be taken below zero. There is no limit on a wallet's balance. Wallets module.

Weather

Setting	What it does
Latitude	The site's latitude, used by the weather forecast. From -90 to 90; a value typed outside that range is clamped as you type. Weather module.
Longitude	The site's longitude, used by the weather forecast. From -180 to 180; a value typed outside that range is clamped as you type. Weather module.
Altitude (m)	The site's altitude in metres, read together with the coordinates for the weather forecast. From -500 to 9000; a value typed outside that range is clamped as you type. Weather module.

SMS credentials

Appointment-reminder SMS are sent with your own Twilio account, configured under SMS on the Modules tab. All four values must be filled in — with any of them missing, no SMS is sent. These are organisation-level settings; there are no per-resource SMS credentials. The Auth token is write-only, like every stored secret (see Payments: provider and checks).

Setting	What it does
Account SID	The Twilio account identifier.
Auth token	The Twilio auth token belonging to the account.
Sender	The alphanumeric sender name tried first on each SMS, up to 10 characters.
From number	The sender phone number (digits only, up to 12) used as the fallback when the alphanumeric sender is not accepted.

Video credentials

Credentials for the Video module, entered under Video on the Modules tab — they connect your Twilio Video account for video appointments. All three values must be filled in before you can set up a video appointment type; with any of them missing, the video option stays unavailable elsewhere in the dashboard. The API secret is write-only.

Setting	What it does
Account SID	The Twilio account identifier.
API key	The Twilio Video API key.
API secret	The secret belonging to the API key.

Saving changes

Every tab feeds the one Save button in the toolbar, so a single save commits all your changes together. The button stays disabled until there is something to save; with the delete button armed (Profile tab, in the editor opened from the organisations list), saving deletes the organisation instead. If you try to leave the page with unsaved edits, you are prompted to discard them first. After saving, follow Check after changing.