@adminide-stack/yantra-help-browser 12.0.16-alpha.20 → 12.0.16-alpha.21

package/lib/templates/content/platform-features/platform-overview.md

@@ -0,0 +1,58 @@
+# Yantra Platform Overview
+
+Yantra is an **AI-powered workforce platform** that deploys intelligent AI employees into your existing toolchain. Unlike traditional chatbots that wait for prompts, Yantra AI employees operate proactively — monitoring your communication channels, development pipelines, CRM systems, and project management tools around the clock.
+
+## Why Yantra Exists
+
+Modern teams lose significant productivity to repetitive operational tasks:
+
+- **Context fragmentation**: Critical information is scattered across dozens of tools
+- **Manual data entry**: Teams spend hours updating CRMs, logging notes, and syncing systems
+- **Knowledge silos**: When team members leave or switch projects, institutional knowledge disappears
+- **Alert overload**: Engineers, salespeople, and marketers drown in notifications without clear prioritization
+
+Yantra solves these problems by providing AI employees that integrate directly into your workflow and handle operational overhead autonomously.
+
+## Core Philosophy
+
+### Proactive, Not Reactive
+
+Traditional AI assistants answer when asked. Yantra AI employees **watch, learn, and act** without waiting for instructions. They surface issues before they escalate, update systems before data goes stale, and share context before you need to ask.
+
+### Gradual Trust Model
+
+Every Yantra AI employee starts in supervised mode. You review and approve all actions. Over time, as trust builds, you can grant more autonomy — letting the AI employee handle routine tasks independently while escalating only the important decisions.
+
+### Built on OpenClaw
+
+Yantra is built on top of [OpenClaw](https://github.com/openclaw), a battle-tested open-source AI agent framework. This means transparent, auditable AI behavior backed by a thriving community of contributors and enterprise users.
+
+## What Yantra AI Employees Can Do
+
+| Capability                      | Description                                                |
+| ------------------------------- | ---------------------------------------------------------- |
+| **Continuous Monitoring**       | Watch Slack, GitHub, error trackers, CRMs, and email 24/7  |
+| **Contextual Correlation**      | Connect data points across tools to surface insights       |
+| **Automated Actions**           | Update CRMs, create tickets, draft messages, and log notes |
+| **Intelligent Alerting**        | Filter noise and escalate only what matters                |
+| **Institutional Memory**        | Capture and recall every interaction, decision, and fix    |
+| **Multi-Channel Communication** | Interact via Slack, WhatsApp, Telegram, or email           |
+
+## Who Uses Yantra
+
+- **Engineering Teams**: Monitor errors, correlate bugs with deployments, maintain institutional knowledge
+- **Sales Teams**: Auto-update CRMs, prepare call briefs, ensure 100% follow-up on leads
+- **Marketing Teams**: Manage social media presence, draft content from product updates, track brand mentions
+- **Support Teams**: Route issues proactively, surface relevant context for customer problems
+- **Operations Teams**: Keep systems synchronized and teams informed
+
+## Getting Started
+
+Setting up Yantra takes approximately 5 minutes:
+
+1. **Connect your tools** — One-click OAuth for Slack, GitHub, HubSpot, Sentry, Linear, Gmail, and 40+ more
+2. **Configure preferences** — Define what your AI employee should watch for and how to prioritize
+3. **Start supervised** — Review and approve all AI actions to build trust
+4. **Expand autonomy** — Gradually let your AI employee work independently on routine tasks
+
+For detailed setup instructions, see the [Getting Started Guide](/help-center/ai-employees/getting-started-ai-employees).

package/lib/templates/content/platform-features/proactive-alerts.md

@@ -0,0 +1,88 @@
+# Proactive Alerts — Know Before It Escalates
+
+Yantra AI employees don't wait for you to discover problems — they detect issues early and notify you with full context, so you can respond before situations escalate.
+
+## How Proactive Alerts Work
+
+Your AI employee continuously analyzes events across all connected tools, looking for patterns and anomalies that indicate something needs attention. When it detects an issue, it:
+
+1. **Correlates the signal** with data from other tools to understand the full scope
+2. **Checks for existing responses** — whether someone is already handling it or a ticket exists
+3. **Assesses severity** based on your configured thresholds and historical patterns
+4. **Delivers a contextualized alert** with all relevant information and suggested actions
+
+## Alert Types
+
+### Error Spike Alerts
+
+When your error monitoring tool (Sentry, Datadog, etc.) shows an unusual increase in exceptions, your AI employee investigates:
+
+- Identifies the root error and affected components
+- Checks if the spike correlates with a recent deployment
+- Looks for existing tickets or ongoing fixes
+- Notifies the appropriate team with a complete summary
+
+### Customer Impact Alerts
+
+When multiple customers report similar issues or a high-value account encounters a problem:
+
+- Cross-references support channels with technical monitoring
+- Surfaces the customer's history and account importance
+- Suggests response templates based on similar past incidents
+
+### Stale Activity Alerts
+
+When important items stop progressing:
+
+- Deals that haven't been updated in your CRM
+- Pull requests awaiting review beyond your team's SLA
+- Support tickets approaching response time limits
+
+### Anomaly Alerts
+
+When metrics deviate from normal patterns:
+
+- Unusual traffic patterns or usage drops
+- Unexpected changes in deployment frequency
+- Communication volume spikes in specific channels
+
+## Smart Escalation
+
+Not every alert deserves your attention. Yantra uses **smart escalation** to ensure you only get interrupted when it genuinely matters:
+
+### Severity Classification
+
+- **Informational**: Logged for reference, included in daily briefings
+- **Low**: Batched and delivered at your preferred check-in times
+- **Medium**: Delivered promptly but not urgently
+- **High**: Immediate notification through your preferred channel
+- **Critical**: Multi-channel notification with escalation chain
+
+### Escalation Rules
+
+You define what constitutes each severity level:
+
+- Error count thresholds (e.g., 50+ occurrences in 1 hour = Critical)
+- Customer tier triggers (e.g., Enterprise account issues always escalate)
+- Time-based rules (e.g., P0 tickets unresponded after 15 minutes)
+- Custom keyword triggers (e.g., "data loss", "security breach")
+
+## Configuring Alerts
+
+Navigate to your AI employee's preferences to set:
+
+- **Notification channels**: Where alerts get delivered (Slack, email, WhatsApp, Telegram)
+- **Quiet hours**: When to batch non-critical alerts
+- **Escalation chains**: Who gets notified if the primary responder doesn't acknowledge
+- **Alert suppression**: Rules to prevent duplicate or noise alerts
+
+## Alert History
+
+All alerts are logged with:
+
+- Timestamp and severity
+- Full context at the time of alerting
+- Actions taken (by the AI employee or team members)
+- Resolution status and timeline
+
+This history helps refine alert thresholds over time and provides data for post-incident reviews.

package/lib/templates/content/platform-features/smart-escalation.md

@@ -0,0 +1,93 @@
+# Smart Escalation — Only Get Pinged When It Matters
+
+Yantra's smart escalation system ensures you're only interrupted for issues that truly require your attention, filtering out noise while never missing critical events.
+
+## The Noise Problem
+
+Modern development and business teams are overwhelmed by notifications:
+
+- Hundreds of Slack messages daily
+- Dozens of error alerts, most of which are duplicates or low priority
+- CRM notifications for routine stage changes
+- Email threads that don't require immediate action
+
+This constant noise creates **alert fatigue**, causing teams to miss genuinely important issues buried in the flood. Yantra solves this by acting as an intelligent filter between your tools and your attention.
+
+## How Smart Escalation Works
+
+### 1. Signal Analysis
+
+Every event from your connected tools is analyzed for:
+
+- **Severity**: How impactful is this event?
+- **Novelty**: Is this a new issue or a known one being tracked?
+- **Scope**: How many users, customers, or systems are affected?
+- **Trend**: Is this getting better or worse?
+
+### 2. Context Enrichment
+
+Before escalating, your AI employee gathers full context:
+
+- Related events from other tools
+- Historical data on similar issues
+- Current status of any existing responses
+- Who is available and responsible for this type of issue
+
+### 3. Decision Logic
+
+Based on your configured rules and the enriched context, Yantra decides:
+
+- **Absorb silently**: Log it, include in daily summary
+- **Batch for later**: Group with related items for periodic review
+- **Notify gently**: Send a non-urgent message at your next check-in
+- **Escalate immediately**: Push a notification through your preferred urgent channel
+- **Trigger escalation chain**: If no response within the defined window, escalate to the next person
+
+## Escalation Configuration
+
+### Threshold-Based Rules
+
+```
+Error Count Rules:
+  - Less than 5 occurrences → Log only
+  - 5-25 occurrences → Batch notification
+  - 25-100 occurrences → Immediate notification
+  - 100+ occurrences → Critical escalation chain
+```
+
+### Customer Tier Rules
+
+- **Enterprise accounts**: All issues escalated immediately
+- **Pro accounts**: P0/P1 issues escalated, others batched
+- **Free accounts**: Included in daily summaries
+
+### Time-Based Rules
+
+- **Business hours**: Standard escalation flow
+- **Off hours**: Only critical issues escalate; everything else queued for morning
+- **Weekends**: Emergency-only escalation with higher thresholds
+
+## Escalation Chains
+
+Define cascading notification paths for critical issues:
+
+1. **Primary responder**: Notified first via Slack and email
+2. **Backup responder**: Notified after 10 minutes if no acknowledgment
+3. **Team lead**: Notified after 20 minutes if still unacknowledged
+4. **On-call manager**: Final escalation for sustained non-response
+
+## Feedback Loop
+
+Yantra learns from your responses to refine escalation over time:
+
+- If you consistently dismiss certain alert types, it adjusts thresholds
+- If you escalate items that were batched, it increases their priority
+- Monthly escalation reports help you tune your rules
+
+## Getting Started
+
+1. Connect your tools via [Integrations](/help-center/integrations/integrations-overview)
+2. Set your default escalation preferences in the AI employee configuration
+3. Define customer tiers and priority thresholds
+4. Specify quiet hours and escalation chains
+5. Review and refine based on the weekly escalation summary

package/lib/templates/content/security-compliance/audit-trail.md

@@ -0,0 +1,112 @@
+# Audit Trail
+
+Every action taken by a Yantra AI employee is comprehensively logged, providing full transparency and accountability for compliance, debugging, and trust-building purposes.
+
+## What Gets Logged
+
+### Event Processing
+
+- Every event received from connected tools
+- How the event was classified and prioritized
+- Which correlations were made with other data sources
+- Time to process and resulting decisions
+
+### Actions Taken
+
+- **Informational**: Morning briefings, context summaries, status updates
+- **Alerts**: Notifications sent to team members with severity context
+- **Updates**: CRM field changes, ticket updates, status modifications
+- **Creations**: New tickets, contacts, or records created
+- **Drafts**: Messages and content drafted for approval
+- **Escalations**: Issues routed to humans for decision
+
+### Approval Workflow
+
+- Actions drafted and presented for approval
+- Approval, edit, or rejection decisions by human reviewers
+- Time from draft to action for each item
+- Modification details when actions are edited before approval
+
+## Log Structure
+
+Each audit log entry contains:
+
+| Field               | Description                                                   |
+| ------------------- | ------------------------------------------------------------- |
+| **Timestamp**       | Precise UTC timestamp of the action                           |
+| **Action ID**       | Unique identifier for the action                              |
+| **Action Type**     | Category (inform, alert, update, create, draft, escalate)     |
+| **Target Tool**     | Which integration was affected (Slack, HubSpot, GitHub, etc.) |
+| **Target Resource** | Specific resource (channel, deal, issue, etc.)                |
+| **Trigger**         | What event or condition triggered the action                  |
+| **Context**         | Data from other tools that informed the decision              |
+| **Previous Value**  | State before the action (for updates)                         |
+| **New Value**       | State after the action                                        |
+| **Approval Status** | Auto-approved, human-approved, human-edited, or rejected      |
+| **Approver**        | Who approved the action (if human-approved)                   |
+| **Outcome**         | Success, failure, or pending                                  |
+
+## Accessing Audit Logs
+
+### Dashboard
+
+Navigate to **AI Employee → Audit Trail** in your Yantra dashboard:
+
+- Filter by date range, action type, target tool, or approval status
+- Search for specific resources, actions, or keywords
+- Export logs in CSV or JSON format
+- Visualize action patterns over time
+
+### API Access
+
+Enterprise customers can access audit logs programmatically:
+
+- REST API for log retrieval and filtering
+- Webhook notifications for real-time log streaming
+- Integration with external SIEM tools
+- Scheduled export for compliance archives
+
+## Compliance Use Cases
+
+### SOC 2 Audit Support
+
+Audit logs provide evidence for SOC 2 controls:
+
+- Access control effectiveness
+- Change management procedures
+- Incident response documentation
+- Data handling compliance
+
+### GDPR Compliance
+
+For data subject requests:
+
+- Identify all data processed for a specific individual
+- Document the legal basis for each processing activity
+- Provide evidence for data processing inventories
+- Support right-to-erasure request fulfillment
+
+### Internal Review
+
+Regular audit log review helps:
+
+- Verify AI employee behavior meets expectations
+- Identify areas for configuration improvement
+- Detect unusual patterns or potential security issues
+- Build confidence in AI employee autonomy
+
+## Retention
+
+### Log Retention Periods
+
+- **Action logs**: Retained for 12 months by default (configurable)
+- **Approval records**: Retained for 24 months
+- **Security events**: Retained for 36 months
+- **Custom retention**: Enterprise customers can configure custom retention periods
+
+### Deletion
+
+- Logs are purged automatically after retention period expires
+- Customers can request early deletion in writing
+- Deletion is permanent and irreversible
+- Deletion confirmation provided for compliance records

package/lib/templates/content/security-compliance/compliance.md

@@ -0,0 +1,120 @@
+# Compliance and Certifications
+
+Yantra maintains rigorous compliance standards to meet the security and regulatory requirements of enterprise customers across industries.
+
+## Standards and Certifications
+
+### SOC 2 Type II
+
+- Annual third-party audit covering Security, Availability, and Confidentiality trust principles
+- Report available to customers under NDA
+- Continuous monitoring of SOC 2 controls
+- Remediation tracking for any identified findings
+
+### GDPR (General Data Protection Regulation)
+
+Yantra's GDPR compliance covers:
+
+- **Lawful basis**: Clear legal basis for all data processing
+- **Data minimization**: Only collecting and processing data necessary for service delivery
+- **Right to access**: Customers can request export of all their data
+- **Right to erasure**: Complete data deletion upon request
+- **Data portability**: Standard format data export available
+- **Data protection officer**: Designated DPO for privacy oversight
+- **Data processing agreements**: Available for all customers
+
+### CCPA (California Consumer Privacy Act)
+
+- Right to know what data is collected and how it's used
+- Right to delete personal information
+- Right to opt out of data sharing
+- No sale of personal information — ever
+
+### Additional Compliance Support
+
+- **HIPAA**: Business Associate Agreement available for healthcare customers (enterprise plan)
+- **ISO 27001**: Security management practices aligned with ISO 27001 framework
+- **PCI DSS**: Payment data never touches Yantra systems (handled by payment processor)
+- **FERPA**: Available for educational institution customers
+
+## Data Processing
+
+### Data Processing Agreement (DPA)
+
+Available for all customers, covering:
+
+- Nature and purpose of data processing
+- Categories of personal data processed
+- Technical and organizational measures
+- Sub-processor management and notification
+- Data breach notification procedures
+- Data return and deletion upon termination
+
+### Sub-Processors
+
+Yantra uses a limited number of sub-processors:
+
+- Cloud infrastructure providers (SOC 2 certified)
+- AI model providers (with strict data usage restrictions)
+- Payment processors (PCI DSS compliant)
+- Analytics tools (privacy-first, no personal data shared)
+
+A current list of sub-processors is maintained and customers are notified of changes.
+
+### Data Residency
+
+- **Default**: US-based infrastructure (US-East and US-West)
+- **EU**: Available for customers requiring EU data residency
+- **Additional regions**: Available on enterprise plans
+- No data transfer outside specified regions without written consent
+
+## Privacy by Design
+
+### Minimal Data Collection
+
+- Only data necessary for service delivery is collected
+- No data collection for marketing or advertising purposes
+- No data shared with or sold to third parties
+- AI model providers do not retain customer data
+
+### Data Lifecycle Management
+
+1. **Collection**: Minimum necessary data collected during integration
+2. **Processing**: Data processed within isolated customer environments
+3. **Storage**: Encrypted storage with customer-specific keys
+4. **Retention**: Configurable retention periods (default: 12 months)
+5. **Deletion**: Automatic deletion after retention period; manual deletion on request
+
+## Security Assessments
+
+### Penetration Testing
+
+- Annual penetration tests by independent security firms
+- Results reviewed and remediated promptly
+- Summary available to enterprise customers under NDA
+
+### Vulnerability Management
+
+- Automated vulnerability scanning for all components
+- Dependency scanning for known CVEs
+- Patch management SLA: Critical (24h), High (72h), Medium (7d)
+- Bug bounty program for responsible vulnerability disclosure
+
+### Business Continuity
+
+- Disaster recovery plan tested quarterly
+- Business impact analysis reviewed annually
+- Incident response plan documented and rehearsed
+- Communication plan for security events
+
+## Requesting Compliance Documents
+
+Enterprise customers can request:
+
+- SOC 2 Type II report
+- Penetration test summary
+- Data processing agreement
+- Security architecture white paper
+- Sub-processor list
+
+Contact your account manager or email security@yantra.ai to request any compliance documentation.

package/lib/templates/content/security-compliance/data-encryption.md

@@ -0,0 +1,94 @@
+# Data Encryption
+
+Yantra employs multiple layers of encryption to protect your data at every stage — in transit, at rest, and during processing.
+
+## Encryption in Transit
+
+### TLS Configuration
+
+- All connections use **TLS 1.2 or higher**
+- TLS 1.0 and 1.1 are disabled across all endpoints
+- Strong cipher suites only — weak ciphers are explicitly blocked
+- Perfect Forward Secrecy (PFS) enabled on all connections
+- HSTS headers enforced with long max-age values
+
+### What's Encrypted in Transit
+
+- API requests between your tools and the Yantra Gateway
+- Internal communication between Yantra components
+- Data sent to and received from AI model providers
+- Dashboard access and administrative API calls
+- Webhook payloads from integrated tools
+
+## Encryption at Rest
+
+### Storage Encryption
+
+- All persistent data encrypted using **AES-256** encryption
+- Database-level encryption enabled for all data stores
+- File system encryption on all VM storage volumes
+- Backup data encrypted with the same standards as primary data
+
+### Key Management
+
+- Encryption keys managed through a dedicated **Key Management Service (KMS)**
+- Customer-specific keys isolate each tenant's data
+- Keys are rotated on a regular schedule (quarterly minimum)
+- Key access is logged and auditable
+- Emergency key revocation procedures tested quarterly
+
+## Credential Management
+
+### OAuth Tokens
+
+- OAuth access and refresh tokens stored in encrypted secret vaults
+- Token encryption uses separate keys from data encryption
+- Tokens are scoped to minimum required permissions
+- Token refresh is handled automatically and securely
+
+### API Keys
+
+- API keys encrypted at rest using dedicated key encryption keys
+- Keys are never stored in plaintext anywhere in the system
+- API key rotation supported without service interruption
+- Compromised keys can be revoked instantly
+
+### What We Never Store
+
+- Your tool passwords (OAuth is used instead)
+- Credit card numbers (handled by payment processor)
+- Raw authentication credentials
+- Secrets in application logs or error reports
+
+## Processing Security
+
+### In-Memory Protection
+
+- Sensitive data in processing memory is cleared after use
+- Memory isolation between customer workloads via VM separation
+- No swap-to-disk of sensitive in-memory data
+
+### AI Model Interactions
+
+- Prompts sent to AI models are encrypted in transit
+- No customer data is retained by model providers for training
+- Model provider connections use dedicated, authenticated channels
+- Prompts are constructed to minimize exposure of sensitive information
+
+## Verification
+
+### How to Verify
+
+- Check TLS configuration: Our endpoints pass SSL Labs A+ rating
+- Request our latest SOC 2 report for encryption control details
+- Audit logs show encryption status for all data operations
+- Penetration test results available for enterprise customers upon NDA
+
+### Compliance Alignment
+
+Our encryption practices align with:
+
+- **NIST 800-171**: Encryption requirements for controlled data
+- **ISO 27001**: Information security management standards
+- **PCI DSS**: Payment card industry data security standards
+- **FIPS 140-2**: Federal information processing standards