Enable Claude Code Remote Control on a Team or Enterprise plan

You're on your company's Claude Team plan, you run claude remote-control or /remote-control, and it refuses. On Pro and Max, Remote Control works as soon as you sign in. On Team and Enterprise it doesn't, and nothing you change on your own machine fixes that.

The short answer

Remote Control is off by default on Team and Enterprise plans. An Owner of your Claude organization has to turn it on:

Go to claude.ai/admin-settings/claude-code.
Turn on the Remote Control toggle.

Per Anthropic's Remote Control docs, this is a server-side organization setting. Until it's on, nobody in the org can use Remote Control, however they sign in. After it's on, members start Remote Control the normal way.

If the toggle is on and it still fails, the cause is one of five things covered below: custom roles, a device policy, Trusted Devices, a compliance setting, or a sign-in under the wrong organization.

If you're not the Owner

Most people hitting this aren't. Here's a message you can send as is:

Hi, could you turn on Remote Control for Claude Code in our Claude org?
It's at claude.ai/admin-settings/claude-code, the "Remote Control" toggle.
It's off by default on Team/Enterprise. It lets me check on and steer
a Claude Code session from the Claude app on my phone. Thanks!

If your org uses custom roles, add: "and please check my roles include the cloud sessions permission and the Claude Code remote control permission."

Step 1: check which organization you're signed in under

Before chasing settings, make sure Claude Code is checking the org you think it is. In a session:

/status

Look at the plan and organization. A common surprise:

You moved to a personal Pro or Max plan, but Claude Code is still signed in under an old Team login, so it checks that org's policy. Fix: claude auth logout, then claude auth login.

Step 2: the Owner turns on the toggle

Only an Owner can do this, at Admin settings > Claude Code. If the switch is grayed out, the org has the HIPAA configuration applied. Per the docs, organizations with HIPAA or Zero Data Retention can't enable Remote Control at all. That's a decision for the Owner and your Anthropic account team, not something a member can work around.

Once it's on, run /remote-control again, or start claude remote-control. If you still get the old answer, update Claude Code (claude update), restart it, and try once more.

Step 3 (Enterprise): check custom roles

If your Enterprise org manages access with custom roles, Remote Control needs both of these on your roles:

the cloud sessions permission
the Claude Code remote control permission

If either is missing, you see "Remote Control is disabled by your organization's policy", even with the toggle on. The tell: it works for colleagues and not for you. An Owner adds the missing permission at Organization settings > Roles (claude.ai/admin-settings/roles).

Step 4: check for a device policy

If the error mentions disableRemoteControl, your IT team has switched Remote Control off on this computer through managed settings. That's separate from the org toggle and from how you sign in. Only whoever manages your device's settings can change it.

Step 5: Trusted Devices, if your org turned it on

Trusted Devices is an optional extra check, in beta, that an Owner can turn on at Organization settings > Capabilities > Remote sessions. With it on:

Each browser, phone or desktop app you use to view or steer a session enrolls once, as part of a real sign-in.
Your sign-in must be no more than 18 hours old. After that, the next Remote Control interaction asks for Face ID, Touch ID, Windows Hello or a passkey.
The machine running Claude Code gets its own credential when you sign in to the CLI. There's no separate enrollment step in the terminal.

The two errors you might see, and the fix the docs give for each:

"Your organization requires Trusted Devices for Remote Control, but this device is not enrolled": run /login in Claude Code.
"session expired for trusted-device check": run /login, or confirm with Face ID, Touch ID, Windows Hello or a passkey when the app asks.

If your org requires Trusted Devices, DISABLE_TELEMETRY or DO_NOT_TRACK in your environment also block Remote Control. Unset them.

Error messages, decoded

You see	Most likely cause	Who fixes it
"Remote Control is disabled by your organization's policy"	Toggle off, or a missing role permission	An Owner
The same, mentioning `disableRemoteControl`	Device policy in managed settings	Your IT team
The same, without "contact your organization admin"	HIPAA configuration; `/status` shows `HIPAA`	Owner and Anthropic account team
"...requires Trusted Devices... not enrolled"	Trusted Devices on, device not enrolled yet	You, with `/login`
"Remote Control environments are not available for your account"	Several causes, plan included	See our guide to that error

What doesn't change on Team plans

API keys still don't work. Remote Control needs a claude.ai login. A CLAUDE_CODE_OAUTH_TOKEN from claude setup-token can't start Remote Control either.
The computer still has to stay on. Remote Control is a window into a claude process on some machine. Close the laptop and the phone has nothing to talk to. How long an unattended session lasts goes through what stops it.

Using an always-on machine with a Team plan

The same rules apply on any machine you run Claude Code on, a VPS or a hosted one. A Podway pod is an always-on cloud computer for Claude Code that you open from the Claude app through Remote Control. Podway can't skip your org's check: on a Team or Enterprise plan, the Owner has to enable Remote Control first, exactly as above. On Pro or Max it works as soon as you sign in.

You need your own Claude plan: Pro or Max, or a Team or Enterprise seat with Remote Control enabled. On a pod, if the agent crashes, Podway restarts it and Remote Control reconnects, and before your Claude login expires, Podway tells you, with a one-click reconnect. Claude runs without permission prompts there, because the pod is its own isolated machine.

Your first pod is free, no card needed, and pods start at $4/month. Start a pod, or read more on the agent computer page.

FAQ

Is Remote Control available on the Claude Team plan?

Yes, once an Owner turns it on at claude.ai/admin-settings/claude-code. It's off by default on Team and Enterprise.

Can a regular admin turn it on, or only an Owner?

Anthropic's docs say an Owner. If you're an admin and don't see the toggle, ask an Owner.

I'm the Owner and the toggle is grayed out. Why?

Per the docs, that means the HIPAA configuration is applied. Organizations with HIPAA or Zero Data Retention can't enable Remote Control.

It works for my teammates but not for me.

On Enterprise with custom roles, your roles need both the cloud sessions permission and the Claude Code remote control permission. Also run /status to check you're signed in under the right org.

Do I need to enable anything on Pro or Max?

No. Remote Control works on Pro and Max as soon as you sign in with your claude.ai account.

Last reviewed October 26, 2026, against Anthropic's Claude Code docs. Spot something out of date? Email support@podway.io and we'll fix it.