Toggle public template sharing for Grok Bot

Team and Enterprise admins control whether members can share Bot templates outside the team. The control lives on the Grok Bot page of the Cursor dashboard. Official guide: Grok Bot for teams and enterprises → Admin controls → Public template sharing.

Off keeps Bot template sharing within your team. Cursor enforces the policy on its servers, including for templates that were already public. Enterprise teams start with public sharing off; other teams start with it allowed.

Who can change it

Admins on Teams and Enterprise. Members never see the Grok Bot admin page. The setting is team-wide.

Change the toggle

1. Sign in as a team admin and open Grok Bot in the Cursor dashboard.
2. Find Public template sharing.
3. Leave it on only if members should publish Bot templates outside the team.
4. Turn it off for security-sensitive rollouts so shares stay inside the team.

Recommended baseline for security-sensitive deployments: keep public template sharing off unless members should publish outside the team.

What a public share actually exposes

When a member shares a Bot, anyone with the link can preview it on x.ai and add a copy to their own account. Recipients do not get the sharer’s computer, logins, or conversation history. The link exposes the Bot’s configuration — strip secrets and confidential details before sharing. Adding a shared Bot accepts the third-party bot terms (see Share a Bot in the official docs).

Turning the team policy off blocks new outside sharing and is enforced server-side for existing public templates.

Pitfalls

• Enterprise defaults to off; self-serve Teams often default to allowed — audit on first rollout.
• This toggle is independent of Cloud Agents delegation and of Enterprise Network Controls.
• Sharing a Bot is not the same as granting access to that member’s hosted computer.