Overview
Users are the people who sign in to Mobaro. Locations are the places where work happens, such as a ride, a shop, a pool or a back-of-house area. Almost everything else in Mobaro connects the two: Schedules put Checklists at Locations for Users to complete, Assignments send work to people, and every Result records who did the work and where.
This article explains the building blocks and how they connect, and links to the articles that show each step.
At a glance |
|
Who can do this | Creating Users: Super Users or a Role with Users › Create. Creating Locations: Super Users or a Role with Locations › Create |
Where | Administrate › Users, User Groups, Roles, Locations and Location Groups |
Works on | Backend (web) to set up. The Mobile app and RideOps use them. |
Availability | All organizations |
💡 Why this matters: A User's Roles decide what they can do. Their Location membership decides where. Most "they can't see it" questions come down to a missing Location membership, not a missing permission.
The people side
Building block | What it does |
User | One person. They sign in with the email address on their User, which must be unique across all of Mobaro. One User can belong to several Mobaro organizations. See Create new users in your organization. |
Role | What a User can do in each area, such as viewing Results or editing Schedules. A Role applies across the whole organization. See Introduction to Roles. |
User Group | A named team. Use it to assign work, send notifications, make every member a member of Locations, or give every member a Role. A User can be in any number of groups. See Create and manage User Groups. |
Super User | Every permission in the organization, at every Location. Only Mobaro grants it. See What is a Mobaro super user?. |
The place side
Building block | What it does |
Location | One place where work happens. Checklists are completed at a Location, Schedules target Locations, and Assignments usually point to one. See Overview of Locations in Mobaro. |
Location Group | A folder of Locations, which can be nested to mirror your park, for example Resort › Water Park › Slides. A Location can be in several groups. Schedules can target a whole group, and dashboards can filter by group. See How to create Location Groups. |
How users and locations connect
Location membership. A User is a member of a Location if they're added to it directly, through a User Group, or through a Location Group that contains it. Any one route is enough.
What membership shows. Results, Assignments, Notes, Gallery images and Downtime show only for Locations the User is a member of, whatever their Role. A Role with Locations › View shows every Location record but doesn't make anyone a member.
Work in the app. The Mobile app shows scheduled Checklists where the User, or one of their User Groups, is an assignee, at Locations they're a member of.
Reporting. Each Result records its Location and the User who completed it, so dashboards and reports can compare by Location, Location Group or User.
For the full access model, see How access works in Mobaro.
Set up users and locations
1. Create Locations and Location Groups
Create a Location for each place where work happens, and sort them into Location Groups that match your zones. See How to create Locations.
2. Create User Groups and Roles
Create a User Group for each team, and a Role for each kind of job. See Set up Roles to manage permissions.
3. Create Users
Create each User with their name and email address. See Create new users in your organization.
4. Connect them
Add Users to their User Groups, add the User Groups to Roles, and add the User Groups to the Locations or Location Groups they work at. Only Super Users can add Roles, User Groups and Locations in the User editor. Everyone else adds the User from the User Group, Role or Location instead. See Giving Users access to a Location.
Best practices
Mirror your real zones in Location Groups and your real teams in User Groups.
Give Location membership through User Groups on Location Groups, rather than User by User. A new ride added to the zone's group then reaches the whole team.
Represent each physical place once. Duplicate Locations split your history and reports.
Keep each User's email address up to date: it's how they sign in and reset their password.
Frequently asked questions
If I give a user group a location group, do I need to add each location too?
No. Every member of the User Group becomes a member of every Location in the Location Group and its child groups, including Locations added later. See Giving Users access to a Location.
What's the difference between direct and inherited members?
A direct member was added to the Location itself. An inherited member comes through a User Group or a Location Group. Both give the same access.
If a checklist is scheduled at a location where I'm a member, do I become an assignee?
No. Membership alone doesn't assign work. The Mobile app shows a scheduled Checklist only when you or one of your User Groups is an assignee on it, at a Location you're a member of.
How can a manager see all the assignments at a location, not only their own?
Give them a Role with Assignments › View and make them a member of the Location. They then see every Assignment at that Location in the Backend, not only ones assigned to them.
Can I schedule a checklist on a location group?
Yes. A Schedule can target a whole Location Group, so the Checklist is due at each of its Locations. See How to create Location Groups.
Can I add a new user without putting them in a user group?
Yes. User Groups are optional. Without one, add the User directly to the Locations or Location Groups they work at, and name them individually on Schedules and Assignments.