Settings·General Settings

General Settings

Organization-wide preferences covering tour visibility, scheduling, time slots, integrations, and check-in restrictions.

Tour Visibility

Hours before tour becomes visible

Controls how far in advance guides can see all organization tours. Outside this window, guides only see tours they are personally assigned to.

0 hoursGuides always see only their assigned tours.
24 hoursGuides see all tours starting within the next 24 hours, plus their assigned tours at any time.

Guides to only see own tours

When enabled, guides can only see tours they are assigned to via Schedule. When disabled, guides can see all organization tours.

Guides being able to see Booking Platforms

When enabled, guides can see which platform each booking came from. When disabled, platform information is hidden from guides.

Show combined pax count

When enabled, adults and children are shown as a single total number. When disabled, they are shown separately (e.g. 10 + 3).

Count children in capacity

When enabled, children are included when calculating open slots and overcapacity. When disabled, only adults count toward capacity.

Enable income recording

When enabled, guides can record tour income after completing a tour. When disabled, the Record Income button is hidden from guides.

Schedule

Auto Assign

Automatically assign guides to tours based on their availability in Schedule. The system balances workload, respects rest days, and considers guide preferences.

Auto-Assignment Parameters

Parameter

Description

Minimum break between tours (hours)

Minimum time required between consecutive tours for a guide.

Maximum tours per day

Maximum number of tours a guide can be assigned to in a single day.

Preferred max working days

Soft limit — guides prefer not to exceed this, but can if needed.

Maximum working days per week

Hard limit — guides cannot be assigned beyond this number of days per week.

Underutilization threshold

Show a warning if a guide works this number of days or fewer in a week.

User-Specific Settings

Override auto-assignment parameters for individual guides. Any guide without a personal override will fall back to the organization defaults above.

Time Slots

Configure the time blocks guides use when submitting availability. A maximum of 8 time slots are allowed.

Name

Start Time

End Time

Morning08:0012:00
Afternoon12:0017:00
Evening17:0022:00

Example time slot configuration.

Integrations

Third-party integrations — coming soon

Booking Check-In

Restrict Check-In Time for Guides

When enabled, guides can only mark bookings as checked-in within a specified time window after the tour has started. Once that window closes, the check-in action is no longer available to guides.

Payment Schedule

Configure automatic creation of payment records for all guides. When enabled, the system calculates what each guide owes (or is owed) for the completed period and creates the corresponding records automatically.

Enable automatic schedule

Toggle to turn automatic calculation on or off. When disabled, payment records can only be created manually via the Calculate button in the Payments section. Saving with the toggle off clears any saved schedule.

Periodicity

WeeklyRecords are created once a week. The day of the week is taken from the start date.
Bi-weeklyRecords are created every two weeks on the same weekday as the start date.
MonthlyRecords are created on the 1st of each month and cover the entire previous calendar month.

Start date

For Weekly and Bi-weekly — sets the anchor date and determines the weekday the schedule runs on (e.g. selecting a Friday means the schedule always runs on Fridays). For Monthly — only the month matters; the date is automatically set to the 1st.

Time

The hour at which the calculation triggers. The time is in UTC — European organizations are typically UTC+1 (winter) or UTC+2 (summer), so set the hour 1–2 hours earlier than your intended local time.

How it works

The cron job runs every hour and checks whether it is time to calculate for your organization.

When triggered, it calculates the last completed period — for example, running on Monday calculates the previous week (Monday to Sunday). Monthly runs on the 1st and covers the entire previous calendar month.

If records for that period already exist, the run is skipped automatically — no duplicates are created.