Two levels of gating. A tutorial can declare which roles it applies to and simply won't appear in the library, the search results, the campaign checklist or a hint icon for anyone else. A single step can be gated on a permission key or a role list, and when blocked renders a centered explainer ('This step needs access your role doesn't have. Ask your admin — or they can run this tour themselves.').
Also called: role based training · admin only tutorial · crew tutorials
- 1Step gates are checked BEFORE any navigation happens, so a blocked step never drags you to a screen you can't use
- 2Role-hidden chapters drop out of the campaign ring and the Resume target too — and if none remain, the whole campaign card disappears
- 3Gates use the app's real permission set, not a copy
A project manager cannot open the Leads Manager at all — that screen belongs to the owner. Pointing a walkthrough at it anyway left a PM watching a highlight sit on a menu item that did nothing for them, which teaches them the software is broken rather than that the setting is not theirs. Tutorials and individual steps now match what the person is allowed to do: a crew lead is never offered an admin tour, and an admin-only step inside a shared tour explains what happens there and who does it instead of failing in front of them.
- Training that teaches controls a user's role can't reach
- Progress checklists that can never be completed by a restricted user
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →