ResytechResytech Docs
Team Management

Employees & Roles

Add team members and configure their roles and permissions.

Adding Employees

  1. Click your name in the top right corner, choose Company Settings, then open the Users tab
  2. Click Add User
  3. Enter their details:
    • Email address (used for dashboard login)
    • First name and last name
    • Phone number (required) -- used for team SMS; 2FA uses a separate number the employee verifies themselves
    • User group (optional, shown once you have created a group)
    • Administrator Access, or the individual feature permissions they need (see Permissions below)
    • Default employee role for time tracking (optional)
    • Default location view and allowed locations (for multi-location businesses)

Once added, the employee gets an email with a link to choose their own password (the link works once, for 7 days, and can be sent again from the user list). To choose the password yourself, tick Set password manually when adding them: they still get an email that their account is ready, without the password. After that they can access the dashboard according to their assigned permissions. See Add a Team Member for the details.

The first time an employee signs in they are offered two-factor authentication, and the user list shows who has it (a 2FA or No 2FA badge). An administrator can make it mandatory for everyone from Company Settings > Security (click your name in the top right, then Company Settings), and can reset it for an employee who has lost their phone. See Require Two-Factor Authentication.

Permissions

Administrators and Feature Permissions

There are no preset access roles. Each team member is either an administrator or has only the feature permissions you turn on for them. You set both when you add or edit the user on Company Settings > Users.

  • Administrator Access gives full access to every feature, setting and page, and bypasses every permission check on this page. Some actions are for administrators only, such as refunding a card payment and resetting someone's two-factor authentication.
  • Without it, the user has only the permissions turned on under Feature Permissions (labeled Additional Permissions when they are in a user group). A new user starts with none, so turn on each area they need. Even clocking in needs Timesheet.

The permission list has two modes:

  • Simple shows one switch per feature. Turning a switch on gives every action for that feature, including the extra Point of Sale actions below.
  • Advanced shows a checkbox per action. Read is what these docs call View, and Write is Edit.
PermissionActions
BookingsRead, Write
ActivitiesRead, Write
ResourcesRead, Write
Point of SaleRead, Write, Price Override, Refund, Catalog
CRMRead, Write
TimesheetRead, Write
Timesheet (Admin)Read, Write
ReportsRead
MarketingRead, Write
Blog / CMSRead, Write
WebsiteRead, Write
CheckoutRead, Write
Company SettingsManage
FinancesRead
Waiver ApprovalApprove
IncidentsManage
PluginsManage
Charge Above BalanceOvercharge
Support TicketsRead, Write
SMS Inbox (send)Send
Broadcasts (send)Send
Message of the Day (manage)Manage
Commission (approve)Approve

Company Settings also covers adding, editing and disabling team members. The team's timesheets, summaries and tip reports still need Administrator Access, even with Timesheet (Admin) turned on.

User Groups

Setting permissions on each employee one at a time gets tedious as the team grows. A user group bundles a set of permissions -- plus rules for which operator notifications its members receive -- under one name you assign in a single dropdown. A member's effective permissions are their group's permissions plus anything ticked on their own profile.

See User Groups for the full behavior, or Set Up User Groups for step-by-step instructions.

Bookings: View vs Edit

The Bookings feature has two separate permissions, and they do different jobs:

  • View lets a team member open bookings, search them, run the audit and manager review lists, and see previews (reschedule conflicts, price previews, cancellation preview). Nothing they do is saved.
  • Edit is required for anything that changes a booking: changing its status, cancelling, rescheduling, checking guests in, editing line items or equipment, adding or removing payments, extending or shortening a trip, and sending invoices or waivers.

A view-only team member who tries an edit action gets a permission error. If staff who previously could change booking status can no longer do so, grant them the Bookings: Edit permission on their user (Company Settings > Users) or on their user group (Company Settings > User Groups). Administrators are unaffected -- they bypass all permission checks.

Refunds are stricter still: only Administrators can refund a transaction, regardless of their Bookings permissions. The same applies when a cancellation includes a refund to the customer's card: an Administrator must perform it and re-enter their password. Anyone with Bookings: Edit can still cancel without a refund, or record a cash or check refund.

Resources: View vs Edit

The Resources permission covers equipment, add-ons, amenities, coupons, taxes and fees, custom line items, membership plans, gift cards, Activity Voucher promotions and orders, and waiver forms and themes. Refunding an Activity Voucher purchase additionally requires an Administrator.

  • View lets a team member browse all of it. Equipment and add-on lists appear on booking and activity screens, so view access stays broad.
  • Edit is required to create, change, or delete any of those, and to issue, void, or adjust the balance of a gift card.

Which equipment an activity uses is set on the activity and needs Activities: Edit instead. So do the guest limit and the add-ons of a tour without equipment: they belong to the tour, not to your equipment list.

Gift card codes are treated like cash. A view-only team member sees the gift card list with codes masked to their last four characters and without balances, and cannot open a card's detail page or look a card up by code. Resources: Edit shows full codes and balances. Adjusting a card's balance upward by more than $500 in one step, and any adjustment that would take a card above $10,000, requires an Administrator who re-enters their password.

Approving a counter-signed waiver is separate — that needs Waiver Approval, and Resources: Edit alone does not grant it.

Two places cross features: the activity setup wizard creates equipment as part of setting up an activity, so staff who run it need Resources: Edit in addition to Activities: Edit; and the custom line items editor on the Location Settings page needs Resources: Edit even though the rest of that page does not.

Location Settings

Everyone can see location settings -- the location switcher, timezone, and operating details load throughout the dashboard. Changing them is restricted:

  • Company Settings is required to create or edit a location, manage approved OTA links, configure the daily summary and abandoned-cart recovery emails, and add or change tracked fields.
  • Activities: Edit is required to add or remove facilitators and to set operations blackouts, since those are day-to-day scheduling tasks rather than company configuration.

Previously any signed-in team member could change these. If someone who used to edit location settings can no longer save, grant them Company Settings (or Activities: Edit for facilitators and blackouts).

View vs Edit everywhere else

The same split applies to every feature that offers both View and Edit: Activities, Point of Sale, CRM, Timesheet, Marketing, Blog / CMS, and Checkout. View opens the pages and shows every value; Edit is required to create, change, delete, publish, upload, or send anything.

Point of Sale has three extra actions:

  • Price Override. A POS order line that is linked to a catalogue product is always priced from the product, whatever price the register sent. A line with no product (a typed name and price) needs Price Override; without it the order is refused with a prompt to pick a product.
  • Refund. Refunding a POS order, or canceling a partly paid one, moves money back to the customer, so it is separate from Edit (which lets staff ring up sales and take payments).
  • Catalog. Creating and editing products, prices, options and stock counts. Separate from Edit so a cashier can't change a price, ring it up, and change it back. Hiding or showing a product and syncing from Stripe only need Edit.

All three are off by default for existing team members. Administrators always have them.

A view-only team member sees a read-only notice at the top of editor pages and the save, create, and delete controls are disabled or hidden. Two things stay available to view-only users on purpose:

  • Clock in and clock out on the Timesheet page, since that is a staff member's own action.
  • Previews that only render something on screen, such as the email template preview.

Sending a test email or SMS from a template, survey, or workflow counts as an edit action, because a real message goes out.

Employee roles for time tracking are edited in Company Settings, so creating or changing them needs Company Settings rather than Timesheet: Edit.

Previously, view-only staff in these areas could save changes. If someone reports that a settings page no longer saves, grant them the matching Edit permission on their user (Company Settings > Users) or on their user group (Company Settings > User Groups).

Charge Above Balance

The Charge Above Balance permission controls whether a team member can move more money than a booking actually owes. It exists mainly to protect security deposits: staff should place deposits as authorization holds, not charge them outright.

  • Without the permission, a team member can only collect or capture card payments up to the booking's remaining balance. They can still place an authorization hold for any amount (the correct way to take a deposit), but the "Collect Payment" option is disabled once the amount exceeds the balance, and capturing a hold is capped at the balance.
  • With the permission (and for Administrators, who always have it), there is no cap -- staff can charge or capture any amount, including capturing a deposit when damage occurs.

This permission is off by default. After it is enabled on your account, existing team members will be limited to the booking balance until an administrator grants them Charge Above Balance. Grant it to managers and any staff who legitimately need to capture deposits.

