Troubleshooting: Why Is A Feature Locked

Some features are intentionally tied to access rules. 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 in the current personal plan, Business workspace context, or role. Examples include technical-mode workflows, archive actions, Equipment Check, PDF export, and some workspace-specific tools.

Common access-related cases

If a user cannot see a version-related action, archive control, Equipment Check, export feature, or workspace action, check the current billing tier, active workspace, and current role 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.