ResytechResytech Docs
Team Management

Set Up User Groups

How to create a user group, set its permissions and notification rules, assign team members to it, and understand what members can still change themselves.

A user group bundles dashboard permissions and operator notification rules under one name, so you configure them once and apply them to as many team members as you like. This guide walks through creating a group, assigning users, and the rules that decide who gets which alerts.

For the concepts behind groups, see User Groups.

Create a group

  1. In the sidebar, click Company.
  2. Scroll to the User Groups section.
  3. Click Add Group.
  4. Enter a Name (required, unique within your company) -- for example Front Desk, Dock Staff, or Managers.
  5. Optionally enter a Description so other administrators know who the group is for.
  6. Under Group Permissions, toggle the features members of this group should have.
  7. Under Notification Rules, set a rule for each event type and channel (see below).
  8. Click Create Group.

Set notification rules

Every event type has a rule per channel -- Email, SMS, and Push. Pick one of:

RuleWhat it does
DefaultLeaves the platform behavior in place, as if the group said nothing.
Optional (off)Members can turn it on themselves. Starts off for members who never touch it.
Optional (on)Members can turn it off themselves. Starts on for members who never touch it.
RequiredAlways sent. Members see it locked on and cannot opt out.
OffNever sent on that channel. Members cannot opt in.

A practical setup:

  • Dock Staff -- new bookings Optional (on) by email, chargebacks Off. They see the day's bookings without being copied on money problems.
  • Managers -- chargebacks and message delivery failures Required by email. Nobody can quietly mute the alerts that cost money.
  • Front Desk -- SMS Inbox messages Optional (on) by push, so whoever is on shift picks it up.

SMS cannot be set to Required, and cannot default to on. Staff SMS goes to personal phones and costs money per message, so every member enables it themselves.

In-app notifications are always delivered and are not part of the rules.

Assign a user to a group

  1. In the sidebar, click Company.
  2. In the Company Users section, click the edit icon next to the user.
  3. Choose a group from the User Group dropdown.
  4. Click Save Changes.

The User Group dropdown only appears once at least one group exists -- create a group first if you do not see it.

The user's permission list is now labeled Additional Permissions -- anything ticked there is granted on top of the group. Use it for one-off exceptions ("Front Desk, but she also handles refunds") rather than re-ticking what the group already covers.

To remove a user from a group, clear the User Group dropdown and save. They keep whatever is ticked in their own permission list.

Permission changes reach a member the next time their session refreshes, the same as editing an individual user. Administrators bypass permission checks entirely, so group permissions do not restrict them.

Edit or delete a group

  • Edit -- click the edit icon on the group row, change permissions or rules, and save. Changes apply to every member.
  • Delete -- click the delete icon and confirm. The confirmation tells you how many members are affected. Members are not deleted: they keep their individual permissions and fall back to default notification behavior.

Check what a member sees

Ask a member (or use your own account) to open Profile > Notifications. Channels the group pinned show a padlock badge -- Always for Required, Off for Off -- instead of a toggle. Everything else stays a normal toggle they can set themselves.

If an event type shows every channel locked off, that is expected: the row stays visible because in-app notifications still fire for it.

Tips

  • Start with Default everywhere and only pin the channels you actually care about. Pinning everything makes the group brittle and irritates staff.
  • Reserve Required for alerts with financial or legal consequence -- chargebacks, delivery failures.
  • One group per user. If someone genuinely needs two groups' worth of access, put them in the closer group and grant the difference as Additional Permissions.

On this page