Skip to main content

Documentation Index

Fetch the complete documentation index at: https://playerzero.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Microsoft Teams is a collaboration platform from Microsoft. PlayerZero’s Teams integration lets you interact with AI Players directly from Teams — starting investigations from channel conversations, approving workflow stage transitions, and receiving notifications alongside your team’s work.

What You Can Do

Once connected, you can:
  • @mention or message the bot — Mention the PlayerZero bot in any channel or send it a direct message to start a conversation. The bot responds with an interactive card to configure your investigation.
  • Start investigations with Ask PlayerZero — Select a project, choose a workflow or playbook, and provide your question. PlayerZero creates a Player session and responds in the thread.
  • Approve workflow stage transitions — When a Player needs approval to move to the next workflow stage, an interactive approval card appears in Teams with options to approve immediately or approve with a message and playbook.
  • Receive notifications in channels — Get workflow stage approval requests, Player summaries, and other notifications delivered to your team’s channels.
  • Open in Chat — Link an existing PlayerZero session to a Teams channel from the PlayerZero UI, so you can continue a conversation in Teams.
  • Reply in threads — Continue a conversation with a Player by replying in the Teams thread. Messages in the thread are forwarded to the Player, and the Player’s responses appear in the thread.

Ask PlayerZero

When you @mention or message the PlayerZero bot in a channel, the bot responds with an interactive Ask PlayerZero card. This card lets you configure your investigation before it starts. For organizations with multiple projects, the card starts with a project picker. Select your project and click Continue to load the compose form. For single-project organizations, the compose form appears directly. The compose form includes:
  • Workflow — Optionally select a workflow to start the Player in a specific workflow stage
  • Playbook — Optionally select a playbook to guide the Player’s approach
  • Message — Describe your question or task
Click Ask to create the Player session. PlayerZero responds in the thread with the Player’s findings and a Full Chat link to the complete session in PlayerZero. If you @mention the bot in an existing thread, the initial message from that thread is automatically included as context for the Player.

Workflow Stage Approvals

When an AI Player needs approval to move to the next workflow stage, PlayerZero delivers an approval card to Teams. These cards appear in the thread where the Player was started (if it originated from Teams) and in any channels configured for that workflow stage. The approval card includes:
  • An Approve button to approve the transition immediately
  • A Playbook picker to optionally select a playbook before approving
  • An Approval message field to add context or instructions
  • A View in PlayerZero link to open the full Player session
After approval, a confirmation message is posted to the thread so the team can see who approved and any notes they included.

Open in Chat

You can link any PlayerZero session to a Teams channel directly from the PlayerZero UI. From a Player session in PlayerZero, click Open in Chat and select a Teams channel. PlayerZero creates a new thread in that channel linked to the Player — messages in the thread are forwarded to the Player, and the Player’s responses appear in the thread. If the Player is already connected to a Teams thread, clicking Open in Chat takes you directly to that thread instead.

Receive Notifications

PlayerZero delivers notifications to Teams channels based on your project and workflow configuration. Notifications include:
  • Workflow stage approval requests when a Player needs human approval to continue
  • Player response summaries posted to threads where investigations were started
  • Notifications from monitor-initiated Players when a monitor triggers a new investigation and delivers results to a configured channel
Notification routing is configured per project and per workflow stage in Settings. See Notification Configuration for details.

Setup

Setup starts in PlayerZero — no pre-configuration in Microsoft Teams is required. The Teams connection is managed under Collaboration, not the Ticketing page (which is used for tools like Jira and Linear). Connecting Teams requires Microsoft 365 admin consent.
  1. In PlayerZero, navigate to Settings → Collaboration
  2. Click the Microsoft Teams card to open its detail page
  3. Click Enable — a popup window will open for Microsoft admin consent authorization
  4. Sign in with a Microsoft 365 admin account and grant consent for your organization
  5. After authorization, a team picker appears — select which Teams to install the PlayerZero bot in
  6. Click Install to add the bot to the selected teams, or Skip to finish setup and install the bot later
After setup, the PlayerZero bot is available in all channels within the teams you selected. You can add or remove teams at any time from the Collaboration settings page by clicking Edit on the Connection Details card.

Notification Configuration

Once Teams is connected, you can configure where notifications are delivered at the organization and project level. Organization-level defaults:
  • Set a default Teams channel for notifications from the Collaboration settings page
  • Control which projects are authorized to use the Teams connection — either all projects or a specific set
Per-project, per-stage channels:
  • Each project can configure notification channels independently
  • When selecting a channel, first choose a team, then select a channel within that team
  • Assign different channels to different workflow stages — for example, route approval requests to a support channel and engineering escalations to an engineering channel
  • Enable or disable workflow notifications (approval requests, stage transitions) per project
Business hours:
  • Optionally restrict notifications to business hours based on your team’s timezone
  • Notifications generated outside business hours are held and delivered when business hours resume

Get Started

👉 AI Player overview 👉 Workflow overview 👉 Setup guide