Preferences
Fine-tune platform behavior to match your team's operational workflows. These settings control default views, validation rules, ticket scheduling, and what tenants can do in the Tenant Portal.
Default Management
These settings control the default behavior of the Bookings module and the data your team is required to capture.
Default Booking Dashboard View
| Setting | Description |
|---|---|
| Default Booking Dashboard View | Choose whether the Bookings module opens on the List view or the Timeline view by default. Set this to whichever view your team uses most frequently. |
When to choose each view:
- List view — Best for teams that primarily search, filter, and sort bookings by tenant name, status, debt, or platform. Ideal for finance-oriented teams focused on collections and payment tracking.
- Timeline view — Best for operations teams that need a visual overview of occupancy across units. Ideal for spotting booking gaps, planning turnovers, and managing availability.
Individual team members can always switch between views manually — this setting only controls which view loads first.
Mandatory Booking Fields
| Setting | Description |
|---|---|
| Mandatory Booking Fields | Define which fields are required when creating a new booking. Fields marked as mandatory will show a validation error if left empty during booking creation. |
Common fields to make mandatory and why:
| Field | Why Make It Mandatory |
|---|---|
| Tenant Email | Required for sending automated emails (onboarding, check-in, check-out, payment reminders). Without it, the tenant receives no communications. |
| Tenant Phone | Essential for last-minute coordination on check-in day and for emergency contact during the stay. |
| Tenant Fiscal ID | Required in many jurisdictions for legally compliant invoicing. Making it mandatory ensures your team captures it upfront rather than chasing it later. |
| Tenant Nationality | Useful for reporting, compliance with local rental regulations, and segmenting your tenant base. Required in some jurisdictions for rental declarations. |
Start with a minimal set of mandatory fields and add more as your team identifies gaps. Making too many fields mandatory can slow down booking creation, especially for urgent or short-notice reservations.
Tickets Priorities
Set the default deadline (in days) for each priority level. When a ticket is created at a given priority, the system automatically calculates the due date by adding these days to the creation date.
| Priority | Example Default Deadline |
|---|---|
| Critical | 1 day |
| High | 3 days |
| Medium | 7 days |
| Low | 14 days |
These are defaults only — individual tickets can always have their due date overridden manually when created or edited.
How Priority Deadlines Work in Practice
When a team member creates a ticket and selects High priority, the system automatically sets the due date to 3 days from today (using the example defaults above). The assignee sees this deadline in their ticket list in the Operations module, and the ticket appears as overdue if not resolved by that date.
Your cleaning team lead creates a "Pre-arrival deep clean" ticket on Monday with High priority. With a 3-day default, the due date is automatically set to Thursday. If the team member knows the check-in is actually on Wednesday, they can manually override the due date to Tuesday to allow buffer time.
Align your priority deadlines with your team's actual response capacity. If your maintenance team cannot realistically respond to a "Critical" ticket in 1 day, set it to 2 days — an unrealistic deadline that is consistently missed is less useful than an achievable one.
Default Tenant Portal
Configure how the Tenant Portal behaves for tenants. These are account-wide toggles that apply to all tenants across all properties.
| Setting | Description |
|---|---|
| Allow Tenants to Edit Fiscal ID | When enabled, tenants can update their own fiscal/tax ID number in the Tenant Portal. Disable this if you need to control fiscal data entry (e.g., to prevent tenants from entering incorrect tax information that affects invoices). |
| Allow Online Payments | Master toggle for online payment functionality in the Tenant Portal. Note that individual properties also have their own "Property Payments Active" toggle — both must be enabled for a tenant to make an online payment. |
| Allow to see services | When enabled, tenants can view the services catalogue and submit service requests in the Tenant Portal. Disable this to hide the Services offering from tenants. |
Impact of Each Setting
Allow Tenants to Edit Fiscal ID
- Enabled: Reduces back-and-forth — tenants enter their own tax ID, saving your team data-entry time. Useful when fiscal IDs are not needed for invoicing at booking creation and can be captured later.
- Disabled: Ensures data accuracy — your team controls all fiscal data. Recommended if your invoicing provider (e.g., Invoice-xpress) requires validated fiscal IDs and incorrect entries would cause invoice errors.
Allow Online Payments
- Enabled: Tenants can pay rent, deposits, and fees directly through the portal. This is the fastest way to collect payments and reduces the need for manual payment recording.
- Disabled: Use this if you handle all payments through bank transfers or another external system and do not want tenants to attempt online payments.
The Allow Online Payments setting here is the master toggle. Even when enabled, individual properties can disable payments via the "Property Payments Active" toggle in each property's Payments tab. Both must be on for a tenant to pay online.
Key Rules
-
View preferences are account-wide. The default booking view (List or Timeline) applies to all team members. Individual members can switch views manually but will return to the default on their next session.
-
Mandatory fields block booking creation. If a field is marked as mandatory, the booking cannot be saved without it — even for bookings imported from external platforms. Be cautious about making fields mandatory that external platforms may not provide.
-
Priority deadlines are defaults, not enforced limits. The system sets the due date automatically based on the priority, but any team member can override it. Use these as guidelines, not hard constraints.
-
Online payments require two toggles. The master toggle here and the per-property toggle must both be enabled. Disabling the master toggle here immediately blocks online payments for all properties, regardless of their individual settings.
Related
- Tenant Portal — Full documentation of the tenant-facing interface
- Operations > Tickets — Where ticket priority deadlines apply
- Bookings Module — Where mandatory fields and default view settings take effect
- Listings > Payments Tab — Per-property "Property Payments Active" toggle
- Interface Language — Language selection from the header dropdown, My Profile, or Preferences, and localization scope