ResytechResytech Docs
Activities

Copy Settings to Other Activities

How to copy agreements, check-in, payment and other settings from one activity onto many others in Resytech.

Use this guide when several activities should share a setting and you do not want to change each one by hand. You set it up on one activity, then copy it onto the others in one step. An operator with an activity per car, boat or room uses this to keep agreements, the check-in flow, deposits and the like the same everywhere.

Copying works between activities of the same location. You need permission to edit activities.

Steps

  1. Go to Activities and click Copy Settings. You can also open it from Apps > Tools > Copy Activity Settings.
  2. Under Copy from, choose the Source activity. This is the activity whose settings are copied. It is not changed.
  3. Under What to copy, tick the settings to copy. Only what you tick is changed on the other activities.
  4. Under Copy to, tick the activities that should take those settings.
    • Type in Search activities, then click Select these (the button says how many) to tick everything the search shows.
    • Use the Type filter to list only rentals or only tours, then click Select all.
  5. Click Copy to N activities, read the confirmation, and click Copy settings.

A copy cannot be undone. The page then shows Results of the last copy: how many activities were copied with nothing to report, and for the others, what was left out, kept or not saved.

Starting from an activity you just changed

In an activity's Settings, click Copy to Other Activities in the page header. The page opens with that activity as the source. If the tab you were on holds one setting (Agreements, for example), it is already ticked. Save your changes on the tab first: a copy takes what is saved.

What Each Setting Copies

Most settings replace what the other activity has. A few are more careful, so that a copy never deletes anything a booking still needs.

SettingSettings tabWhat happens on the activities you copy to
Cancellation policyGeneralThe policy text is replaced.
Page alertGeneralThe alert text and its style are replaced.
Age restrictionManifestThe minimum age is replaced. Guest limits and guest types are not copied.
Dates and timesSchedulingThe bookable dates and days, the time slots or specific times, the daily time slot overrides and the advanced script are replaced. Durations are not copied.
Booking cutoffsSchedulingThe early cutoff and the future cutoff are replaced.
Blackout datesBlackout DatesBlackout dates the activity does not have yet are added. None is ever removed. Blackouts on specific equipment are not copied.
Pricing modifiersPricingEvery modifier is replaced. A modifier for a guest type or a duration the activity does not have is left out.
AgreementsAgreementsAn agreement with the same title is updated. New ones are added. Agreements the source does not have are removed.
Check-in flowCheck-InThe stages, their requirements, automatic advancement, equipment assignment and scannable tickets are replaced, and check-in is turned on or off as on the source.
Custom fieldsCustom FieldsA field with the same label is updated. New ones are added, and the fields follow the source's order. A field the source does not have is removed, unless bookings have answers for it.
Special eventsSpecial EventsEvery special event is replaced, matched to the activity's duration of the same length. An event with no matching duration is left out.
Deposit and balancePaymentThe deposit and how the balance is collected are replaced.
Security holdPaymentThe hold amount and the extended authorization setting are replaced.
Trip protectionTrip ProtectionEvery trip protection setting is replaced, its price included. If the source never set trip protection up, it is turned off.
Facilitator rolesFacilitator RolesA role with the same name is updated (optional or not, and its group). New ones are added. A role the source does not have is disabled.
Confirmation emailCommunicationThe email text, the terms, what to bring and what the email shows are replaced.

What a copy keeps

  • Custom fields with answers. A field that bookings have answers for is never removed and never changed to another type. It stays on the activity, after the copied fields, and the results name it. Delete it on the activity itself if you no longer want it asked.
  • Facilitator roles on bookings. A role the source does not have is disabled, the same as deleting it on the activity: bookings keep the people already assigned to it. The results say how many upcoming bookings have someone in that role.
  • Blackout dates. A copy only adds blackout dates. A date you closed on one activity alone (a car in the shop) stays closed.
  • Bookings in a check-in stage. A stage with the same name on both activities keeps the bookings that are on it. A stage the source does not have is removed: bookings on it go back to the first stage, or to the second if they were already checked in, and a workflow that names that stage no longer matches. The results list each removed stage with its number of upcoming bookings.

If the source has no check-in flow, the check-in flow is not copied at all. The other activities keep theirs.

What Is Never Copied

  • The name, description, tagline, details and color
  • Durations and every price, including the pricing type and group pricing
  • Guest limits and guest types
  • Photos
  • Equipment and capacity
  • Calendar sync
  • Dynamic duration settings
  • Whether the activity is published or hidden

Taxes and fees, allowed facilitators, categories, tracked fields and info options are not copied either. Each is assigned to many activities at once on its own screen.

To make a whole new activity from an existing one, see Clone an Activity.

Tips

  • Copy to one activity first and open it to check the result. Then copy to the rest.
  • Keep one activity as the one you edit, and copy from it each time. Copying the same setting again is safe: nothing changes on an activity that already matches.
  • Match by name: agreements are matched by title, custom fields by label, facilitator roles and check-in stages by name. Rename on the source and the copy treats it as new, so the old one is removed (or kept, for a field with answers, and disabled, for a role).
  • Tick Security hold on its own, apart from Deposit and balance, when hold amounts differ from one activity to the next.
  • Waiver requirements in a copied check-in flow use the same location waivers. The waiver forms are not duplicated.

On this page