Overview
A Competency is a single skill or qualification you track in Mobaro — "Lifeguard", "Coaster Operator", "First Aid". Competencies are the foundation of the qualification system: a User holds a Competency by being awarded a Certification for it, and Competencies can be required on Schedules and for Operator and Attendant positions in RideOps. This article covers creating one. For the bigger picture, see Utilizing Competencies.
At a glance |
|
Who can do this | Super Users, or a Role with Competencies › Administrate (create, edit, and delete; includes View). Competencies › View lets a User see Competencies without changing them. See Role permissions reference. |
Where | Competencies |
Works on | Backend (web) |
Availability | All organizations |
💡 Why this matters: The Competency is just the label — it's the thing a Certification grants and a Schedule or RideOps position requires. Creating clear, well-named Competencies up front means every Certification and requirement built on top of them stays easy to read and audit.
Create a Competency
1. Go to Competencies
In the Mobaro Backend, click Competencies in the navigation.
2. Create a new Competency
Click Create.
3. Add Competency details
Give the Competency a clear Name. Optionally add a Description to clarify its purpose.
4. Save
Click Save to add the Competency to your setup.
After you save a Competency
When you open an existing Competency, the editor also shows:
Users — every User with a Certification for this Competency, and whether it's valid, due for renewal, or expired.
Usages — the Schedules, Checklists, and Locations that require this Competency.
Delete a Competency
🛑 Critical: Deleting a Competency can't be undone. It also:
deletes every Certification for the Competency, including ones awarded by Certification Processes;
deletes every Certification Process that awards the Competency;
removes it as a requirement from other Certification Processes, Schedules, Checklist schedule triggers, and RideOps Locations.
Users who held it will no longer meet those requirements. Check the Users and Usages panels before you delete.
Grant the Competency to Users
Once a Competency exists, you grant it to Users in one of two ways:
Create Certifications directly — for one User or several at once — see Gaining and managing Certifications.
Set up a Certification Process that awards the Competency when a User completes a training Checklist — see Create a Certification Process.
Best practices
Name Competencies for the qualification, not the person or position — Coaster Operator, not Zone A staff. One Competency can then be required across many Locations and granted to many Users.
Check for duplicates first. Mobaro doesn't stop you creating two Competencies with the same name, so check the list before you add a new one.
Frequently asked questions
How do I add a user to a competency?
Give them a Certification for it: create one manually in Competencies › Certifications, or have them complete a Certification Process that awards it. See Gaining and managing Certifications.
What's the difference between a Competency and a Certification?
A Competency is the skill itself. A Certification is a specific User's awarded, dated instance of that Competency — it's how a User comes to hold the Competency.
Can I rename a Competency later?
Yes. Edit it and change the Name; existing Certifications and requirements stay linked. The name is required, so it can't be left empty.