Platform Quality
Training module guard
Training area respects your workspace feature toggle.
Overview
When Training is off for your company, the section will show the standard turned-off notice instead of partial routes.
What we're building
When you switch off a feature area in Thorbis, you expect it to disappear cleanly, not leave half-loaded pages behind. Today, turning Training off for your company can still expose partial routes, which confuses anyone who lands on them.
Thorbis is adding a guard so the Training area always respects your workspace feature toggle. When Training is off, the section shows the standard turned-off notice instead of partial pages, and every route under it behaves the same way. Flip the toggle back on and the full section returns, a small consistency fix that makes on/off behavior predictable across your workspace.
What you'll be able to do
- See a clear turned-off notice when Training is disabled
- Stop partial Training routes from loading when the area is off
- Keep Training's on/off behavior consistent with other feature areas
- Trust that disabling Training hides the whole section
- Re-enable Training and get the full section back
Rollout plan
- 01
Consistent off-state
In progressWhen the workspace toggle is off, Training shows the standard turned-off notice instead of partial pages.
- 02
Full route coverage
In progressEvery route under Training respects the toggle, not just the landing page.
- 03
Toggle parity
In progressTraining matches the same guard behavior used across other workspace feature areas.
Milestones
- Not started:
Toggle check wired in
The Training section reads the workspace feature toggle.
- Not started:
Turned-off notice in place
The standard turned-off notice renders when Training is disabled.
- Not started:
Routes guarded
Sub-routes redirect to the notice instead of rendering partially.
- Not started:
Parity verified
Behavior is confirmed against other guarded feature areas.
More in Platform Quality
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.