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

package/lib/templates/content/search-modes/labs-features.md

@@ -0,0 +1,81 @@
+# Labs Features
+
+Yantra Labs is where we test experimental features before they're ready for general release. Get early access to cutting-edge capabilities and help shape the future of Yantra.
+
+---
+
+## What is Yantra Labs?
+
+Labs is an opt-in program that gives you access to features still in development. These features may be:
+
+- **Experimental** — New capabilities being tested for the first time.
+- **Beta** — Features that work well but are being refined based on user feedback.
+- **Preview** — Nearly finished features that will soon graduate to general availability.
+
+> **Note:** Labs features may change, break, or be removed without notice. They're not covered by our SLA.
+
+---
+
+## Current Labs Features
+
+| Feature                   | Status       | Description                                                            |
+| ------------------------- | ------------ | ---------------------------------------------------------------------- |
+| **Voice Search**          | Beta         | Ask questions using voice input on desktop and mobile                  |
+| **Multi-modal Analysis**  | Experimental | Upload images and get AI analysis alongside text                       |
+| **Collaborative Threads** | Beta         | Multiple users can contribute to the same research thread in real-time |
+| **Custom AI Personas**    | Preview      | Create specialized AI personas with custom instructions and knowledge  |
+| **Canvas Mode**           | Experimental | Visual workspace for organizing search results and notes spatially     |
+
+_This list is updated as features are added or graduated._
+
+---
+
+## Enabling Labs Features
+
+1. Go to **Settings > Labs**.
+2. Browse available experimental features.
+3. Toggle on the features you want to try.
+4. Some features may require additional permissions or a specific plan tier.
+
+### Disabling
+
+Toggle any Labs feature off at any time. Your data from the feature is preserved for 30 days in case you re-enable it.
+
+---
+
+## How to Give Feedback
+
+Your feedback directly influences which Labs features become permanent:
+
+### In-app feedback
+
+Every Labs feature has a **feedback button** (💬) in its interface. Click it to:
+
+- Report a bug
+- Suggest an improvement
+- Rate your experience (1–5 stars)
+
+### Labs community
+
+Join the **#labs** channel in the Yantra community Discord to:
+
+- Discuss experimental features with other users
+- Share your use cases and workflows
+- Get tips from the Yantra team on getting the most out of new features
+
+---
+
+## Feature Graduation
+
+When a Labs feature reaches maturity:
+
+1. **Announcement** — We publish a blog post and in-app notification.
+2. **Migration** — Your data and settings carry over automatically.
+3. **SLA coverage** — Graduated features are covered by our standard uptime SLA.
+4. **Labs toggle removed** — The feature moves to its permanent location in the product.
+
+---
+
+## Availability
+
+Labs access is available on all plans. Some individual features may require Pro or higher due to infrastructure costs.

package/lib/templates/content/search-modes/pro-search.md

