Troubleshooting: Why Is A Feature Locked

Some features are intentionally tied to plan access. That means a hidden or unavailable feature is not always a bug.

Why it may be hidden

The frontend can hide features that are not available on the current plan. Examples include deeper technical workflows, saved-version actions, Equipment Check, and future reporting/export features.

Common plan-related cases

If a user cannot see a version-related action, Equipment Check, or planned report/export feature, check the current subscription tier first. The public pricing section and plan articles explain the intended differences.

Why the backend still matters

Even if the UI hides something, the backend is still the final source of truth for protected actions. That is why a locked action should be understood as an access rule, not just a visual setting.