Skip to main content
Sammy Labs provides a comprehensive Slack integration that transforms Slack workspaces into intelligent knowledge management and policy tracking hubs. This integration delivers three core features that work together to create a seamless workflow where policies are discovered, tracked, analyzed, and actioned—all within Slack.

​
Security First: Built with Privacy by Design

SAMMY on Slack follows the principle of least privilege and is designed to only respond when explicitly invoked (e.g., an @mention in a thread). It does not inject itself into random public channels or send unsolicited messages.
From the app manifest, SAMMY is granted access only to:

Read @mentions

app_mentions:read - Detect when users explicitly mention @SAMMY

Post messages

chat:write - Send responses and notifications to threads

Read files

files:read - Access files in channels where SAMMY is added

Read channel history

channels:history - Read messages only in public channels SAMMY is explicitly added to
While Slack permissions allow SAMMY to read messages within channels it is added to, SAMMY’s application logic only processes and responds to user-triggered interactions in channels where users have chosen to involve the bot.

​
What This Means for Your Organization

No Passive Monitoring

SAMMY never monitors or logs conversations in the background

User-Initiated Only

Processing only occurs when you @mention SAMMY or click an action button

Explicit Consent

You control exactly when and where SAMMY operates

​
Core Capabilities

Policy Notifications

Automated policy updates delivered to Slack channels with rich formatting and actionable buttons

JIRA Ticket Creation

One-click JIRA ticket creation from policy notifications with automated analysis

Knowledge Ingestion

Thread-based knowledge extraction and storage via @sammy mentions

​
Feature 1: Policy Notifications to Slack

​
Overview

Policy notifications automatically deliver policy updates to configured Slack channels when new policies are detected or updated. These notifications include rich formatting, actionable buttons, and country-specific team mentions.

​
User Experience

When a new policy is detected, a formatted notification appears in your designated Slack channel: 
📋 POLICY UPDATE    🇬🇧 United Kingdom    employment_law

*New UK Employment Policy: Remote Work Guidelines*

✅ Status: Active    ✓ Verified: High Confidence

📝 Summary:
The new UK Employment Policy establishes comprehensive guidelines for remote work 
arrangements, including eligibility criteria, equipment requirements, and performance 
expectations...

💼 Impact:
This policy affects all UK-based employees working remotely. Key changes include 
mandatory equipment audits, updated performance review cycles...

🔗 Sources:
• https://example.com/policy/remote-work-uk
• https://internal.wiki/remote-work-guidelines

[Create JIRA Ticket]  [View in Dashboard]

​
Features

Rich Formatting

Modern Slack Block Kit components with emojis, visual indicators, and hyperlinks

Smart Truncation

Long content automatically truncated with “See more…” links for readability

Country Mentions

Automatic tagging of country-specific teams based on policy jurisdiction

Actionable Buttons

Create JIRA tickets or view policies in dashboard with single click

​
How It Works

Policy Detection

New or updated policies are automatically detected by the system

Notification Delivery

Rich, formatted notification sent to your designated Slack channel

Team Alerts

Country-specific teams automatically mentioned for relevant policies

Take Action

Click “Create JIRA Ticket” or “View in Dashboard” to take immediate action
The notification channel can be configured in your Sammy Labs dashboard settings.

​
Use Cases

Get notified immediately when new policies are detected, with full context for compliance review and action.

​
Feature 2: JIRA Ticket Creation from Slack

​
Overview

Create JIRA tickets directly from Slack policy notifications with a single click. The system analyzes the policy in context, creates a JIRA ticket with analysis results, and sends confirmation back to Slack.

​
User Experience

Click Button

User clicks “Create JIRA Ticket” button on policy notification

Review Form

Modal opens with pre-filled policy data (summary, description, priority, custom fields)

Submit Request

User confirms settings and submits; receives ”⏳ Processing policy analysis…” message

Analysis Processing

System ingests thread, analyzes policy, and creates JIRA ticket with research

