Grokbot TemplatesGrokbot Templates
All use cases

Work

Write the Teams channel fence before you OAuth

Workplace chat connectors are useful — and they are a blast radius.

Share

What hurt

Ankit Agarwal (@kumarumt) posted a 10-point Teams pre-wire list for Grok Bot before OAuth on a solo or small team: which teams/channels it may read; which it may never touch (HR, legal, client-private); search yes, send default no; always_ask before any channel post or DM; no create-chat until a human names participants; Action Recording on if you have it (90-day scrubbed trail); MCP allowlist only the Teams server URL you intend; kill/revoke Microsoft consent in under 60s; never paste client PII into a prompt that can fan out; dry-run in a sandbox channel first. Author tip list — not a system prompt. Not affiliated with xAI.

What to install or create

Write the fence first. Then OAuth. Search/read in a sandbox channel before any send. Keep revoke under a minute.

Bots

  • Teams fence desk

    Holds the channel fence. Search/read only until you unlock a named send.

Plugins

  • Microsoft Teams

    Required

Files

  • Author pre-wire list: (1) which teams/channels it may read (2) never-touch (HR, legal, client-private) (3) search yes, send default no (4) always_ask before channel post or DM (5) no create-chat until a human names participants (6) Action Recording on if you have it — 90-day scrubbed trail (7) MCP allowlist: only the Teams server URL you intend (8) kill/revoke Microsoft consent in under 60s (9) never paste client PII into a prompt that can fan out (10) dry-run in a sandbox channel first.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/kumarumt/status/2100384243016749295 — paste the 10-point fence into a note; do not invent a system prompt.
  2. 2Write which teams/channels it may read vs never-touch (HR, legal, client-private) before any OAuth.
  3. 3Add the Teams plugin; set search yes / send default no / always_ask before post or DM; ban create-chat until you name participants.
  4. 4Allowlist only the Teams MCP URL you intend; confirm you can revoke Microsoft consent in under 60s.
  5. 5Dry-run search/read in a sandbox channel. No client PII in prompts. Sends stay behind your yes.

Approval fence

Search may be on. Channel posts, DMs, and create-chat stay behind always_ask / your yes. No auto-send.

What to tweak

Steal the channel fence. Connectors expand reach; the fence is the product.

Source

Ankit Agarwal @kumarumt · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro