Overview
Delegable User Groups let members of one User Group assign work to another User Group they don't belong to. They unlock cross-team handoffs — Operations dispatching to Maintenance, a control room routing tasks to multiple crews, a general crew escalating to specialists — without forcing the assigning User to be a member of the receiving team.
Why this matters: By default, Mobaro only lets a User assign work to themselves or to User Groups they belong to. That's the right default — it prevents accidental cross-team chaos. Delegable User Groups are the controlled exception, opening up specific cross-team workflows without flattening the structure.
Required access: To configure delegable User Groups, you must be a Super User or hold a Role with the User Groups: Modify permission. End Users assigning work do not need any special permission beyond what they already have for creating Assignments.
The default behavior
Without any delegable Groups configured, here is what a User sees when they create an Assignment and open the assignee dropdown:
Themselves — they can always assign work to their own User account.
Every User Group they are a direct member of — listed by name.
Every individual User who is also a member of one of those Groups — to support direct assignment within their own teams.
Anything outside that scope is hidden. A Maintenance technician cannot accidentally assign work to F&B Leadership, and an F&B supervisor cannot accidentally route a task to the Ride Operators — Zone A Group. The walls between teams are intentional.
Best practice: Treat the default as the right answer until proven otherwise. The fewer cross-team paths you open, the easier your assignment flows are to reason about and audit.
What a delegable User Group changes
When you mark another Group as a delegable User Group on a User Group, members of the configured Group gain the ability to assign work to the delegable Group — without becoming members of it.
What changes
The delegable Group appears in the assignee dropdown for members of the configured Group when they create an Assignment.
Members can assign work directly to the delegable Group as a target.
What does not change
Members of the configured Group do not receive Assignments routed to the delegable Group.
Members do not gain visibility into the delegable Group's Schedules, Notification Rules, or other configurations.
Members do not gain the delegable Group's Location memberships.
The delegable Group's permissions are not applied to the configured Group's members.
Note: Delegable User Groups are strictly a one-way assignment permission. They do not establish any membership relationship in either direction.
When to use a delegable User Group
Reach for a delegable User Group when:
Cross-team handoff — a User in one team needs to route work to a different team. Most common at shift-lead level (Ops Lead → Maintenance, Maintenance Lead → Specialty Mechanics).
Centralized dispatch — a control room or operations desk routes incoming work to multiple operating crews. The dispatcher is not part of any single crew but needs to assign to all of them.
Escalation paths — a frontline team escalates difficult or specialty work upward (frontline operator → ride mechanic, general maintenance → electrician).
Compliance and audit teams — a compliance lead routes follow-up Assignments to operating teams without being a working member of those teams.
When not to use a delegable User Group
If the User actually does participate in the receiving Group's work — add them as a regular member of that Group instead.
If you want the receiving Group to also be able to assign back to the originating Group — set up a delegable User Group in both directions; one direction does not imply the other.
If you are trying to grant permissions rather than just an assignment route — that's a Role, not a delegable User Group.
Configure a delegable User Group
Open the assigning User Group
From the Mobaro Backend, navigate to User Groups and select the Group whose members you want to give cross-team assignment ability. This is the Group doing the assigning, not the one being assigned to.
Expand the Memberships section
In the editor panel on the right, scroll to the Memberships section and expand it. You will see Administrators, Users, Delegable User Groups, Locations, and Location Groups.
Add the receiving Group as a delegable User Group
Under Delegable User Groups, search for and add the Group you want this Group's members to be able to assign work to.
Heads up: Direction matters. If you add Maintenance as a delegable Group on Ops Leads, Ops Leads can assign to Maintenance — but Maintenance cannot assign to Ops Leads. To enable the reverse, configure the same setting in the opposite direction on the Maintenance Group.
Save
Click Save. The change takes effect immediately. Members of the configured Group will see the new delegable Group in their assignee dropdown the next time they create or edit an Assignment.
Worked examples
Example 1: Operations dispatches to Maintenance
Scenario: An Operations Lead notices a queue gate latch is broken. They need to assign a repair to the Maintenance team without being a member of Maintenance.
Setup: On the Ops Leads User Group, add Maintenance — All as a delegable User Group.
Result: When an Ops Lead creates an Assignment, both Ops Leads and Maintenance — All appear in the assignee dropdown. Members of Ops Leads who are not leads (regular operators) only see Ops Leads.
Example 2: Central dispatcher routes to multiple crews
Scenario: A control room operator routes incoming work to several operating crews across a park, but is not a member of any of them.
Setup: Create a Control Room User Group with the dispatcher as a member. On the Control Room Group, add Ops — Zone A, Ops — Zone B, Ops — Zone C, and Maintenance — All as delegable User Groups.
Result: The dispatcher sees all four operating crews in the assignee dropdown when creating Assignments. They do not receive the resulting Assignments themselves and have no visibility into the crews' Schedules.
Example 3: Maintenance escalates to specialists
Scenario: A general Maintenance technician identifies an electrical issue that needs a licensed electrician.
Setup: On the Maintenance — All User Group, add Electricians as a delegable User Group.
Result: Any Maintenance technician can assign the issue to Electricians. Electricians keep their own focused queue, manage their own Schedules, and don't see Maintenance's general work unless it's been delegated to them.
Anti-patterns to avoid
Watch out for these configurations, which create dropdown clutter and obscure assignment flows:
Every Group delegable to every other Group — defeats the purpose of separating teams. If everyone can assign to everyone, you have one big team, not a structured set of teams.
Delegable Groups instead of memberships — if the User actually does the receiving team's work, add them to the Group as a member. Delegable is for assigning to, not participating in.
Bidirectional setups by default — only configure the reverse direction if you actually want both teams to assign to each other. Most cross-team flows are one-way.
Delegable Groups stacked on too many parent Groups — try to configure delegation on the smallest set of "leadership" or "dispatcher" Groups rather than every Group in the hierarchy.
Troubleshooting
A User can't see a Group they expect to assign to
Check the following in order:
Confirm the User is a member of the Group that has the delegable User Group configured. Delegable settings only apply to that Group's members — not to all Users in the system.
Confirm the receiving Group is set as a delegable User Group on the User's Group, not just a member relationship.
Confirm the receiving Group has Assignability enabled. A Group with Assignability turned off won't appear as an assignee even when set as delegable.
Have the User log out and log back in. Delegable User Group changes take effect immediately for new sessions but cached dropdowns may need a refresh.
Assignments work one direction but not the reverse
Delegable User Groups are one-way. If Ops can assign to Maintenance but Maintenance cannot assign back, you need to configure the reverse on the Maintenance Group: add Ops as a delegable User Group on Maintenance.
Too many Groups in the dropdown
If members of a Group are seeing dozens of delegable options, audit the Group's Delegable User Groups setting and remove any that are not actively used. Consider whether some delegations should move to a smaller "lead" or "dispatcher" sub-Group instead of the whole Group.
See also
Create and manage User Groups — full walkthrough of User Group creation, memberships, and configuration.
User Groups vs Roles: understanding the two access primitives — for distinguishing User Groups from Roles when designing access.
How to create and delegate an Assignment — for the Assignment-creation side of the delegation workflow.
Using Assignment Definitions — for restricting which Groups can create or be assigned specific kinds of Assignments.
How to set up Roles — for granting the Assignment-creation permission delegable Groups assume is in place.
Frequently asked questions
Q: Does adding a delegable User Group give me access to that Group's data?
A: No. Delegable User Groups are strictly a one-way assignment permission. You can assign work to the Group, but you do not gain visibility into its members, Schedules, Notification Rules, or Location memberships.
Q: Are delegable User Groups bidirectional?
A: No. If Ops has Maintenance set as a delegable Group, Ops can assign to Maintenance — but the reverse is not automatic. Configure both directions independently if you need both.
Q: Do delegable User Groups grant permissions?
A: No. They only expand which assignees show up in the assignee dropdown. See User Groups vs Roles.
Q: Can a User Group have multiple delegable Groups?
A: Yes. There is no practical limit. Common setups for control-room or dispatcher Groups configure several delegable Groups at once.
Q: Will members of the delegable Group see who assigned the Assignment?
A: Yes. Standard Assignment attribution applies — the originating User is recorded as the creator, regardless of whether the assignee is in their direct Group or a delegable Group.
Q: Does a delegable User Group affect Notification Rules or Schedules?
A: No. Delegable settings only affect Assignment assignee dropdowns. Notification Rules and Schedules use direct Group membership only.
Q: Can a delegable User Group be removed?
A: Yes. Open the User Group, expand Memberships, remove the entry under Delegable User Groups, and save. Existing Assignments that were already assigned to the (formerly delegable) Group are not affected — only new Assignment creation is gated by the change.
Q: How are delegable Groups different from Assignment Definition Group restrictions?
A: They operate at different layers. Delegable User Groups govern which Groups appear in any assignee dropdown for a given User. Assignment Definitions can further restrict which Groups can create or be assigned specific kinds of Assignments. Delegable User Groups are about the User's general capability; Assignment Definitions are about the work item's policy. See Using Assignment Definitions.