Confirmation

Slack thread receives ”✅ A Jira ticket has been created: [TICKET-URL]” message

​
What Happens Next

After you submit the JIRA ticket request:

Analysis Begins

The system analyzes the policy in context to gather relevant research and insights

JIRA Ticket Created

A JIRA ticket is automatically created with the analysis results attached

Confirmation Posted

You receive a confirmation message in the Slack thread with a link to the JIRA ticket
The entire process typically completes in under a minute. You’ll receive status updates in the Slack thread so you know exactly what’s happening.

​
Feature 3: Knowledge Ingestion via @sammy Mentions

​
Overview

Mention @sammy in any Slack thread to ingest the entire thread as knowledge. The system processes text, videos, and attachments, extracts structured information, and stores it in your organization’s knowledge layer.

​
User Experience

Simply mention the bot in any thread: 
User: @sammy process this thread

Bot: Got it! Your thread has been ingested to your knowledge layer.
Behind the scenes:
  • Complete thread is fetched from Slack
  • Videos are downloaded and analyzed
  • Text content is processed and structured
  • Memories are extracted and stored
  • Content becomes searchable in knowledge base

​
How It Works

Mention @sammy

Simply @mention SAMMY in any thread you want to capture

Instant Confirmation

SAMMY confirms immediately: “Got it! Your thread has been ingested…”

Content Processing

All thread messages, videos, and attachments are processed in the background

Knowledge Storage

Extracted knowledge becomes searchable in your organization’s knowledge base

​
Video Processing

When videos are detected in threads, the system performs advanced AI analysis:
Videos are analyzed using Vertex AI with a specialized documentation extraction prompt that identifies:
  • Product features and how-to guides
  • Technical documentation (APIs, SDKs)
  • Workflows and processes
  • Configuration and setup instructions
  • Business information (pricing, SLAs)
  • Policies and guidelines
  • Troubleshooting guides
Video Processing Steps:
  1. Detection - Videos in the thread are automatically identified
  2. Secure Processing - Videos are processed in secure, encrypted storage
  3. AI Analysis - Advanced AI extracts structured documentation from video content
  4. Cleanup - Temporary files are immediately deleted after processing
  5. Indexing - Extracted content becomes searchable in your knowledge base

​
Content Types Supported

Text Messages

All thread messages with author attribution and timestamps

Videos

MP4, MOV, and other formats with AI-powered content extraction

Attachments

Files and documents shared in thread

Links

URLs referenced in messages with context

​
What Gets Captured

Content Stored:
  • All thread messages with author attribution
  • Video transcripts and extracted insights
  • File attachments and shared documents
  • Links and references from the conversation
  • Full conversation context and threading
Privacy Options:
  • Internal - Accessible only within your organization
  • Public - Available in your organization’s public knowledge base
You control the privacy settings when ingesting content. Internal memories remain completely private to your organization.

​
Use Cases

@sammy after a meeting to capture discussion, decisions, and action items automatically

​
Example

User: @sammy process this thread

Thread Content:
├─ Message 1: "Here's how to enable 2FA..."
├─ Message 2: [Video: Product demo]
└─ Message 3: "The API endpoint is /api/v2/auth/2fa"

Bot: Got it! Your thread has been ingested to your knowledge layer.

What Happens:
├─ All 3 messages captured with full context
├─ Video analyzed and documentation extracted
└─ Everything becomes searchable in your knowledge base

​
Security & Data Protection

​
How We Keep Your Data Safe

Our integration implements enterprise-grade security to ensure your data remains protected and isolated:
Every Request is Verified
  • All Slack requests are cryptographically verified to ensure authenticity
  • Timestamp validation prevents replay attacks
  • Only legitimate requests from Slack are processed

​
Minimal OAuth Permissions