To capture a security deposit (e.g. for damage), a team member needs this permission; otherwise they should release the hold and let a manager handle the capture.

Support Tickets

The Support Tickets permission controls who can contact Resytech support from the Help panel. The panel itself, documentation search, and Ask AI are open to everyone on the team; only tickets are gated.

  • View shows every ticket anyone at your company has raised, in the Help panel's Tickets tab and on the Support page.
  • Edit is required to raise a ticket or add a message to one. Team members with Edit can reply on any of the company's tickets, not just their own.

Administrators always have both. A team member with neither permission does not see the Contact support or Tickets tabs at all, and cannot open the Support page.

Ticking Edit on its own is enough to file and follow up on tickets: anyone holding either Support Tickets permission can view the list.

Employee Roles (Time Tracking)

Employee roles are separate from dashboard permissions and are used for time tracking categorization. They allow you to track hours by job function (e.g., "Guide", "Cashier", "Maintenance").

To manage employee roles:

  1. Click your name in the top right corner, then choose Company Settings
  2. On the Employee Roles tab, click Add Role
  3. Enter a role name
  4. Toggle Is Active to control whether the role appears in the clock-in dropdown

Each employee role has:

FieldDescription
NameDisplay name for the role (e.g., "Tour Guide")
Hourly WageOptional pay rate for the role, used to calculate shift earnings
Is ActiveWhether the role is available for selection during clock-in

Hourly Wage

Each employee role can have an optional hourly wage attached to it. When set, the system automatically calculates earnings for each shift based on hours worked multiplied by the wage rate.

The wage is snapshotted at clock-in time -- meaning the rate recorded on a time entry is the rate that was in effect when the employee clocked in. If you update a role's wage later, existing time entries keep the original rate. This ensures historical payroll data remains accurate.

To set or update a wage:

  1. Click your name in the top right corner, choose Company Settings, then open the Employee Roles tab
  2. Click edit on an employee role (or create a new one)
  3. Enter the Hourly Wage amount
  4. Save changes

Leave the wage field blank for roles where pay tracking is not needed.

Employees can select an employee role each time they clock in, and administrators can assign roles when creating or editing time entries.

Default Employee Role

Each team member can have a default employee role set on their profile. When they clock in, this role is pre-selected in the dropdown, saving time for employees who typically work the same role every shift.

Editing Employee Details

  1. Click your name in the top right corner, choose Company Settings, then open the Users tab
  2. Click the edit icon next to the employee
  3. Update any profile fields
  4. Click Save Changes

Changes to permissions take effect the next time the employee loads the dashboard.

Deactivating Employees

Rather than deleting employee records (which would remove associated time entries and audit history), deactivate employees who are no longer with your organization:

  1. Click your name in the top right corner, choose Company Settings, then open the Users tab
  2. On the employee's row, click the Disable user button
  3. Confirm

Deactivated employees cannot log in but their historical data is preserved.

Facilitator Assignment

Facilitators are the people who run a booking: guides, captains, drivers, instructors. They are kept on their own list, separate from team members, so a facilitator does not need a dashboard login.

  • Add the people under Location Settings → Facilitators (click your name in the top right, then Location Settings), with their name, phone and email. A person can be limited to certain activities.
  • Each activity defines its roles (for example Captain, Guide, Driver). A booking takes one person per role.
  • When you assign someone who is already on an overlapping booking, the dashboard warns you about the scheduling conflict.
  • A facilitator can be notified of each assignment by email, with a calendar invite. They do not have a schedule page in the dashboard.
  • If a facilitator is also a team member, link the two by choosing their Team member on the facilitator. Where the location sends tips to the staff assigned to each booking, a linked person sees their share on their own Timesheet page. Choosing or changing the link needs the Company Settings permission; the rest of the facilitator can be edited with Activities: Edit.

See Facilitators & Guides for details on scheduling and conflict detection.

Multi-Location Considerations

In businesses with multiple locations:

  • Employees can be assigned to one or more locations
  • Location assignment controls which location's data they see when logged in
  • Administrators can view and manage team members across all locations
  • Time entries are recorded at the location where the employee clocks in

See Multi-Location for details on location-level team management.

On this page