Troubleshooting: Why Is A Feature Locked

A locked feature usually means the current plan, workspace context, or role does not allow that action.

Check context before calling it a bug

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

Why the backend still matters

The backend is still the final source of truth for protected actions. A locked action should be understood as an access rule, not just a visual setting.