Attributes

An Attributes table is where you configure the detailed settings of an organisation, a resource, or a booking template. This page explains what an attribute is, which things carry them, how you edit them, and — most usefully — how the attributes you set turn into what your clients see on the online booking site.

What an attribute is

An attribute is a single setting stored as a key and a value on an entity. Each table has one row per setting: the left column is the setting's name and the right column is where you change its value. The set of keys is fixed and defined by the application — you never invent new rows, you only edit the values of the rows that are there.

Because the keys are defined in code, each attribute also knows how it should be edited and what its starting value is. That is why the value column shows the right control for each setting: an on/off switch, a number box (clamped to a minimum and maximum as you type), a dropdown of fixed choices, a weekday picker (single or, for some settings, multiple weekdays shown as chips), a client-field picker (for settings that designate one of your client custom fields), a country picker with flag and dial code, a time-zone picker, or a plain text box. When an entity has never had a value saved for a row, the table shows that setting's built-in default.

Which entities carry attributes

Three kinds of thing have an Attributes table, each in a different place:

• Organisation — on the Profile tab of the organisation editor, and only for an individual organisation; the module-gated rows sit under their module switch on the Modules tab. A group container has no Attributes table of its own. See Organisation Settings — every organisation attribute is documented row by row in its attributes reference.
• Resource — in the resource editor. A standard (provider) resource and a session resource show different rows, because they do different jobs. See Resources. The full per-attribute tables are on Resource Detail, and a resource's email switches sit in their own Email notifications control below the attribute table — one switch per client-facing email.
• Booking template — on the template's Profile tab. Templates have just four attributes. See Templates; the four rows are documented on Booking Template Detail.

Settings that belong to a module — currency and VAT rates under Payments, voucher validity under Vouchers, and so on — do not appear in the organisation's main Attributes table. They live under their module switch on the Modules tab. Turning a module off hides its attribute rows but keeps their saved values, so switching the module back on restores everything exactly as it was.

Editing attributes

Open the entity, find its Attributes table, and change values in the right-hand column. Number boxes are clamped to a sensible range as you type — for example the OTP code length can only be set between 3 and 6. Nothing is written until you use the page's own Save button, which commits the whole editor together.

How module toggles affect attributes

A handful of attributes only make sense while a particular module is switched on — currency, VAT rates, a session's slot price, and a resource's cancellation fee are tied to the Payments module; a session's waitlist settings to the Waitlist module. SMS and video credentials are organisation-level settings tied to the SMS and Video modules: they are edited under their switch on the organisation's Modules tab, never on an individual resource.

While the owning module is off, those rows simply do not appear in the Attributes table — they are hidden, not deleted. Their saved values are left exactly as they were, so switching the module back on brings the same rows back with the same values, unedited.

A few rows appear conditionally on another row's value rather than on a module: a resource's Cancel timeout (hours) is only shown while Allow cancellation is on. Rows hidden this way keep their saved values too.

Cancellation fee is stored as a plain percentage: a resource's cancelFeePercent of 10 means a cancelled, paid booking is refunded minus a 10% fee (paid amount times feePercent / 100).

A worked example

Suppose you run a fitness studio and want a paid drop-in class.

1. On the organisation, set Currency to CHF.
2. On the class's session resource, set Slot price to 25 and Cancellation fee (%) to 10.
3. Make sure the Payments module is on.

With Payments on, the slot price and cancellation fee rows are visible and editable on the session resource's Attributes table, alongside currency and VAT on the organisation. If a paid booking for that class is later cancelled, the refund is calculated minus the 10% fee you set.

Now turn the organisation's Payments module off: the currency, VAT, slot price and cancellation fee rows disappear from their Attributes tables — but the 25 and 10 you entered are still saved underneath. Turn Payments back on and the same rows reappear with the same values.