Account, team, and permissions
Check the team's time-based workflows
Verify how Holidario interprets operational times before coordinating Canary Islands or multi-timezone rentals.
- I manage my own rentals
- I own or administer an agency
- I manage operations
- Owner
- Agency
On this page
Holidario uses Europe/Madrid as its default operational timezone and provides no team-, office-, or property-specific selector. This check does not correct that boundary: it establishes what the team can operate safely and where it needs a manual rule.
Prepare a controlled check#
- 1 Prepare a safe case Use a rental and non-sensitive case with known local time; never an active stay as the first experiment.
- 2 Test each workflow Calendar, agenda, messages, cleaning, keys, alerts, and channels are checked separately.
- 3 Record the comparison Keep displayed time, local time, temporary rule, owner, and evidence without sending anything real.
- 4 Decide whether to use it Classify each result as accepted, operable with a manual rule, or unverified.
- 5 Recheck seasonal changes Repeat when daylight-saving changes could affect a critical workflow.
- Choose a rental and a test reservation or non-sensitive case with known arrival and departure times.
- Record the property's timezone and expected local time.
- Identify the functions the agency will actually use: calendar, Daily PMS Agenda, scheduled messages, cleaning, key handover, alerts, and channels.
- Name a front-desk or operations reviewer and, where relevant, a cleaning or maintenance reviewer to interpret the result.
- Do not use an active guest stay as the first experiment.
Run the check#
For every included function:
- open the correct team and property;
- record the time Holidario shows and where it appears;
- compare it with the expected local time;
- check any preview or scheduled notice without sending it to a real person;
- record whether the result is correct, needs manual interpretation, or could not be verified;
- repeat on a representative date after a seasonal clock change when that workflow is critical.
A match in the calendar does not prove that messages, tasks, or integrations use the same interpretation. Accept each workflow separately.
Define the operating boundary#
The check should end with a simple table: workflow, affected property or zone, displayed time, local time, temporary rule, owner, and next review date. Tell each function only the rule it needs.
Do not compensate for a difference by changing real reservation, task, or message times. Do not promise automatic conversion for a workflow that has not been tested.
When to stop onboarding#
Do not launch the affected workflow if the difference could cause an unattended arrival, incorrect access, mistimed message, missed cleaning, or unsafe channel change. Escalate with the team, property, screen or automation, date, expected local time, and observed time, without guest data.
People who only need to interpret a time should use the operational-timezone boundary, not this full administrative check.