The Sammy Labs Slack integration follows the principle of least privilege, requesting only the absolute minimum permissions necessary for core functionality. We deliberately exclude permissions for private channels, DMs, and workspace-wide access.
Complete Slack App Manifest Scopes: 
{
  "scopes": {
    "bot": [
      "app_mentions:read",    // Only detect @SAMMY mentions
      "chat:write",           // Send responses in threads
      "files:read",           // Access shared files
      "channels:history"      // Read public channel messages (only where invited)
    ]
  }
}
What SAMMY Cannot Access:
  • Private channels (unless explicitly invited)
  • Direct messages or group DMs
  • Channels it has not been added to
  • Workspace user lists or admin functions
  • Ability to delete or modify messages

​
Exactly What SAMMY Can Access

What SAMMY will be able to view:
  • Messages in public channels where SAMMY has been explicitly added
  • @mentions of SAMMY in conversations
  • Files shared in channels and conversations SAMMY has access to
SAMMY can only access content in channels where it has been explicitly invited. It cannot see content in channels it hasn’t been added to.

​
Privacy Principles

User-Initiated Only

SAMMY only processes content when explicitly invoked by users via @mentions

No Background Monitoring

The bot never passively monitors conversations or logs content without explicit request

Explicit Consent

All processing requires explicit user action (button click or @mention)

Minimum Access

Only permissions essential for functionality are requested

​
Key Security Guarantees

No Auto-Join

SAMMY never automatically joins channels. It must be explicitly invited using /invite @SAMMY

No Unsolicited Messages

SAMMY only posts when responding to @mentions or sending requested notifications

User-Triggered Processing

Application logic only processes content when users explicitly invoke SAMMY

Transparent Operations

All SAMMY actions are visible in thread replies and audit logs
Critical Privacy Note: While Slack’s channels:history permission technically allows SAMMY to read messages in channels it’s added to, SAMMY’s application code is designed to only process and respond to explicit user interactions (@mentions, button clicks). SAMMY does not passively monitor, log, or process conversations in the background.

​
Data Handling & Privacy

Encrypted Storage

All your data is encrypted at rest using enterprise-grade encryption. Credentials and tokens are stored in secure vaults.

Secure Transmission

All communications between Slack and Sammy Labs use HTTPS/TLS encryption to protect data in transit.

Organization Isolation

Your organization’s data is completely isolated. No possibility of access by other organizations.

Temporary Processing

Files like videos are processed securely and immediately deleted from temporary storage after processing.

​
Installation & Setup

​
Getting Started

Installation requires Slack workspace administrator permissions and an active Sammy Labs organization account.

Start Installation

Navigate to your Sammy Labs dashboard, go to Integrations, and click “Add Slack Integration”

Authorize with Slack

Review the requested permissions on Slack’s authorization page and approve the integration

Automatic Configuration

The bot is automatically configured with your organization’s settings

Invite to Channels

Add SAMMY to specific channels using /invite @SAMMY where you want to use the features

Start Using

You’re ready to go! @mention SAMMY or receive policy notifications immediately

​
Configuring Channels

Set Your Notification ChannelConfigure which Slack channel receives policy notifications in your Sammy Labs dashboard under Settings > Integrations > Slack > Notification Channel.
Choose a channel dedicated to compliance or policy updates for best organization.

​
Frequently Asked Questions

Can SAMMY access all our Slack messages?No. The integration only processes messages in threads where it’s explicitly mentioned by users via @mentions. It never passively monitors conversations.How is our data isolated from other organizations?Complete isolation through database-level Row Level Security, separate encryption keys, organization-specific bot tokens, and multi-tenant architecture.Can we control what data is processed?Yes. Processing only occurs when users explicitly mention @sammy or click action buttons. No background monitoring or automatic processing occurs.

​
Getting Started

Ready to transform your Slack workspace into an intelligent knowledge and policy hub?

Install Slack Integration

Connect your Slack workspace to Sammy Labs in just a few clicks. Requires Slack admin permissions and an active organization account.
After installation, add the bot to your desired channels using /invite @SAMMY and configure your notification channel to start receiving policy updates.