Mini user manual

Complete setup

1. Open Mini in account context with complete property access.
2. Set the registration/invitation sender email and sender name.
3. Set the owner rate plan code and optional owner service filter.
4. Configure Finnish and English terms links and upload the owner-portal logo when needed.
5. Subscribe to reservation webhooks and verify readiness.
6. Review owner mappings and test with one owner before inviting everyone.
7. Reopen Onboarding or Settings to maintain the configuration.

Mini administration uses account-wide context. Owners see the mapped portal scope rather than the administration view.

Invite an owner

1. Open the owner invitation panel from Mini.
2. Enter the owner’s email, first name and required last name; remove duplicate email entries.
3. Check the Mini sender address and owner portal URL, then send the invitations.
4. Review each result. Use the offered copy-link option only for the intended owner.
5. The owner follows their setup link to complete account/password setup and signs in at the portal.

Troubleshoot registration

1. If invitation sending is blocked, check sender settings, owner portal URL and the highlighted owner details.
2. Check email delivery and the exact invited address if the owner cannot find the invitation.
3. Confirm the owner has the correct property/unit mapping after registration.

Registration does not by itself establish the owner’s unit entitlement. Review access mappings separately.

Review an owner mapping

1. Open owner access management and find the owner by name or email.
2. If a new owner is not listed, invite/register them first, then return to their owner record. New records start without unit access; an invitation does not grant a property or unit.
3. Inspect the properties, units and status in the mapping row; expand the row when columns are hidden on a small screen.
4. Open the access editor and assign only the properties and units that belong to that owner.
5. Save, then test the portal as the intended owner.
6. Use the offered status/access controls when an owner’s entitlement changes and verify the saved result.

Check both property and unit choices. A similarly named unit in another property is not the same entitlement.

Transfer a unit after an ownership change

1. Open the old owner’s saved mapping and explicitly remove the sold unit, retaining any other units they still own; save and verify the result.
2. Invite/register the new owner if needed, then grant only the intended property/unit and save.
3. Test both owners’ portal views. Granting the new owner access does not automatically revoke the previous owner’s access.
4. Review existing reservation visibility separately. There is no automatic ownership-history or booking-transfer transaction.

Use the owner portal

1. Sign in at the owner portal and choose the available calendar or reservations view.
2. Choose the property/unit and date filters offered for your mapped scope.
3. Open a reservation to review its dates, status and available details.
4. Use the folio/breakdown view where offered to inspect charges and totals.
5. Use the language control when you need another supported portal language.

Understand visibility

1. The default reservation visibility includes confirmed stays and eligible in-house stays.
2. Use the past/checked-out option when offered to inspect completed stays.
3. If a reservation is missing, check mapped units, filters and status before contacting support.

Personal guest details can be masked by the account’s guest-data policy even when the owner can see a reservation.

Configure owner rates

1. Set up an appropriate Apaleo owner rate plan for the relevant unit groups.
2. Enter its code in Mini settings. A dedicated code such as OWNER makes the setup easier to review.
3. Configure the optional owner service filter when owner bookings should include specific services.
4. Test availability and the resulting reservation before rolling out the flow.

Book or change a stay

1. In the owner portal, choose the new-booking action and an authorized unit/date range.
2. Review the available owner offer, occupants and services and submit the booking.
3. For an existing eligible owner reservation, open its details and use the offered amendment or cancellation action.
4. Review the changed dates, availability, price/service implications and confirmation before saving.
5. Refresh the calendar/list and verify the result.

The normal portal identifies owner reservations by the configured owner rate-plan ID code and account within the mapped-unit scope; it is not a per-person creator-ownership rule.

The normal UI offers editing for Confirmed owner reservations whose departure is not in the past. Cancellation is offered for Confirmed owner reservations. These UI criteria are not a configurable permission matrix for each booking.

Extend a stay when added nights may be occupied

1. Open the eligible reservation’s amendment action, change departure and wait for the added-night availability check.
2. If the original unit is unavailable, the editor can look for a mapped alternative in the same unit group with sufficient capacity and request explicit consent to attempt a move.
3. If no suitable alternative is available, choose other dates or contact the property; do not treat the extension as an occupancy override.
4. After saving, refresh the reservation and verify the final dates and assigned unit. Alternative-unit consent does not by itself guarantee that the displayed alternative was assigned.
5. If an operation reports a partial failure or unit-assignment warning, inspect the current reservation before retrying.

Who this setting controls

1. ownerGuestDataMode controls owners viewing guest data in the Mini owner portal. It is not a staff or reception access-control policy.
2. If the aim is to limit reception staff, summary-only in Mini does not do that. Staff permissions must be configured in the relevant staff workflow; do not test a staff restriction by changing the owner policy.
3. An administrator saves the policy, but the restricted viewer is the owner. Opening a reservation does not turn an owner-only policy into a staff policy.
4. MSG form questions, collected fields and staff access are configured separately. This Mini owner policy does not change what MSG forms collect.

Set the policy

1. Open Mini settings as an authorized administrator.
2. Choose the owner guest-data mode: full data after normal sign-in, password-verified temporary reveal, or summary only.
3. Save the policy and test the portal with an owner account.

Use a reveal prompt

1. In password-reveal mode, use the reveal action and re-enter the owner account password in the dedicated prompt.
2. Check the stated temporary visibility period and close/hide sensitive information when finished.
3. In summary-only mode, personal data cannot be revealed; request help from the responsible property contact when needed.

This policy masks guest data in the Mini owner portal. It does not configure reception staff permissions or the fields collected by MSG forms; configure those workflows and access rights separately.

Opening a reservation does not bypass summary-only masking or grant a passport editor. Do not treat the owner privacy setting as permission to reveal or edit identity documents.

A mode name containing MFA does not mean the interface asks for a separate SMS code: the current reveal prompt verifies the owner’s account password. Never send that password to support chat.

Check the configuration

1. For sign-in/invitation issues, verify the invited email, setup link result and sender settings.
2. For missing units or reservations, inspect the owner mapping, filters and default status visibility.
3. For missing personal details, check the configured guest-data mode.
4. For unavailable owner offers, check the owner rate plan code, unit-group coverage, dates and Apaleo availability.
5. For booking changes, inspect the eligibility message and whether the reservation is an authorized owner booking.
6. Send support the account, owner identifier/email through the appropriate support channel, unit/reservation ID, workflow and error.