[DOCS] Be transparent and truthful in your featuers availablitly
Documentation Type
Missing documentation (feature not documented)
Documentation Location
Section/Topic
Remote Control is disabled by your organization’s policy
Current Documentation
Your Team or Enterprise admin hasn’t enabled it:
Remote Control is off by default on these plans. An admin can enable it at [claude.ai/admin-settings/claude-code](https://claude.ai/admin-settings/claude-code) by turning on the Remote Control toggle. This is a server-side organization setting, not a managed settings key.
What's Wrong or Missing?
Remote Control is not available on the Team Plan. Period.
Why are you not telling straight away and throwing the user from one option to another?
The referred settings https://claude.ai/admin-settings/claude-code are available to Enterprise plans only.
This is what Claude say about this issue
The documentation says Remote Control is available on "all plans" and directs Team admins to enable a toggle at claude.ai/admin-settings/claude-code — but that page doesn't even exist for Team plan users. You only discover the real limitation after hitting the wall, not upfront. That's genuinely poor transparency, not just a documentation gap.
From your screenshot, you're on Claude Code v2.1.107 on a Team plan, and --remote-control fails outright with "disabled by your organization's policy" — confirming this is a hard platform-level block, not a misconfiguration on your end.
What's actually true (that Anthropic doesn't state clearly upfront):
- Remote Control is not available on Team plans in practice
- The admin toggle page doesn't exist for Team plan admins
- The error message "contact your administrator" is misleading when you are the administrator
- The docs say "all plans" but mean "all plans where the admin has enabled it" — which requires Enterprise to access
Suggested Improvement
Be transparent and say "Remote Control feature is not available on Team Plans."
Impact
High - Prevents users from using a feature
Additional Context
You have to dig deep to find the actual issue, which is the waste of users' time.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