@@ -0,0 +1,75 @@
+# Pro Search
+
+Pro Search is Yantra's enhanced search mode — delivering deeper analysis, more sources, and smarter follow-ups than Regular search.
+
+---
+
+## What Pro Search Does Differently
+
+| Feature             | Regular Search              | Pro Search                                       |
+| ------------------- | --------------------------- | ------------------------------------------------ |
+| Response depth      | Quick, concise answers      | Detailed analysis with multiple angles           |
+| Sources consulted   | 5–10                        | 10–20                                            |
+| Follow-up questions | Basic suggestions           | Context-aware, multi-layered follow-ups          |
+| Response time       | 1–3 seconds                 | 5–10 seconds                                     |
+| Context window      | 50K tokens                  | 100K tokens                                      |
+| Best for            | Quick lookups, simple facts | Multi-step questions, comparisons, how-to guides |
+
+---
+
+## When to Use Pro Search
+
+### Ideal use cases
+
+- **Comparisons** — "Compare PostgreSQL and MongoDB for a high-write analytics workload"
+- **How-to guides** — "How do I set up CI/CD with GitHub Actions for a monorepo?"
+- **Multi-part questions** — "What are the pros and cons of serverless, and when should I avoid it?"
+- **Detailed explanations** — "Explain how TLS 1.3 handshake works step by step"
+- **Analysis** — "What caused the 2023 banking crisis and what are the long-term implications?"
+
+### When Regular Search is better
+
+- Quick facts ("population of Canada")
+- Definitions ("what is a mutex?")
+- Simple lookups ("React 19 release date")
+
+---
+
+## How to Activate
+
+### On-demand
+
+Click the **Pro** toggle below the search bar before submitting your query.
+
+### As default
+
+Set Pro Search as your default mode:
+
+**Settings > Preferences > Search > Default search mode** → Pro Search
+
+### Via keyboard
+
+Press ⌘ + P (Mac) or Ctrl + P (Windows) to toggle Pro Search on/off before searching.
+
+---
+
+## Pro Search Workflow
+
+1. **You ask a question.**
+2. **Yantra plans its approach** — You'll see a brief "thinking" indicator showing what sub-questions the AI is exploring.
+3. **Sources are fetched and analyzed** — More sources are consulted than in Regular mode.
+4. **A structured response is generated** — With clear sections, bullet points, and inline citations.
+5. **Smart follow-ups are suggested** — Based on what angles weren't fully covered.
+
+> **Transparency:** Pro Search shows you which sources it consulted and why it prioritized certain results.
+
+---
+
+## Availability
+
+| Plan       | Pro Search queries                 |
+| ---------- | ---------------------------------- |
+| Free       | 5 per day                          |
+| Pro        | Unlimited                          |
+| Team       | Unlimited for all members          |
+| Enterprise | Unlimited with priority processing |

package/lib/templates/content/search-modes/regular-search.md

@@ -0,0 +1,86 @@
+# Regular Search
+
+Regular Search is Yantra's default mode — designed for fast, accurate answers to everyday questions with real-time source citations.
+
+---
+
+## How It Works
+
+1. **Type your question** in natural language or keywords.
+2. **Yantra processes** your query using hybrid search (keyword + semantic).
+3. **Results are generated** in 1–3 seconds with inline source citations.
+4. **Follow-up** with additional questions to refine or go deeper.
+
+---
+
+## What You Get
+
+### AI-generated answer
+
+A concise, direct response synthesized from multiple sources. Key facts are cited with numbered references you can click to verify.
+
+### Source cards
+
+Below the answer, expandable source cards show:
+
+| Field     | Description                                                  |
+| --------- | ------------------------------------------------------------ |
+| Title     | The page or article title                                    |
+| Domain    | Source website                                               |
+| Date      | When the content was published or last updated               |
+| Snippet   | The specific passage that supports the answer                |
+| Relevance | A score indicating how closely the source matches your query |
+
+### Suggested follow-ups
+
+2–4 suggested follow-up questions help you explore the topic further without having to formulate queries from scratch.
+
+---
+
+## Daily Limits by Plan
+
+| Plan       | Searches per day | Real-time sources | AI model                    |
+| ---------- | ---------------- | ----------------- | --------------------------- |
+| Free       | 20               | 5                 | GPT-4o mini                 |
+| Pro        | Unlimited        | 10                | GPT-4o or Claude 3.5 Sonnet |
+| Team       | Unlimited        | 10 per member     | GPT-4o or Claude 3.5 Sonnet |
+| Enterprise | Unlimited        | 20                | Any available model         |
+
+---
+
+## Tips for Better Results
+
+### Be specific
+
+Instead of:
+
+> "Tell me about databases"
+
+Try:
+
+> "What are the main differences between PostgreSQL and MySQL for web applications?"
+
+### Include context
+
+Instead of:
+
+> "How to fix the error?"
+
+Try:
+
+> "How to fix 'ECONNREFUSED' error when connecting to PostgreSQL from a Docker container?"
+
+### Use natural language
+
+You don't need to use search-engine-style keywords. Yantra understands full sentences, questions, and even casual phrasing.
+
+---
+
+## When to Upgrade to Pro Search
+
+Regular Search is ideal for quick lookups and straightforward questions. Consider switching to [Pro Search](/help-center/search-modes/pro-search) when:
+
+- You need a detailed, multi-angle analysis
+- Your question has multiple parts
+- You want more sources and deeper citations
+- You need a comprehensive how-to guide

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