Overview
Membership-based logic shows or hides an element or page based on whether the User completing the Checklist belongs to a given User Group. It tailors the same Checklist to who is running it.
Why this matters: A shared Checklist often has steps that only one role should see or do — a maintenance-only verification, a manager-only sign-off. Membership logic shows those steps only to members of the right User Group, so everyone runs the same Checklist but each person sees the parts that apply to them.
How it works
Attach the logic to the element or page and choose the User Group whose members should see it. When a User runs the Checklist, Mobaro checks their membership and shows the element only if they belong to that Group.
Example
A handover Checklist includes a page, "Maintenance verification," with membership-based logic set to the Maintenance User Group. Operators completing the handover don't see it; a maintenance team member running the same Checklist does.
Frequently asked questions
Q: Whose membership is checked — the assignee or the person completing it?
A: The User completing the Checklist. The element shows based on that User's membership of the configured Group.
Q: Is this the same as restricting who can run the Checklist?
A: No. This controls visibility of content within the Checklist by Group membership. Who can be assigned or run a Checklist is controlled by Schedules, Roles, and Competencies, not logic.
Q: How do I set it up?
A: Add logic to the element or page and choose the "based on a membership" condition. See Adding logic to a Checklist.