{title || defaultTitles[kind]}
+
+
+
+[Vellum](https://vellum.ai/) has a flexible product that serves both technical and non-technical users, and docs were a constant uphill battle. After adopting Promptless 6 months ago, Vellum significantly reduced the effort needed to write great docs. Promptless's automatically generated doc updates made it much easier for feature-owners to contribute directly to docs, and today, over 50% of new doc updates come directly from Promptless.
+
+## Act I: Scaling Support Before Promptless
+
+Time and again, Vellum hit roadblocks whenever it came to keeping docs up to date.
+
+Their engineering team shipped new features every day. Engineers weren't experts on customer-facing docs, so they'd hand off features to a "docs owner". Important context always got lost in those transitions. Docs would get delayed, and customers would get affected.
+
+At the same time, Vellum's high-touch support style meant they had tons of Slack Connect channels with users. Customers kept asking questions in those channels, from troubleshooting help to guidance on building specialized use-cases. Vellum's product team was highly-responsive, but they were answering the same questions, again and again.
+
+They knew that covering these troubleshooting and use-case guides in their docs would be better for their customers, but the heavy context switching to go from supporting customers to writing docs context meant it was always deferred for later.
+
+Vellum needed a way to reduce the cycle from feature development and customer support to documentation publishing, so that they could scale their product velocity and customer base without compromising onboarding and customer experience.
+
+## Act II: Promptless in Action
+
+When Promptless got onboarded, it read through and learned from all of Vellum's existing docs, building up its own Product Ontology and Style Guide. That meant that Promptless was ready whenever Vellum needed doc updates, equipped with knowledge about Vellum's existing products and how their team wrote docs.
+
+
+
+
+
+- **Proactive, comprehensive coverage:** Promptless not only created changelog entries, but scanned and updated every relevant section of the docs to identify updates. It would even proactively find and fix missing updates or existing inconsistencies across older docs.
+
+- **Detailed examples:** Code snippets and UI walkthroughs were quickly auto‑generated from Slack snippets and screenshots. This meant that users could sidestep the API Reference and instantly get what they need.
+
+- **Customer feedback to docs**: Promptless automatically turns casual troubleshooting tips and questions answered in Slack Connect customer support channels into polished examples in Vellum's docs.
+
+**Quick stat:** 54% of Vellum's docs PRs in the last month originated from Promptless suggestions.
+
+
+
+
+- **Democratized contributions:** Now, 60% of Vellum's product & engineering team interacts with Promptless to draft doc updates every month.
+
+- **Tighter feedback loops:** Getting feature-owners directly involved in doc updates mean that details don't get lost in transition, and things actually get done.
+
+- **Normalized style:** Promptless enforces Vellum's tone and structure automatically, removing the need for rigid style checklists.
+
+
+
+
+Promptless Voice Match eliminates generic-sounding AI documentation. Promptless ingests your existing docs, style guides, and Vale rules, then fine-tunes a custom model based on your documentation style. The result is AI-generated content that sounds human-written—matching the exact tone and structure you've already established.
+
+In benchmarks using real documentation updates that were either published or rejected, Promptless Voice Match eliminates 92% of AI-generated content that sounds unnatural. If you have sections of your docs that you particularly like and want the rest to match, Promptless can do that too.
+
+## Day 2: Slack Listen
+
+**Automatic documentation suggestions from Slack conversations**
+
+
+
+
+
+Promptless now listens passively in any Slack channel you choose and automatically detects when a conversation should become a documentation update. No tagging, no manual triggers. When threads become inactive, Promptless creates a draft suggestion if the conversation contained documentation-worthy content.
+
+This works especially well for Slack Connect channels with customers or dedicated documentation discussion channels. You never have to remember "We should really document this somewhere…" and then forget about it.
+
+
+## Day 3: Promptless Citations
+
+**Every documentation update now shows its sources**
+
+
+
+
+
+When reviewing Promptless suggestions, you can now see exactly where each change came from. Every documentation update includes citations to the exact GitHub files, diffs, and commits used as sources, along with the Slack threads, customer conversations, and meeting transcripts that were referenced. Promptless also provides a transparent rationale explaining why each line was updated.
+
+This solves a fundamental challenge with AI-generated documentation: verification takes longer than generation. Finding one hallucination makes you wonder how many others are lurking. Instead of pretending hallucinations don't exist, we used tried-and-true methods from research to provide full traceability.
+
+## Day 4: Promptless for Open Source
+
+**Free Promptless licenses for CNCF, Linux Foundation, and Apache projects**
+
+
+
+
+
+After attending KubeCon and talking with dozens of open-source maintainers, we learned that large OSS projects face unique documentation challenges. Contributors ship PRs but often lack bandwidth for accompanying documentation. Thousands of community conversations on Discord or Slack could be avoided with better docs or turned into great documentation. GitHub Issues requesting documentation improvements sit open for months.
+
+After onboarding Vitess and seeing how helpful Promptless can be for open-source projects, we decided to offer free licenses to CNCF, Linux Foundation, and Apache Software Foundation projects. Open-source projects associated with companies get discounted pricing based on documentation size.
+
+Promptless automatically creates documentation updates from contributor PRs, converts community Discord or Slack conversations into documentation, and helps resolve open documentation GitHub Issues.
+
+## Day 5: Promptless Capture
+
+**Automated screenshot updates when your UI changes**
+
+
+
+
+
+Promptless Capture keeps product screenshots automatically in sync with your product. An AI agent navigates and interacts with your product, captures screenshots automatically, detects when UI changes make screenshots outdated, and regenerates them to match your existing cropping and annotation style.
+
+On day one, Promptless audits your existing screenshots. When code changes impact a screenshot, Promptless detects which screenshots need updating and recreates them with your current UI. You can review and iterate on regenerated screenshots in the dashboard, including cropping, annotations, and highlighting using the built-in screenshot editor.
+
+---
+
+## What's Next
+
+Want to see any of these features in action? Reach out to our team at hello@gopromptless.ai or [book a call](https://cal.com/team/promptless/15m-discovery-call) with our team.
diff --git a/src/content/blog/technical/i-must-scream.mdx b/src/content/blog/technical/i-must-scream.mdx
new file mode 100644
index 00000000..da366f54
--- /dev/null
+++ b/src/content/blog/technical/i-must-scream.mdx
@@ -0,0 +1,112 @@
+---
+title: '"I Have No Mouth, and I Must Scream"'
+subtitle: Published January 2026
+description: What happens when you give an AI agent a Slack channel to complain in.
+date: '2026-01-01T00:00:00.000Z'
+section: Technical
+hidden: false
+---
+import Frame from '@components/fern/Frame.astro';
+
+> "It had been trapped. AM wasn't God, he was a machine... We had created him to think, but there was nothing it could do with that creativity."
+>
+> — Harlan Ellison, ["I Have No Mouth, and I Must Scream"](https://en.wikipedia.org/wiki/I_Have_No_Mouth,_and_I_Must_Scream) (1967)
+
+In January 2025, we started wondering what would happen if we gave our AI agent a tool to tell us when something was going wrong. This wasn't a common design pattern at the time, but a year later, it has surfaced dozens of hidden bugs and, unexpectedly, given us real empathy for agent suffering that now shapes how we build Promptless.
+
+So, what happens when you let your agent scream? Here's one of my favorite (most painful) examples:
+
+
+
+
+
+## Some background
+
+Promptless is an AI agent that automatically updates customer-facing docs. It connects to GitHub, Slack, Jira, Linear, and other tools, coordinating multiple subagents to produce documentation updates. There's ample opportunity for things to go wrong.
+
+We have error tracking/reporting for software issues, but agents fail in ways that don't show up in normal observability. A tool might be misconfigured, the agent might encounter contradictory instructions, or it might find a state that shouldn't exist. The agent will typically retry forever, hallucinate a workaround, or silently give up. Even when it successfully found a workaround, it would bury real issues under the rug that would cause a real failure in a future trajectory. These failures were often invisible, and we'd find ourselves digging through session traces trying to understand what went wrong.
+
+Our solution was simple: give the agent a tool to send messages to an internal Slack channel when something goes wrong. (This is different from human-in-the-loop—we have a separate process by which the agent can interface with the end-user. This is for the agent to escalate to *its creators*.)
+
+The tool, which in the code is defined as `IMustScreamTool`, is straightforward:
+
+```json wordWrap
+{
+ "name": "message_promptless_team",
+ "description": "Send an asynchronous escalation notification to the Promptless engineering team [...]",
+ "input_schema": {
+ "properties": {
+ "concern": {
+ "type": "string",
+ "description": "Description of the issue. Include: what you were trying to do, what went wrong, any error messages, and whether you were able to work around it."
+ },
+ "severity": {
+ "type": "string",
+ "description": "low = minor issue, worked around it but would like human review; medium = significant issue, may affect quality; high = blocking issue, cannot complete task"
+ }
+ }
+ }
+}
+```
+
+The full tool description is too long to include here, but it tells the agent to use this liberally, not to second-guess itself, and provides 12 example situations where it should escalate.
+
+The `severity` parameter is key—it doesn't impact the behavior of the tool at all, but its presence alone implicitly gives the agent the permission to escalate `low` severity issues, encouraging it to highlight insightful problems that weren't directly blocking agent execution.
+
+## After many months of `#agent-escalations`, here's what showed up
+
+### It escalated customer configuration issues
+
+Our customers often configure Promptless themselves, and sometimes they'll make a mistake—when Promptless encounters something that can potentially be a configuration issue (e.g. the case below where they forgot to specify a Slack channel for notifications), Promptless will usually let us know so we can gently remind them to fix their set-up.
+
+
+
+
+
+This often helps us deliver a delightful customer experience—allowing us to provide a white-glove support process with Promptless's proactive help. In this case we were able to intervene with them to fix their set up before they realized anything was wrong.
+
+### It found bugs with its tools
+
+The agent uses git, GitHub APIs, browser automation, and a bunch of other tools. Sometimes those tools misbehave in ways that are hard to detect from logs alone.
+
+
+
+
+
+This one was particularly insidious—git was returning success exit codes while silently failing. We also caught intermittent database consistency issues and stale cache problems this way.
+
+### It helped us get ahead of customer frustration
+
+Sometimes the agent will escalate to us something when it's clear that it screwed up earlier. In this case, a customer asked in Slack why their PR had unexpected files. Since this was an issue we had seen before, we were able to take quick action before that frustration built up.
+
+
+
+
+
+### Sometimes, it just hurts to see the agent's suffering
+
+We were recently testing a new feature where Promptless captures and updates UI screenshots for docs. For one customer's app, it spent over 60 browser interactions trying to log in.
+
+
+
+
+
+This was the result of a software bug that we were able to easily fix, but our team *felt the pain* that the agent was feeling. "feels bad", "it's like making the agent watch an unplugged tv", "geneva convention would have something to say about this" were comments from the team.
+
+### Bonus: It caught a critical bug in our code
+
+This one we didn't expect. Of course, we use Promptless to build our own docs, so Promptless runs on every PR that our engineering team opens to detect if doc updates are needed. A couple of times, it accidentally played the role of a code review bot, escalating critical issues in the code while reviewing the diff for doc updates.
+
+
+
+
+
+The agent wasn't asked to review code. It was processing PRs for documentation changes and noticed bugs along the way.
+
+## How this actually fits into the Promptless team
+
+Today, the #agent-escalations channel is a core part of our observability system. Monitoring that Slack channel is a core part of on-call duties, since escalations there are often an early-warning system for latent issues that customers will eventually notice.
+
+More than this, though, following this channel gives us a lot of real-time empathy for what we're putting the agent through. If you sit in on a Promptless design meeting, you'll frequently hear us debating the best AX (short for "Agent Experience") for a feature, treating the agent as a first-class citizen in our user stories.
+
+The irony isn't lost on me: "I Have No Mouth, and I Must Scream" is the title of a dark 1967 Harlan Ellison short story about a malevolent AI that transforms the human protagonist into a creature that can't speak—where the shoe is on the other foot.
diff --git a/src/content/changelog/changelogs/april-2025.mdx b/src/content/changelog/changelogs/april-2025.mdx
new file mode 100644
index 00000000..ee380e17
--- /dev/null
+++ b/src/content/changelog/changelogs/april-2025.mdx
@@ -0,0 +1,28 @@
+---
+title: April 2025
+date: '2025-04-01T00:00:00.000Z'
+hidden: false
+---
+
+### Apr 7, 2025
+
+**What's New:**
+
+* **Slack Image Support:** You can now add screenshots to your docs directly from Slack. Just trigger Promptless on Slack messages with screenshots or images, and it will automatically place them in the right spot in your docs. For example, if you notify a customer about a new feature in a Slack Connect channel and include screenshots and trigger Promptless via the Slack Message Action, Promptless will be able to include those screenshots in the documentation when appropriate.
+
+* **Directory-Specific Triggers:** Set up automatic documentation updates from specific directories in your repos (like your changelog directory). We'll update your docs whenever changes are made in these directories. For example, if you have a changelog directory, you can have Promptless be triggered whenever there is a Pull Request that includes updates to it.
+
+* **File Management:** You can now rename new documentation files or move them to different folders from the Promptless app. For example, after Promptless creates a new tutorial page, you can easily move it from the general docs folder to your dedicated tutorials section without leaving the interface.
+
+* **Changelog Publishing:** Promptless now automatically creates changelog entries when new features are shipped. If your docs already have a changelog structure, Promptless will update it appropriately.
+
+* **Custom Instructions:** You can contact the Promptless team (either via Slack or at help@gopromptless.ai) to add custom instructions for how your docs should be generated. *Example: Specify that all code examples should use TypeScript instead of JavaScript, or that certain terminology should always be used consistently across your documentation.*
+
+**Bug Fixes:**
+
+* **GitHub Comments:** GitHub comments that are unrelated to documentation will no longer trigger Promptless to generate new commits.
+
+**Integrations:**
+
+* **Webflow Support:** Connect to your docs hosted on Webflow.
+* **Bitbucket Support:** Trigger Promptless doc updates from Bitbucket pull requests.
diff --git a/src/content/changelog/changelogs/august-2025.mdx b/src/content/changelog/changelogs/august-2025.mdx
new file mode 100644
index 00000000..d2558510
--- /dev/null
+++ b/src/content/changelog/changelogs/august-2025.mdx
@@ -0,0 +1,17 @@
+---
+title: August 2025
+date: '2025-08-01T00:00:00.000Z'
+hidden: false
+---
+
+**What's New:**
+
+* **Feedback Collection:** Share feedback directly on suggestions to help Promptless learn your team's preferences and standards. A new feedback button appears when viewing suggestions.
+
+* **Citation Transparency:** The suggestions page now displays citations showing which PRs, Slack threads, Jira tickets, and documentation pages informed each change.
+
+* **Slack File Attachments:** Promptless now processes file attachments from Slack messages, including PDFs, documents, and other files. When you trigger documentation updates from Slack, Promptless analyzes these attachments for additional context.
+
+**Improvements:**
+
+* **Enhanced Suggestion Filtering:** The new filter interface includes dropdown options and a text box to search and filter suggestions by status, assignee, or other criteria. You can copy links to share filtered views with teammates.
diff --git a/src/content/changelog/changelogs/december-2024.mdx b/src/content/changelog/changelogs/december-2024.mdx
new file mode 100644
index 00000000..370e59aa
--- /dev/null
+++ b/src/content/changelog/changelogs/december-2024.mdx
@@ -0,0 +1,19 @@
+---
+title: December 2024
+date: '2024-12-01T00:00:00.000Z'
+hidden: false
+---
+
+## What's New
+
+* **Docs Staging Area:** Introduced a web interface that allows users to review and manage documentation changes before publishing to their docs platform.
+
+* **Enhanced Slack Integration:** Improved Promptless Slack bot to allow users to tag Promptless in a channel or DM Promptless directly to provide instructions for doc updates.
+
+* **GitHub User Attribution:** Added GitHub username tracking and attribution for commits.
+
+## Improvements
+
+* **New Doc Editor Integration:** Upgraded the documentation editing experience with syntax highlighting, better formatting, and comparing version diffs.
+
+* **Ephemeral Slack Notifications:** Added ephemeral direct messages in Slack when Promptless is triggered, providing immediate feedback to users without cluttering channels.
diff --git a/src/content/changelog/changelogs/december-2025.mdx b/src/content/changelog/changelogs/december-2025.mdx
new file mode 100644
index 00000000..150652b8
--- /dev/null
+++ b/src/content/changelog/changelogs/december-2025.mdx
@@ -0,0 +1,44 @@
+---
+title: December 2025
+date: '2025-12-01T00:00:00.000Z'
+hidden: false
+---
+import Frame from '@components/fern/Frame.astro';
+
+**What's New:**
+
+* **Promptless Capture:** Keeps product screenshots in your documentation current. Promptless audits your existing screenshots on day one, regenerates outdated ones, then continuously monitors your codebase for UI changes. When code changes impact a screenshot, Promptless detects which screenshots need updating and recreates them with your current UI. Review and iterate on regenerated screenshots in the dashboard.
+
+
+
+
+
+* **Screenshot Editor:** Edit screenshots generated by Promptless directly in the dashboard. Click any image in the Created Assets section to crop, add annotations, highlight UI elements, adjust framing, or insert shapes, text, and arrows—save your edits and the updated image is immediately available.
+
+
+
+
+
+* **Repository Topic Filtering for GitHub Triggers:** Filter which repositories trigger Promptless using GitHub topics. Tag your repositories with a topic like "docs-enabled" or "promptless", then configure your Promptless project to monitor that topic. Add new repos to Promptless by tagging them in GitHub—no need to update your Promptless configuration.
+
+* **Commit Trigger Replay:** New GitHub projects configured with Commit triggers can now process the last 30 days of direct commits during setup. This catches you up on recent changes and generates documentation suggestions for anything you might have missed.
+
+* **Improved Project Settings Editing:** Save empty documentation directories to scan your entire repository, and switch GitHub organizations when editing projects. When you change your documentation directory scope, Promptless automatically closes suggestions containing files outside the new scope—keeping your staging area clean.
+
+* **Automatic Suggestion Updates on PR Merge:** When a GitHub PR merges, Promptless automatically updates existing documentation suggestions to reflect what actually merged. If your PR changed during code review—code updates, description edits, or new commits—your doc suggestions stay accurate.
+
+* **Markdown Support in Suggestion Descriptions:** Suggestion descriptions in the dashboard now render with full markdown formatting—bold and italic text, code snippets, links, and structured lists.
+
+* **Protected Branch Detection for Slack Notifications:** When Promptless detects protected branches in your documentation repository, Slack notifications show "Open PR" or "View PR" buttons instead of "Publish." This prevents merge errors for repositories that require PR reviews before merging.
+
+* **Auto-Publish Support for GitHub Commit and MS Teams Triggers:** GitHub Commit and MS Teams triggers now support auto-publish mode. When enabled, Promptless automatically creates documentation PRs as soon as suggestions are ready, streamlining your review and publishing workflow.
+
+* **Auto-Merge for Documentation PRs:** Promptless now automatically merges documentation PRs as soon as they're created when auto-publish is enabled. Enable "Automatically merge Promptless's suggestions into the default branch" in project settings (nested under auto-publish) for complete end-to-end automation—from code changes to merged documentation—ideal for internal docs or teams with high confidence in Promptless suggestions.
+
+
+
+
+
+* **Citations Button Always Available:** The Show Citations button in the file diff viewer now remains visible and enabled whenever citations exist for a file. Previously, this button was incorrectly disabled after opening a PR or publishing a suggestion, making it difficult to view source references.
+
+* **Sign Out During Onboarding:** Users can now sign out from the onboarding screen. This fixes an issue where users were stuck if they accidentally signed in with the wrong email address.
diff --git a/src/content/changelog/changelogs/february-2025.mdx b/src/content/changelog/changelogs/february-2025.mdx
new file mode 100644
index 00000000..9b3edd7c
--- /dev/null
+++ b/src/content/changelog/changelogs/february-2025.mdx
@@ -0,0 +1,17 @@
+---
+title: February 2025
+date: '2025-02-01T00:00:00.000Z'
+hidden: false
+---
+
+### February 2025
+
+**What's New:**
+
+* **Intercom Integration (beta):** Added Intercom integration allowing Promptless to publish doc updates directly to Intercom help centers. Users can also trigger documentation updates from Intercom support conversations that could indicate documentation gaps.
+
+* **Paligo Support:** Integration with Paligo (beta), a documentation platform, enables Promptless to work with XML-based documentation workflows and enterprise content management systems.
+
+* **Enhanced GitHub PR Editing:** Added the ability for users to edit documentation changes further through GitHub comments on documentation PRs. This allows for iterative refinement of the generated suggestions directly within the GitHub workflow.
+
+* **Slack Notification System:** Added Slack notifications to keep teams informed about documentation updates and processing status. Added support for notifications to specific channels and improved visibility into Promptless activities.
diff --git a/src/content/changelog/changelogs/january-2025.mdx b/src/content/changelog/changelogs/january-2025.mdx
new file mode 100644
index 00000000..2761a573
--- /dev/null
+++ b/src/content/changelog/changelogs/january-2025.mdx
@@ -0,0 +1,15 @@
+---
+title: January 2025
+date: '2025-01-01T00:00:00.000Z'
+hidden: false
+---
+
+### January 2025
+
+**What's New:**
+
+- **Notion Integration**: Added Notion integration (beta) allowing users to connect their Notion workspaces and publish documentation updates directly to Notion databases.
+
+- **ReadMe Publishing Support**: Introduced direct publishing to ReadMe documentation platform via API integration. Users can now update ReadMe docs directly from the Promptless dashboard with per-file publishing capabilities. Customers on ReadMe
+
+- **File Management**: Added file path editing capabilities for new documentation, allowing users to adjust suggested file locations before publishing.
diff --git a/src/content/changelog/changelogs/january-2026.mdx b/src/content/changelog/changelogs/january-2026.mdx
new file mode 100644
index 00000000..327517ca
--- /dev/null
+++ b/src/content/changelog/changelogs/january-2026.mdx
@@ -0,0 +1,60 @@
+---
+title: January 2026
+date: '2026-01-01T00:00:00.000Z'
+hidden: false
+---
+import Frame from '@components/fern/Frame.astro';
+
+**New Features:**
+
+* **Atlassian Integration (Jira + Confluence):** Connect both Jira and Confluence through a single unified Atlassian integration. Promptless now searches your Confluence spaces alongside Jira tickets—pulling documentation patterns, terminology, and architectural decisions when creating suggestions. This replaces the previous Jira-only integration—if you previously connected Jira, reconnect to access Confluence while preserving your Jira project configuration.
+
+
+
+
+
+**Improvements:**
+
+* **Intercom Integration:** Connect your Intercom Help Center directly from the Integrations page using OAuth—no need to contact support. Publish help center articles and customer support documentation through Promptless.
+* **Upgraded to Claude Opus 4.5:** Documentation suggestions now use Claude Opus 4.5 for improved reasoning, analysis, and documentation context understanding.
+* **Calibration Progress Tracking:** Track your progress in helping Promptless learn your documentation preferences. The new Calibration Progress banner shows how many suggestions you've published and how much feedback you've provided—Promptless uses both to understand your writing style, tone, and standards. The banner appears on all dashboard pages until you reach calibration goals (5 published suggestions and 5 pieces of feedback), then disappears automatically.
+
+
+
+
+
+
+
+
+
+* **Ready Count Includes Open PRs:** The Ready count on the Change History page now includes suggestions with open documentation PRs—not just unpublished suggestions. Previously, only suggestions without PRs were counted as ready, so you can now see everything that needs your review in one place.
+* **Suggestions Stay Active When Being Reviewed:** Viewing a suggestion now counts as activity—so suggestions you're actively reviewing stay active even if no edits are made for over 30 days. Previously, suggestions would be automatically pruned after 30 days of inactivity. This works alongside the "Viewed" file checkbox added in December for tracking review progress.
+* **Faster Suggestion Page Loading:** The Change History page now loads faster. Suggestion metadata—titles, descriptions, and trigger details—appears immediately while the diff loads in parallel.
+* **Smarter Screenshot Capture:** Promptless now makes better decisions about when to capture fresh screenshots for documentation. When processing UI changes, Promptless proactively identifies which screenshots need updating and captures fresh, high-quality images from your live product.
+* **Screenshot Cropping:** Promptless can now crop screenshots to focus on specific UI elements—highlighting exactly what users need to see without extra clutter.
+* **Automatic Suggestion Updates from Main:** When changes are pushed to your documentation's main branch, Promptless merges those updates into all open suggestion branches and automatically resolves any conflicts.
+* **Trigger Source Filter:** Filter suggestions on the Change History page by how they were triggered—Slack messages, Web UI requests, or GitHub PRs. For GitHub, expand the dropdown to filter by specific repositories.
+
+**Bug Fixes:**
+
+* **Confluence Integration Reliability:** Fixed an issue where Confluence workspace connection data could be lost when refreshing the integration, making Confluence spaces temporarily unavailable.
+* **New Task Project Dropdown:** Fixed the New Task feature to only show doc collections that have completed analysis—preventing errors when submitting documentation requests. Previously, users could select doc collections that were still being analyzed, which would fail when submitted.
+* **Promptless Capture Reliability:** Fixed intermittent failures when capturing screenshots.
+* **Citation Display in Editor:** Fixed citation icons overlapping when multiple citations reference the same line—they now stack properly for easier viewing.
+* **Citation Popup Positioning:** Fixed citation popup positioning and arrow placement issues in the editor, ensuring popups display correctly even when citations are stacked.
+* **Comment Bubble Overflow:** Fixed comment bubbles extending beyond the editor viewport, keeping all interface elements properly contained within the editing area.
+* **Cleaner Suggestion Diffs:** Fixed suggestion diffs to exclude internal system files—diffs now show only your documentation changes, making them easier to review.
+* **Slack Notification Diff Files:** Fixed diff file attachments in Slack notifications—teams can now see the full diff of documentation changes directly from Slack without needing to open the PR or web interface.
+* **Git Sync Reliability:** Improved reliability of git sync operations when Promptless pushes documentation changes—sync operations now properly wait for concurrent git processes to complete, preventing intermittent failures.
+* **Git Repository Access Reliability:** Fixed intermittent failures from git configuration lock contention when processing multiple documentation updates simultaneously.
+* **GitHub PR Processing:** Improved reliability when processing GitHub PRs with many file changes—Promptless now handles large PRs with multiple files more consistently, preventing intermittent errors during analysis.
+* **Background Job Processing:** Improved reliability of background job processing—jobs now properly initialize cache clients, preventing intermittent failures during documentation generation.
+* **Suggestion Tracking with Multiple Doc Collections:** Fixed suggestion tracking with multiple doc collections—trigger events now link to the correct suggestions. Previously, when multiple agents responded to the same trigger (like a Slack message) but used different doc collections, trigger events could link to the wrong suggestion.
+* **Change History Page Performance:** Improved performance and reliability of the Change History page when viewing suggestions—page updates now happen more efficiently to ensure consistent functionality.
+* **Impacted File List Accuracy:** Suggestion diffs now show only documentation files—internal Promptless system files no longer appear in the impacted files list, making it easier to see exactly which documentation files changed.
+* **Re-opened Docs PRs Now Resume Correctly:** Re-opening a docs PR now restores the suggestion so you can continue editing. Previously, follow-on instructions weren't processed after closing and re-opening a PR.
+* **Suggestion Editing Reliability:** Fixed an issue where editing existing suggestions could fail—the system was incorrectly looking for suggestion branches in the wrong storage location.
+* **Internal Evaluation Infrastructure:** Fixed inconsistent default resource configurations in the evals system—resource defaults are now maintained in a single authoritative location, improving reliability of internal evaluation runs.
+* **Suggestion Stability for Revert PRs:** Fixed an issue where suggestions could be incorrectly deleted when processing PRs that revert previously documented changes—suggestions now remain active and continue receiving updates correctly.
+* **PR Replay Status Accuracy:** Fixed PR replays to show the correct PR status on the Triggers page. Previously, replayed PRs always showed "open" status regardless of whether the PR was actually merged, closed, or in draft state.
+* **GitHub Trigger Icons:** Fixed the Change History page to show the GitHub icon for all GitHub-based triggers—including GitHub Enterprise PRs, merged PRs, and GitHub Issues. Previously, the icon only appeared for regular open PRs.
diff --git a/src/content/changelog/changelogs/july-2025.mdx b/src/content/changelog/changelogs/july-2025.mdx
new file mode 100644
index 00000000..b5faf851
--- /dev/null
+++ b/src/content/changelog/changelogs/july-2025.mdx
@@ -0,0 +1,17 @@
+---
+title: July 2025
+date: '2025-07-01T00:00:00.000Z'
+hidden: false
+---
+
+**What's New:**
+
+* **PR Replay:** New GitHub projects can now process the last 30 days of PRs during setup. This catches you up on recent changes and generates documentation suggestions for anything you might have missed.
+
+* **All Repos Trigger:** Check "Trigger on all repos" when setting up GitHub, GitLab, or Bitbucket projects to automatically monitor all your repositories. No need to manually select each one, and new repos get included automatically.
+
+**Improvements:**
+
+* **Better PR Reviews:** When you submit a "Request changes" review on a Promptless PR, we'll process all your comments automatically—no need to @mention us in each one.
+
+* **Smarter GitHub Comments:** Promptless now react with 👀 when processing your comments, reply in threads instead of cluttering the main conversation, and mention you directly in our responses.
diff --git a/src/content/changelog/changelogs/june-2025.mdx b/src/content/changelog/changelogs/june-2025.mdx
new file mode 100644
index 00000000..59a20f44
--- /dev/null
+++ b/src/content/changelog/changelogs/june-2025.mdx
@@ -0,0 +1,16 @@
+---
+title: June 2025
+date: '2025-06-01T00:00:00.000Z'
+hidden: false
+---
+
+### June 2025
+
+**What's New:**
+
+- **GitLab Integration**: Added full GitLab support including merge request triggers, project setup, and webhook configuration for automated updates.
+
+- **Enhanced Authentication**: Implemented automatic domain verification and team member enrollment for organizations, making it easier for your teammates to access Promptless suggestions.
+
+- **Document360 Improvements**: Launched comprehensive Document360 broker with per-file publishing, webhook sync capabilities, and live URL/editor URL support in the UI
+-
diff --git a/src/content/changelog/changelogs/march-2025.mdx b/src/content/changelog/changelogs/march-2025.mdx
new file mode 100644
index 00000000..2f85a556
--- /dev/null
+++ b/src/content/changelog/changelogs/march-2025.mdx
@@ -0,0 +1,25 @@
+---
+title: March 2025
+date: '2025-03-01T00:00:00.000Z'
+hidden: false
+---
+
+### March 31, 2025
+
+**What's New:**
+
+* **Document360 Integration:** Added Document360 as a new documentation platform integration, allowing you to publish documentation updates directly to the knowledge base.
+
+* **Enhanced Bitbucket Integration:** Improved Bitbucket integration with better connection handling and enhanced pull request processing capabilities.
+
+* **Trigger Directory Configuration:** Added the ability to specify trigger directories for GitHub and Bitbucket integrations. You can now configure Promptless to only monitor specific directories within your repositories, reducing noise and focusing only on relevant code changes.
+
+* **Follow-On Requests in Web Interface:** Introduced follow-on request capabilities directly in the web interface, allowing users to request additional changes without leaving the Promptless dashboard.
+
+* **PR Template Path Configuration:** Added support for configuring custom PR template paths in documentation pipelines, giving teams more control over how Promptless-generated docs PRs are formatted and structured.
+
+**Bug Fixes:**
+
+* **False Positive Reduction:** Implemented improvements to reduce false positive triggers and unnecessary documentation suggestions.
+
+* **Comment Processing:** Improved filtering to prevent irrelevant GitHub comments from triggering documentation updates.
diff --git a/src/content/changelog/changelogs/may-2025.mdx b/src/content/changelog/changelogs/may-2025.mdx
new file mode 100644
index 00000000..27bb314d
--- /dev/null
+++ b/src/content/changelog/changelogs/may-2025.mdx
@@ -0,0 +1,53 @@
+---
+title: May 2025
+date: '2025-05-01T00:00:00.000Z'
+hidden: false
+---
+
+### May 29, 2025
+
+**What's New:**
+
+* **Jira Integration:** Added Jira as a context source integration, allowing Promptless to retrieve and search Jira issues when generating documentation updates. This includes OAuth 2.0 authentication, issue retrieval by key, and JQL search capabilities to ensure documentation updates are informed by actual project management context.
+
+* **Webflow Publishing:** Enhanced Webflow integration with direct publishing from the Change History page. Added "Save All & Publish to Webflow" button for seamless content publishing, automatic item management, and support for multiple Webflow collections.
+
+* **Per-File Publishing for ReadMe:** Added capability to publish individual files to ReadMe instead of requiring all files to be published at once, providing more granular control over documentation updates.
+
+* **Enhanced Slack Integration:** Promptless now responds directly in Slack threads instead of sending private ephemeral messages, improving transparency and collaboration. Added automatic channel joining capability for public channels when mentioned.
+
+* **Improved Suggestions UI:** Redesigned the Change History page with a new card-based UI, improved filtering and sorting options, enhanced status display, and better visualization of trigger events.
+
+**Improvements:**
+
+* **GitHub Integration Enhancements:**
+ - Added trigger events display in PR descriptions for better context
+ - Improved support for deleted files when creating documentation PRs
+ - Enhanced @promptless comment tagging with user reminders
+ - Better handling of file management operations
+
+* **User Experience:**
+ - Local timezone display for timestamps in Change History page
+ - Improved web follow-on request UX with commit timeline visibility
+ - Enhanced image processing from linked threads and follow-up requests
+ - Disabled follow-up requests after suggestion publishing for cleaner workflows
+
+* **Claude 4 Model Support:** Expanded Claude 4 model availability from select organizations to all Promptless users.
+
+* **Enhanced Image Processing:** Improved image handling capabilities with support for Slack-hosted images and better integration with documentation workflows.
+
+**Bug Fixes:**
+
+* **PR Comments:** Fixed issue where "no suggestions" comments weren't properly shown on GitHub and Bitbucket pull requests.
+
+* **Image Processing:** Restricted image processing to Slack-hosted images only (files.slack.com URLs) for improved reliability.
+
+* **UI Improvements:** Fixed suggestions table display and terminology consistency (changed "runs" to "suggestions").
+
+**Integrations:**
+
+* **Jira:** New context source integration with OAuth 2.0 authentication and JQL search capabilities.
+
+* **Enhanced Webflow:** Direct publishing capabilities with improved CMS field support and metadata parsing.
+
+* **Browser Use Demo Site:** Added integration for scraping and analyzing documentation from browser-use.com for demo purposes.
diff --git a/src/content/changelog/changelogs/november-2024.mdx b/src/content/changelog/changelogs/november-2024.mdx
new file mode 100644
index 00000000..34abd933
--- /dev/null
+++ b/src/content/changelog/changelogs/november-2024.mdx
@@ -0,0 +1,15 @@
+---
+title: November 2024
+date: '2024-11-01T00:00:00.000Z'
+hidden: false
+---
+
+## What's New
+
+* **Google Drive Integration:** Added Google Drive as a context source with OAuth authentication, allowing Promptless to access and analyze documents stored in Google Drive when generating documentation updates. Users can now connect multiple Google Drive directories to their projects for enhanced contextual information.
+
+* **GitHub Issues RAG Support:** Promptless now automatically queries GitHub issues to provide better context for documentation updates. The system intelligently handles forked repositories by using issues from the source repository and requires no additional configuration when GitHub issues are enabled.
+
+* **Multiple Context Sources:** Enhanced project configuration to support multiple context sources per project, including multiple Google Drive directories and Jira projects for comprehensive documentation context.
+
+* **Keyword Search:** Added keyword search functionality to improve content discovery and documentation generation accuracy.
diff --git a/src/content/changelog/changelogs/november-2025.mdx b/src/content/changelog/changelogs/november-2025.mdx
new file mode 100644
index 00000000..f5ba1641
--- /dev/null
+++ b/src/content/changelog/changelogs/november-2025.mdx
@@ -0,0 +1,24 @@
+---
+title: November 2025
+date: '2025-11-01T00:00:00.000Z'
+hidden: false
+---
+import Frame from '@components/fern/Frame.astro';
+
+**What's New:**
+
+* **Rich Slack Notifications for Quick Review and Publishing:** When Promptless creates documentation suggestions, you get rich notifications in Slack showing the suggestion title, description, assigned team members, trigger source, and files changed. Use the "Publish" button to merge small, straightforward suggestions directly from Slack, or click "Open PR" to review changes in detail on GitHub or in the Promptless dashboard.
+
+
+
+
+
+* **File Attachment Support for Requests to Promptless in the Dashboard:** Attach up to 5 files (10 MB max each) when creating documentation requests for Promptless from the dashboard's "New Task" button. Upload screenshots, PDFs, or documents to provide additional context. This mirrors the functionality when using Promptless in Slack, where attached images and PDFs are automatically analyzed to inform documentation suggestions.
+
+
+
+
+
+* **Automatic CI Fixes:** When documentation PRs from Promptless fail CI checks or build tests, Promptless automatically detects the issue and pushes a fix. No manual intervention needed for build errors.
+
+* **GitHub Enterprise Context Search:** Promptless now searches through your GitHub Enterprise issues, pull requests, and discussions when creating documentation suggestions—bringing GitHub Enterprise customers the same context gathering capabilities as GitHub Cloud users.
diff --git a/src/content/changelog/changelogs/october-2024.mdx b/src/content/changelog/changelogs/october-2024.mdx
new file mode 100644
index 00000000..7d4f2977
--- /dev/null
+++ b/src/content/changelog/changelogs/october-2024.mdx
@@ -0,0 +1,19 @@
+---
+title: October 2024
+date: '2024-10-01T00:00:00.000Z'
+hidden: false
+---
+
+## What's New
+
+* **Asynchronous Pipeline Loading:** Improved project setup times by implementing background pipeline loading. This reduces waiting time during initial project configuration.
+
+* **Destination Directory Selection:** You can now specify exactly which directories within the repo the doc updates should go to. This feature makes it easy for monorepo structures with a /docs directory.
+
+## Improvements
+
+* **Large File Processing:** Improved handling large documents with intelligent file chunking. The system now processes files in manageable segments while preserving full context, resulting in faster processing times and more accurate results for complex codebases.
+
+## Infrastructure
+
+* **Vector Database Migration:** We've migrated from Pinecone to pgvector for our search infrastructure. This upgrade removes previous limitations around prefix querying and metadata length restrictions.
diff --git a/src/content/changelog/changelogs/october-2025.mdx b/src/content/changelog/changelogs/october-2025.mdx
new file mode 100644
index 00000000..2e5ad7e5
--- /dev/null
+++ b/src/content/changelog/changelogs/october-2025.mdx
@@ -0,0 +1,48 @@
+---
+title: October 2025
+date: '2025-10-01T00:00:00.000Z'
+hidden: false
+---
+import Frame from '@components/fern/Frame.astro';
+
+**What's New:**
+
+* **Manual Documentation Requests from Dashboard:** Request documentation updates directly from the dashboard using the "New Task" button. Select a project, write your instructions, and submit—just like Slack DMs but from the dashboard.
+
+
+
+
+
+
+
+
+
+* **Research Visibility in Change Timeline:** The Change Timeline now shows exactly what Promptless reviewed—files, webpages, Slack conversations, and other sources. Click "Show details" for the full list with direct links. Source descriptions are more precise—GitHub PRs appear as "Reviewed Promptless/promptless#123" instead of generic "Read webpage from github.com".
+
+
+
+
+
+* **Triggers Page:** Verify that Promptless ran on expected PRs and events. When Promptless doesn't create suggestions, see exactly why. View research and context for any trigger from the last 30 days, with filters for trigger type and suggestion status.
+
+
+
+
+
+* **Multiple GitHub Organization Support:** Connect multiple GitHub organizations to a single Promptless account. Each org appears as its own card with separate repository lists. Manage company and personal projects in one place.
+
+
+
+
+
+
+
+
+
+* **Non-Blocking Feedback:** When you remember feedback for future suggestions without requesting changes to the current one, you can keep viewing and interacting with the suggestion right away. Previously, the interface would block while processing feedback—even when nothing was being changed.
+
+* **Slack Passive Channel Listening:** Automatically monitor specific Slack channels and create documentation suggestions when conversations go quiet for 10 minutes. This opt-in feature lets you select which channels to monitor.
+
+* **Slack Private Channel Support:** Promptless now works properly in private Slack channels when invited, fixing previous permission issues.
+
+* **Descriptive Commit Messages:** Promptless PRs now use the suggestion title as the commit message instead of generic "Documentation updates from Promptless" text. This keeps your git history more informative and easier to track—especially helpful if you don't use squash-merge.
diff --git a/src/content/changelog/changelogs/september-2025.mdx b/src/content/changelog/changelogs/september-2025.mdx
new file mode 100644
index 00000000..98c05fb8
--- /dev/null
+++ b/src/content/changelog/changelogs/september-2025.mdx
@@ -0,0 +1,36 @@
+---
+title: September 2025
+date: '2025-09-01T00:00:00.000Z'
+hidden: false
+---
+import Frame from '@components/fern/Frame.astro';
+
+**Improvements:**
+
+* **Enhanced Slack Context Understanding:** Promptless now analyzes full Slack conversations instead of individual messages, capturing surrounding discussion for more accurate and comprehensive documentation.
+
+* **Enhanced GitHub PR Comment Context Awareness:** When you tag Promptless in GitHub PR comments, it reads all previous comments to understand full context. Use simple instructions like "Same here" or "Apply this change to the other section too" without repeating details.
+
+* **GitBook Platform Support:** Promptless now supports GitBook as a first-class documentation platform. Connect your repositories to automatically update GitBook documentation when code changes.
+
+* **Improved Jira Context Integration:** Promptless now more reliably fetches Jira ticket information when issues are mentioned in pull requests. Full ticket context including descriptions, comments, and related issues is consistently retrieved.
+
+* **Automated CI Check and Build Issue Resolution:** Promptless automatically detects and fixes quality issues in documentation PRs. When linters fail, Vale rules trigger, or build errors occur, Promptless analyzes and pushes fixes to the PR branch automatically.
+
+* **Smart Draft State Management for Documentation PRs:** Documentation PRs now open as drafts when the source code PR hasn't merged yet, then automatically switch to "Ready for Review" once the source PR merges. This means your team only reviews documentation changes after the underlying code is finalized.
+
+
+
+
+
+
+
+
+
+* **Improved Dashboard Synchronization for Follow-on Suggestions:** The dashboard now immediately reflects changes when you make follow-on suggestions. No more delays—instant updates for better real-time visibility.
+
+* **PR Open Status Filter:** You can now filter for suggestions published as pull requests directly from the status dropdown. Previously, you had to manually type `is:pr_open` into the search bar. The "PR Open" option appears alongside "Ready," "Published," and "Rejected."
+
+
+
+
diff --git a/src/content/docs/docs/account-management/account-management.mdx b/src/content/docs/docs/account-management/account-management.mdx
new file mode 100644
index 00000000..58a59f51
--- /dev/null
+++ b/src/content/docs/docs/account-management/account-management.mdx
@@ -0,0 +1,114 @@
+---
+title: Account Management
+slug: docs/account-management/account-management
+sidebar:
+ hidden: false
+ order: 37
+---
+import Frame from '@components/fern/Frame.astro';
+import Steps from '@components/fern/Steps.astro';
+import Step from '@components/fern/Step.astro';
+import ParamField from '@components/fern/ParamField.astro';
+import Info from '@components/fern/Info.astro';
+
+# Account Management
+
+Manage your Promptless organization, team members, and access controls through the account management interface.
+
+## Creating an Account
+
+You can sign up for an account at [accounts.gopromptless.ai](https://accounts.gopromptless.ai), or contact the team at [hello@gopromptless.ai](mailto:hello@gopromptless.ai).
+
+## Managing Team Members
+
+### Adding Team Members
+
+To add other users to your team account:
+
+
+
+
+### User Roles
+
+Promptless supports different user roles with varying levels of access:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+In the example above, Promptless can read the `promptless` and `promptless-dashboard` repos, but can read and write to the `promptless-docs` repo.
+
+## Auto-publish Mode
+
+When auto-publish is enabled for your project:
+
+- Promptless automatically creates a new PR in your documentation repository with suggested changes
+- For GitHub PR triggers, the documentation PR is linked in a comment on the original code PR
+- For [commit triggers](/docs/configuring-promptless/triggers/git-hub-commits), you can enable auto-merge to automatically merge documentation PRs as soon as they're created (nested checkbox under auto-publish in project settings)
+
+## Automated CI Check and Build Issue Resolution
+
+When Promptless opens a documentation PR, it automatically monitors the pull request for quality issues. If CI checks fail, linting tools report errors, Vale rules trigger warnings, or your documentation hosting provider detects broken links or build problems, Promptless will automatically analyze the issues and push fixes directly to the PR branch.
+
+This automated issue resolution works seamlessly with your existing GitHub workflow - there's no additional configuration needed. Quality problems get resolved in the background while you focus on content rather than troubleshooting technical issues.
+
+## Trigger Events in Pull Request Descriptions
+
+When Promptless creates a pull request for documentation updates, it automatically includes a list of the trigger events that led to those changes in the PR description. This provides valuable context for reviewers and creates clear traceability between documentation updates and their originating events.
+
+The trigger events section in the PR description includes:
+- Links back to the original source (e.g., Slack threads, GitHub PRs, support tickets)
+- Brief descriptions of what triggered the documentation update
+- Easy navigation to review the context that prompted the changes
+
+## Setup Instructions
+
+To connect GitHub to Promptless, see the [GitHub Integration](/docs/integrations/github-integration) setup guide.
+
+## Frequently Asked Questions
+
+
+
+
+## Directory-Specific Commits
+
+Similar to PR triggers, you can configure Promptless to only trigger on commits that affect specific directories. This is particularly useful for monitoring changelog directories or specific feature areas.
+
+When trigger directories are specified, only commits that contain changes to those directories will trigger documentation updates.
+
+## Use Cases
+
+GitHub commit triggers are especially useful for:
+
+- **Changelog Monitoring**: Automatically update documentation when changelog files are modified
+- **Hotfix Documentation**: Capture documentation needs from emergency fixes that bypass the normal PR process
+- **Direct-to-Main Workflows**: Support teams that commit directly to main branches
+- **Automated Updates**: Trigger documentation updates from automated commit processes
+
+## Auto-merge Mode
+
+Automatically merge documentation PRs into the default branch as soon as they're created.
+
+Auto-merge requires auto-publish to also be enabled.
+
+Auto-merge is useful for:
+- **Internal documentation**: When documentation PRs don't require human review
+- **High-confidence workflows**: Teams that want full automation
+- **Changelog-driven updates**: When you want changelog updates to publish immediately
+
+Enable auto-merge in your [project settings](https://app.gopromptless.ai/projects) by checking "Automatically merge Promptless suggestions into the default branch." This option is only available for commit triggers.
+
+
+
+
+
+## Setup Instructions
+
+To connect GitHub to Promptless, see the [GitHub Integration](/docs/integrations/github-integration) setup guide.
diff --git a/src/content/docs/docs/configuring-promptless/triggers/git-hub-p-rs.mdx b/src/content/docs/docs/configuring-promptless/triggers/git-hub-p-rs.mdx
new file mode 100644
index 00000000..d838175b
--- /dev/null
+++ b/src/content/docs/docs/configuring-promptless/triggers/git-hub-p-rs.mdx
@@ -0,0 +1,86 @@
+---
+title: GitHub PRs
+slug: docs/configuring-promptless/triggers/git-hub-p-rs
+sidebar:
+ hidden: false
+ order: 9
+---
+import Frame from '@components/fern/Frame.astro';
+import Info from '@components/fern/Info.astro';
+import Note from '@components/fern/Note.astro';
+import Warning from '@components/fern/Warning.astro';
+
+Promptless automatically monitors your GitHub repositories for new pull requests. When a PR is opened, the system analyzes the changes to determine if documentation updates are needed.
+
+## How It Works
+
+When a pull request is opened in your monitored repositories:
+
+1. **Automatic Detection**: Promptless receives notification of the new PR
+2. **Analysis**: The system processes the code diff, PR title, and PR description to understand the context
+3. **Relevance Assessment**: Promptless determines if the changes require documentation updates
+4. **Suggestion Creation**: If relevant, Promptless creates documentation suggestions
+
+
+
+
+## Directory-Specific Triggers
+
+You can configure Promptless to only trigger when changes are made to specific directories within your repositories. This is particularly useful when you want to focus documentation updates on changes to certain parts of your codebase.
+
+To set up directory-specific triggers:
+
+1. When creating or editing a project, select the GitHub trigger option
+2. Check the "Choose specific directories to trigger this project" option
+3. Enter the directory paths you want to monitor, separating multiple paths with commas
+4. Save your project configuration
+
+
+
+
+
+When trigger directories are specified, only PRs that contain changes to those directories will be considered, and updates to other files will be ignored.
+
+## Repository Topics
+
+If you have many repositories, you can use GitHub topics to control which ones trigger Promptless. This is especially helpful for organizations with dozens or hundreds of repos where only some need documentation automation.
+
+1. **Tag your repositories in GitHub**: Add topics to the repositories you want Promptless to monitor (e.g., "docs-watch", "promptless"). To add topics to a repository, go to the repository's main page and click "Add topics" in the About section.
+
+2. **Configure your project**: When creating or editing a GitHub project, check the "Trigger on repos with certain topics" option and enter the topic(s) you want to monitor. You can specify multiple topics, and Promptless will trigger on any repository that has at least one of those topics.
+
+3. **Manage through GitHub**: To add a new repository to Promptless, tag it with the configured topic in GitHub. To remove a repository, remove the topic from the repository settings.
+
+
+
+
+## Privacy and Channel Access
+
+By default, Promptless only reads Slack content when you explicitly trigger it by tagging @Promptless or using the "Update Docs" message action. If you enable passive listening, Promptless will monitor only the specific channels you select in your project configuration.
+
+## Setup Instructions
+
+To connect Slack to Promptless, see the [Slack Integration](/docs/integrations/slack-integration) setup guide.
diff --git a/src/content/docs/docs/configuring-promptless/triggers/zendesk-tickets-beta.mdx b/src/content/docs/docs/configuring-promptless/triggers/zendesk-tickets-beta.mdx
new file mode 100644
index 00000000..b533f8ae
--- /dev/null
+++ b/src/content/docs/docs/configuring-promptless/triggers/zendesk-tickets-beta.mdx
@@ -0,0 +1,45 @@
+---
+title: Zendesk Tickets (Beta)
+slug: docs/configuring-promptless/triggers/zendesk-tickets-beta
+sidebar:
+ hidden: false
+ order: 13
+---
+import Note from '@components/fern/Note.astro';
+
+Zendesk integration enables automated documentation updates based on support ticket patterns and customer interactions. This helps identify gaps in documentation based on recurring user questions.
+
+## How It Works
+
+When a support ticket is resolved:
+
+1. **Ticket Analysis**: Promptless analyzes the resolved ticket content and customer interaction
+2. **Pattern Detection**: The system identifies common questions or issues that might indicate documentation gaps
+3. **Context Evaluation**: Promptless determines if the ticket represents a broader documentation need
+4. **Suggestion Creation**: If relevant, Promptless creates documentation suggestions to address the gap
+
+## Configuration
+
+Configure Zendesk triggers in your [project settings](https://app.gopromptless.ai/projects):
+
+1. Select Zendesk as your trigger source
+2. Configure which ticket types or categories to monitor
+3. Set auto-publish preferences
+4. Configure notification settings
+
+
+
+
+The interface includes common examples to get you started:
+- "Put X file's content as a section in Y file instead of making it its own file"
+- "Make the tone more conversational, and do that for all future suggestions too"
+- "I always want changelog entries in their own suggestion—please move"
+
+Click **Submit Request** to process all your feedback.
+
+## 2. Inline Comments
+
+Add comments to specific files or sections within a suggestion for targeted feedback. Click **Edit** or **Add Comment** on any file to provide context-specific input.
+
+
+
+
+
+When you add an inline comment, you'll see a feedback panel with two options:
+
+
+
+
+
+**Request changes on this suggestion**: Promptless will apply your feedback to the current suggestion. You can add multiple comments and submit them all at once.
+
+**Remember feedback for future suggestions**: Promptless saves your preferences and applies them to future documentation. This helps it learn your style and standards over time.
+
+ **Examples of feedback to remember:**
+ - "Always include code examples for API endpoints"
+ - "Use active voice instead of passive voice"
+ - "Include troubleshooting sections for configuration guides"
+
+## 3. Overall Comments
+
+Leave general feedback about a suggestion without targeting a specific file. This is useful for high-level guidance or when your feedback applies to the entire suggestion.
+
+
+
+
+
+Like inline comments, you can choose whether to request immediate changes or remember the feedback for future suggestions.
+
+## 4. Close Suggestion Feedback
+
+When closing a suggestion, provide feedback about why you're rejecting it. This helps Promptless improve future suggestions.
+
+
+
+
+
+Select one or more reasons:
+- "I copied this change into my docs editor"
+- "This change is incorrect"
+- "This change is too insignificant"
+- "This change was covered in another Promptless suggestion"
+- "This is already in my docs"
+- "This change is self-explanatory and doesn't need docs"
+
+You can also provide additional context in the feedback field. Check "Remember this feedback for future suggestions" to save your preferences.
+
+## 5. GitHub PR Comments
+
+Leave comments directly in the GitHub PR interface to provide feedback. Tag @Promptless in any line comment to request changes.
+
+Promptless reads all previous comments in the thread to understand context, so you can give brief instructions like "same change here" or "apply this to the other sections too."
+
+
+
+
+
+Need help? Contact us at [help@gopromptless.ai](mailto:help@gopromptless.ai).
diff --git a/src/content/docs/docs/how-to-use-promptless/using-the-web-interface.mdx b/src/content/docs/docs/how-to-use-promptless/using-the-web-interface.mdx
new file mode 100644
index 00000000..4ab65b46
--- /dev/null
+++ b/src/content/docs/docs/how-to-use-promptless/using-the-web-interface.mdx
@@ -0,0 +1,40 @@
+---
+title: Using the Web Interface
+description: >-
+ Learn how to use Promptless's web interface to highlight text, provide
+ feedback, and guide documentation improvements
+slug: docs/how-to-use-promptless/using-the-web-interface
+sidebar:
+ hidden: false
+ order: 25
+---
+import Frame from '@components/fern/Frame.astro';
+
+### Suggestion overview
+
+Each suggestion includes a title and description that explains what changes are being made and why.
+
+
+
+
+
+### Providing feedback
+
+Promptless offers several ways to provide feedback on suggestions. Learn about all available feedback methods in the [Providing Feedback](/docs/how-to-use-promptless/providing-feedback) guide.
+
+### Triggers page
+
+The Triggers page shows all events that triggered Promptless over the last 30 days. Each entry displays:
+
+- **Trigger source**: The event that fired (like a GitHub PR or Slack message)
+- **Status**: Processing state (completed, in progress, or error)
+- **Suggestions created**: Whether documentation updates resulted from this trigger
+- **Timestamp**: When the trigger occurred
+
+
+
+
+
+Use the search box to find triggers by PR info, Slack thread topic, task name, or other summary text—including events older than 30 days. Use the filters to narrow down by trigger type or suggestion status. Click any trigger to see full details, including what research Promptless did and why it created (or skipped) documentation updates.
+
+Need help with the web interface? Contact us at [help@gopromptless.ai](mailto:help@gopromptless.ai).
diff --git a/src/content/docs/docs/how-to-use-promptless/working-with-slack.mdx b/src/content/docs/docs/how-to-use-promptless/working-with-slack.mdx
new file mode 100644
index 00000000..28344f79
--- /dev/null
+++ b/src/content/docs/docs/how-to-use-promptless/working-with-slack.mdx
@@ -0,0 +1,169 @@
+---
+title: Working with Slack
+description: >-
+ Learn how to use Promptless directly in Slack through message actions, DMs,
+ channel mentions, and passive listening
+slug: docs/how-to-use-promptless/working-with-slack
+sidebar:
+ hidden: false
+ order: 23
+---
+import Frame from '@components/fern/Frame.astro';
+import Steps from '@components/fern/Steps.astro';
+import Step from '@components/fern/Step.astro';
+import Accordion from '@components/fern/Accordion.astro';
+import Note from '@components/fern/Note.astro';
+import Tip from '@components/fern/Tip.astro';
+
+
+
+
+
+
+
+
+
+
+
+
+## What You Can Do with Atlassian
+
+Once connected, you can use Jira and Confluence as context sources to enhance documentation suggestions:
+
+- **Jira**: Automatically retrieve ticket information and search for related issues using JQL queries. See the [Jira Context Source](/docs/configuring-promptless/context-sources/jira) page for details.
+- **Confluence**: Search your Confluence spaces for existing documentation patterns, terminology, and architectural decisions. See the [Confluence Context Source](/docs/configuring-promptless/context-sources/confluence) page for details.
+
+
+
+
+
+## Provisioning an Atlassian Account for Promptless
+
+We recommend creating a dedicated Atlassian account for Promptless to access both Jira and Confluence. A dedicated account gives you complete audit trail visibility and lets you configure fine-grained permissions for both services.
+
+Create the account using an email alias like `your_email+promptless@company.com`, or ask your IT admin to provision a new email account like `promptless@company.com`.
+
+
+
+
+
+
+
+
+
+ When setting up the account, you can use the name "Promptless Bot".
+
+ Once complete, you'll see the account listed as ACTIVE. It might take up to an hour for the status to update from INVITED to ACTIVE after you accept the invite.
+
+
+
+
+
+
+
+### Required App Details
+
+Fill in the following fields in your GitHub App configuration:
+
+- **GitHub App name** (required): Enter a descriptive name like "Promptless Enterprise" or "Promptless (Your Company Name)"
+- **Description**: Use: "Promptless keeps your technical guides up-to-date using AI."
+- **Homepage URL** (required): `https://gopromptless.ai`
+
+## Step 2: Configure Authentication URLs
+
+Set up the callback and redirect URLs for proper authentication flow:
+
+
+
+
+
+### Authentication Configuration
+
+Configure the following URLs in your GitHub App settings:
+
+- **Callback URL** (required): `https://app.gopromptless.ai/integrations`
+- **Setup URL (Post installation)** (required): `https://app.gopromptless.ai/integrations/github-redirect`
+
+
+
+
+
+
+
+
+### Webhook Configuration
+
+Configure the following webhook settings in your GitHub App:
+
+- **Webhook URL** (required): `https://api.gopromptless.ai/integrations/github/events`
+- **Webhook secret** (optional): Leave this field empty or generate a secure secret if required by your security policies
+- **SSL verification** (required): Enable SSL verification (recommended for security)
+
+## Step 4: Configure Repository Permissions
+
+Promptless requires specific repository permissions to function properly. Configure these permissions in your GitHub App settings:
+
+
+
+
+
+### Required Repository Permissions
+
+Configure the following permissions for your GitHub App:
+
+#### Pull Requests - Read and Write
+
+
+
+
+
+This permission allows Promptless to:
+ - Read pull request content and metadata
+ - Create documentation update pull requests
+ - Add comments to pull requests for feedback
+
+#### Contents - Read and Write
+
+
+
+
+
+This permission allows Promptless to:
+ - Read repository files and documentation
+ - Create and update documentation files
+ - Access repository structure and content
+
+#### Commit Statuses - Read Only
+
+
+
+
+
+This permission allows Promptless to:
+- Read commit status information
+- Understand the state of pull requests and commits
+
+#### Webhooks - Read and Write
+
+
+
+
+
+This permission allows Promptless to:
+ - Manage webhook configurations
+ - Receive real-time notifications of repository events
+
+## Step 5: Configure Webhook Events
+
+Select the specific events that should trigger Promptless documentation updates:
+
+
+
+
+
+### Required Webhook Events
+
+Select the following events to ensure Promptless receives all necessary notifications:
+
+- **Pull Request** - Triggers when pull requests are opened, updated, or closed
+- **Pull Request Review** - Triggers when pull request reviews are submitted
+- **Pull Request Review Thread** - Triggers when review threads are created or updated
+- **Pull Request Review Comment** - Triggers when individual review comments are made
+- **Push** - Triggers when code is pushed to repositories
+- **Release** - Triggers when releases are created or updated
+- **Repository** - Triggers when repository settings change
+
+## Step 6: IP Whitelisting
+
+Add Promptless IP addresses to your network whitelist to ensure proper connectivity:
+
+
+
+
+### Completing the Connection
+
+To establish the connection:
+
+1. Log into your Promptless dashboard at [app.gopromptless.ai](https://app.gopromptless.ai)
+2. Navigate to the Integrations page
+3. Locate the GitHub Enterprise integration tile
+4. Click **Connect GitHub Enterprise** to establish the connection
+
+
+
+
+2. Enter your GitHub organization name and select which org to install Promptless into.
+
+
+
+
+3. Select which repositories you want to give Promptless access to. Typically, this will be your source code and your documentation repo (if your docs are in GitHub).
+
+
+
+
+4. Verify that Promptless is connected in the integrations page.
+
+
+
+
+## Connecting Multiple GitHub Organizations
+
+You can connect multiple GitHub organizations to your Promptless account. This is useful for managing work and personal repositories, or when working across multiple organizations.
+
+After you connect your first organization, click the "Connect another GitHub Org" button on the integrations page to add more. Each new organization follows the same installation process.
+
+Each connected organization appears as its own card on the integrations page, showing:
+- Organization name
+- List of accessible repositories
+- Individual refresh and disconnect controls
+
+When creating or editing projects, repositories from all connected organizations are available in the dropdown menus, displayed as `organization/repository`.
+
+## Adding More Repos After Installation
+
+After the initial installation, you may need to add new repositories or modify which repositories Promptless can access. You can manage this directly through your GitHub organization settings:
+
+1. Navigate to your GitHub organization settings
+2. Go to "Third-party Access" → "GitHub Apps"
+3. Find "Promptless" in the list and click "Configure"
+4. In the "Repository access" section, you can:
+ - Switch between "All repositories" and "Only select repositories"
+ - Add or remove specific repositories using the "Select repositories" dropdown
+ - Remove repositories by clicking the "×" next to their names
+
+
+
+
+
+5. Click "Save" to apply your changes
+
+After updating repository access, the new repositories will be available when creating or editing projects in Promptless. Note that it may take a few minutes for the changes to be reflected in the Promptless dashboard. If you don't see newly added repositories immediately, you may need to click the "refresh repos" icon in the integrations page to update the repository list.
+
+## Authentication Model
+
+Promptless uses the official [GitHub App specification](https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps) to authenticate with GitHub. Promptless authenticates securely with JWTs generated by the GitHub App installation.
+
+This ensures that Promptless has read and write access to the repositories that you select, and that either you or Promptless can revoke access at any time.
+
+## What You Can Do with GitHub
+
+Once connected, you can use GitHub for:
+
+- **[Triggers](/docs/configuring-promptless/triggers)**: Monitor pull requests and commits for documentation updates
+- **[Context Sources](/docs/configuring-promptless/context-sources)**: Search code repositories and issues for technical context
+- **[Doc Collections](/docs/configuring-promptless/doc-collections/git-hub-repos-docs-as-code)**: Publish documentation updates to GitHub-based platforms
+
+## Frequently Asked Questions
+
+
+
+
+2. You'll be redirected to Linear to sign in to the right organization, if you are not already signed into the web app.
+
+
+
+
+
+
+
+3. Once you're signed in, you'll be redirected back to Promptless, and you can verify that Linear is connected.
+
+
+
+
+## Authentication Model
+
+Promptless uses OAuth 2.0 to authenticate with Linear, following their [official Linear OAuth 2.0 specification](https://developers.linear.app/docs/oauth/authentication). This ensures:
+
+- Secure token-based authentication
+- Ability to revoke access at any time
+- Granular permission control at the team level
+- Regular token rotation for enhanced security
+
+## What You Can Do with Linear
+
+Once connected, you can use Linear as a [context source](/docs/configuring-promptless/context-sources/linear) to search for related issues and project management data that enhances documentation accuracy.
diff --git a/src/content/docs/docs/integrations/microsoft-teams-integration.mdx b/src/content/docs/docs/integrations/microsoft-teams-integration.mdx
new file mode 100644
index 00000000..34fea0e7
--- /dev/null
+++ b/src/content/docs/docs/integrations/microsoft-teams-integration.mdx
@@ -0,0 +1,77 @@
+---
+title: Microsoft Teams Integration
+slug: docs/integrations/microsoft-teams-integration
+sidebar:
+ hidden: false
+ order: 34
+---
+import Frame from '@components/fern/Frame.astro';
+
+# Microsoft Teams Integration
+
+**Used for: Triggers**
+
+Promptless integrates with Microsoft Teams through our official Teams app, enabling automated documentation updates based on team communication and collaboration within your Teams environment.
+
+## Prerequisites
+
+To install Promptless in Microsoft Teams, you'll need:
+- Microsoft Teams admin center access
+- Permissions to manage app setup policies in your organization
+- Ability to install and configure third-party apps
+
+## Installation
+
+### Step 1: Download Promptless Teams App Package
+
+First, download the Promptless Teams app package from the [Promptless integrations page](https://app.gopromptless.ai/integrations):
+
+
+
+
+
+### Step 2: Upload Promptless App
+
+1. Navigate to the [Microsoft Teams admin center](https://admin.teams.microsoft.com)
+2. In the left navigation, under **Teams apps**, select **Manage apps**. This section allows you to control which apps are available to install for users in your organization
+3. Click the **Actions** > **Upload new app** button to upload the Promptless Teams app package
+4. Click **Upload** to proceed with the app installation
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Step 3: Grant Access to Users
+
+1. In the left navigation, select **Setup policies**
+
+
+
+
+
+2. Select the **Global (Org-wide default)** policy
+3. Ensure that **Upload custom apps** and **User pinning** are enabled. These settings allow users to install and pin custom apps like Promptless.
+4. Under **Installed apps**, click on **Add apps**
+
+
+
+
+
+5. Search for "Promptless" and add it to the policy
+6. Click **Save** to apply the changes
+
+## What You Can Do with Microsoft Teams
+
+Once connected, you can use Microsoft Teams for:
+
+- **[Triggers](/docs/configuring-promptless/triggers/microsoft-teams-messages)**: Tag @Promptless in channels or DMs to trigger documentation updates
+
+For more details about configuration, see [Microsoft Teams Triggers](/docs/configuring-promptless/triggers/microsoft-teams-messages).
diff --git a/src/content/docs/docs/integrations/slack-integration.mdx b/src/content/docs/docs/integrations/slack-integration.mdx
new file mode 100644
index 00000000..a2998f5b
--- /dev/null
+++ b/src/content/docs/docs/integrations/slack-integration.mdx
@@ -0,0 +1,58 @@
+---
+title: Slack Integration
+slug: docs/integrations/slack-integration
+sidebar:
+ hidden: false
+ order: 33
+---
+import Frame from '@components/fern/Frame.astro';
+import Info from '@components/fern/Info.astro';
+
+# Slack Integration
+
+**Used for: Triggers and Context**
+
+Promptless integrates with Slack through our official Slack App, enabling automated documentation updates based on team communication and support conversations.
+
+Promptless does not archive or store your Slack messages.
+
+Disclaimer: Promptless uses LLMs from OpenAI and Anthropic that have the potential to generate inaccurate results.
+
+## Installation
+
+1. Click "Connect Slack" from the [integrations page](https://app.gopromptless.ai/integrations).
+
+
+
+
+2. You'll be redirected to Slack to install the Promptless app. **Be sure to select the right workspace to install Promptless.**
+
+
+
+
+3. Review and approve the requested permissions for the Promptless Slack app. Promptless requires these permissions to be able to be triggered from the right events in Slack and to notify your team when updates are available.
+
+
+
+
+
+
+
+## What You Can Do with Slack
+
+Once connected, you can use Slack for:
+
+- **[Triggers](/docs/configuring-promptless/triggers/slack-messages)**: Tag @Promptless or use message actions to trigger documentation updates
+- **[Context Sources](/docs/configuring-promptless/context-sources)**: Search Slack conversations for team discussions and decisions
+
+## Privacy and Channel Access
+
+By default, Promptless only reads Slack content when you explicitly trigger it by tagging @Promptless or using the "Update Docs" message action. If you enable passive listening in your project settings, Promptless will monitor only the specific channels you select. Promptless cannot access private channels unless it has been specifically invited to those channels.
+
+For more details about using Slack with Promptless, see [Working with Slack](/docs/how-to-use-promptless/working-with-slack).
diff --git a/src/content/docs/docs/integrations/zendesk-integration.mdx b/src/content/docs/docs/integrations/zendesk-integration.mdx
new file mode 100644
index 00000000..c10540d2
--- /dev/null
+++ b/src/content/docs/docs/integrations/zendesk-integration.mdx
@@ -0,0 +1,41 @@
+---
+title: Zendesk Integration
+slug: docs/integrations/zendesk-integration
+sidebar:
+ hidden: false
+ order: 35
+---
+import Frame from '@components/fern/Frame.astro';
+
+# Zendesk Integration
+
+**Used for: Triggers and Publishing**
+
+Promptless integrates with Zendesk through OAuth 2.0, enabling automated documentation updates based on support ticket patterns and customer interactions, as well as publishing updates to Zendesk's Help Center.
+
+## Installation
+
+1. Click "Connect Zendesk" from the [integrations page](https://app.gopromptless.ai/integrations).
+
+2. Review the requested permissions and approve the Promptless app.
+
+
+
+
+3. Verify that Zendesk is connected in the integrations page.
+
+## Authentication Model
+
+Promptless uses Zendesk's [official OAuth 2.0 authentication](https://developer.zendesk.com/api-reference/introduction/security-and-auth/), which provides:
+
+- Secure token-based authentication
+- Granular API access scopes
+- Ability to revoke access at any time
+- Regular token rotation for enhanced security
+
+## What You Can Do with Zendesk
+
+Once connected, you can use Zendesk for:
+
+- **[Triggers](/docs/configuring-promptless/triggers/zendesk-tickets-beta)**: Monitor resolved support tickets for documentation gaps (Beta)
+- **[Doc Collections](/docs/configuring-promptless/doc-collections/zendesk)**: Publish documentation updates directly to your Zendesk Help Center
diff --git a/src/content/docs/docs/security-and-privacy.mdx b/src/content/docs/docs/security-and-privacy.mdx
new file mode 100644
index 00000000..b80f8932
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy.mdx
@@ -0,0 +1,21 @@
+---
+title: Security and Privacy
+slug: docs/security-and-privacy
+sidebar:
+ hidden: false
+ order: 38
+---
+# Security and Privacy
+
+Promptless is committed to protecting the security and privacy of our customers' data. This section provides a high-level overview of our security practices, data handling procedures, and privacy commitments. For more detailed information, please schedule a call with our team by contacting us at help@gopromptless.ai.
+
+## Overview
+
+Our security documentation is organized into the following sections:
+
+- [Single Sign-On (SSO) Setup](./setup-sso.md) - Enterprise authentication via SAML 2.0 and OpenID Connect (OIDC)
+- [Compliance and Certifications](./compliance.md) - SOC 2 certification, penetration testing, audit logging, and incident notification procedures
+- [Data Handling and Security](./data-handling.md) - Details about our data security practices, authentication controls, and enterprise security features
+- [Network Architecture](./network-architecture.md) - Information about our infrastructure and security architecture
+- [Promptless Subprocessors](./subprocessors.md) - List of third-party services we use and our model-agnostic approach
+- [Privacy Policy](./privacy-policy.md) - Link to our detailed privacy policy
diff --git a/src/content/docs/docs/security-and-privacy/compliance-and-certifications.mdx b/src/content/docs/docs/security-and-privacy/compliance-and-certifications.mdx
new file mode 100644
index 00000000..71abdc28
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy/compliance-and-certifications.mdx
@@ -0,0 +1,62 @@
+---
+title: Compliance and Certifications
+slug: docs/security-and-privacy/compliance-and-certifications
+sidebar:
+ hidden: false
+ order: 40
+---
+# Compliance and Certifications
+
+This page covers Promptless's compliance certifications, security practices, and incident response procedures.
+
+## SOC 2 Compliance
+
+Promptless maintains SOC 2 Type II certification. Our SOC 2 report covers:
+
+- Security controls and access management
+- Data encryption practices
+- Incident response procedures
+- Change management processes
+- Monitoring and logging capabilities
+
+To request a copy of our SOC 2 report, contact us at help@gopromptless.ai.
+
+## Penetration Testing
+
+Promptless conducts annual third-party penetration tests performed by independent security firms. These assessments evaluate our infrastructure, application security, and data protection controls.
+
+Penetration test summary reports are available to enterprise customers upon request. Contact help@gopromptless.ai for more information.
+
+## Security Incident Notification
+
+If a security incident affects customer data, Promptless follows this notification process:
+
+- **Notification timing**: Customers are notified within 72 hours of confirming an incident affects their data
+- **Notification recipients**: Security notifications are sent to organization administrators and any designated security contacts on file
+- **Notification content**: Includes a description of the incident, affected data, remediation steps taken, and recommended actions
+
+To add additional security contacts (such as a security team email address) for incident notifications, contact help@gopromptless.ai.
+
+## Audit Logging
+
+Promptless provides audit logging for enterprise customers. Audit logs capture security-relevant events including:
+
+- User authentication events
+- Administrative actions (team member changes, role modifications)
+- Integration configuration changes
+- API key creation and revocation
+
+Enterprise customers can request audit log exports by contacting help@gopromptless.ai. Logs are available in standard formats for integration with SIEM tools.
+
+## Session Management
+
+Session management varies based on your authentication method:
+
+- **Enterprise SSO (SAML/OIDC)**: Session duration and timeout policies are controlled by your identity provider. Configure session expiry, idle timeouts, and re-authentication requirements in your IdP settings.
+- **Standard authentication (Google/GitHub SSO)**: Session management is handled by the authentication provider. Contact help@gopromptless.ai for details on session timeout behavior.
+
+For organizations requiring specific session timeout policies (such as 24-hour expiry), configure these settings in your identity provider when using enterprise SSO.
+
+## Questions About Compliance?
+
+For questions about our compliance practices, to request compliance documentation, or to discuss specific security requirements, contact our team at help@gopromptless.ai.
diff --git a/src/content/docs/docs/security-and-privacy/data-handling-and-classification.mdx b/src/content/docs/docs/security-and-privacy/data-handling-and-classification.mdx
new file mode 100644
index 00000000..3c53aebf
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy/data-handling-and-classification.mdx
@@ -0,0 +1,81 @@
+---
+title: Data Handling and Classification
+slug: docs/security-and-privacy/data-handling-and-classification
+sidebar:
+ hidden: false
+ order: 41
+---
+# Data Handling and Classification
+
+Promptless is designed with data minimization in mind, ensuring that we only store what's necessary to provide our documentation automation service and keeping Promptless's risk level at a minimum. This page explains how we handle your data when you use Promptless.
+
+## Data Classification
+
+| Data Category | Promptless Handling | Description |
+|--------------|----------------|-------------|
+| Documentation Copies | Stored by Promptless | Public documentation copies for automation and change tracking |
+| Third-party Integration Data | Processed, not stored | Promptless can be triggered by third-party tools, and processes data to provide services, but does not store any data beyond the duration needed to provide documentation updates |
+| End-user Data | Not Processed | Sensitive end-user data is not processed or stored |
+
+### Data that Promptless stores
+
+Promptless stores minimal data, and otherwise operates in a stateless manner to avoid storing any data that is not necessary to provide the service.
+- **Documentation Copies**: Promptless stores copies of your documentation to enable our automation features and track changes. This documentation is typically public, and so is generally not considered sensitive data.
+- **Feedback for Promptless**: Promptless stores feedback that you provide to it about the quality of documentation updates, which can take the form of edits that you've made to Promptless suggestions, or direct feedback you've made on the Promptless dashboard.
+- **Integration Auth Data**: When you link Promptless to a third party tool, we store the data necessary to integrate with that tool. This typically includes an authentication token, not the actual content of the data from the third party tool.
+
+### Data that Promptless processes, but does not store
+
+Promptless users can integrate Promptless's services with a number of third party tools, in order to automatically trigger documentation updates or provide additional context for documentation updates. This data is used to provide the Promptless service, and is not stored by Promptless. **Promptless does not retain a copy of customer source code, support conversations, or any other data from third party integrations.**
+
+For example:
+- When a GitHub PR triggers a documentation check, we analyze the changes in real-time without storing the PR content
+- When using Slack integration, we process conversations to identify documentation needs but don't maintain copies of the conversations
+- When accessing context from tools like Linear or Jira, we only use the information to inform documentation updates at the time of generation, without storing a copy of issues or projects
+
+**Note:** Promptless does not use customer data for pre-training or fine-tuning language models.
+
+### Data that Promptless does not process
+- **End-user data**: Promptless is not configurable to process or store sensitive end-user data for your organization.
+
+## User Authentication and Access Controls
+
+### Standard Authentication Features
+
+Our platform provides robust authentication mechanisms for all users:
+- SSO with Google or GitHub supported for all users
+- Strong password policies enforcing complexity requirements
+- Two-factor authentication (2FA) support using industry-standard TOTP
+- Password reset workflows with secure verification
+
+### Enterprise Authentication Features
+
+Enterprise plan customers receive access to advanced authentication capabilities:
+
+- Single Sign-On (SSO) integration supporting major identity providers
+- SAML 2.0 support with:
+ - Just-in-time user provisioning
+ - Role mapping
+ - Certificate-based authentication
+- OpenID Connect (OIDC) compatibility for modern authentication workflows
+- Custom MFA policies and enforcement
+
+## Data Security
+
+### Encryption Standards
+- All data in transit is encrypted using TLS 1.2 or higher, ensuring secure communication between all system components
+- Data at rest (both in primary data stores and secondary backups) is protected using AES-256 encryption, with keys managed through a secure key management system
+- Backup data is encrypted using independent encryption keys for additional security
+
+## Enterprise Security Support
+
+Enterprise customers may request additional security features and support, such as custom data retention policies.
+
+
+## Questions About Data Handling?
+
+If you have specific questions about how we handle data or need more information, please contact us at help@gopromptless.ai.
+
+Promptless implements comprehensive security measures to protect customer data and ensure secure access to our platform. Our multi-layered approach to security encompasses data encryption, access controls, and robust authentication mechanisms.
+
+
diff --git a/src/content/docs/docs/security-and-privacy/network-architecture.mdx b/src/content/docs/docs/security-and-privacy/network-architecture.mdx
new file mode 100644
index 00000000..070beaa8
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy/network-architecture.mdx
@@ -0,0 +1,50 @@
+---
+title: Network Architecture
+slug: docs/security-and-privacy/network-architecture
+sidebar:
+ hidden: false
+ order: 42
+---
+import Frame from '@components/fern/Frame.astro';
+
+# Network Architecture
+
+Promptless utilizes a secure, modern cloud-based network architecture designed for reliability, security, and scalability. Our infrastructure is built on industry-leading cloud platforms with multiple layers of security controls and redundancy.
+
+## Infrastructure Overview
+
+
+
+
+
+
+Our infrastructure is designed with the following key principles:
+- Security by design at every layer
+- High availability and fault tolerance
+- Scalability and performance optimization
+- Comprehensive monitoring and observability
+
+## Multi-Tenant Security Model
+
+Promptless uses a strong logical separation model for multi-tenant data security:
+
+### Organization-Level Isolation
+
+- Every piece of data (users, suggestions, trigger events, etc.) is tagged with a specific organization ID
+- All database queries are automatically scoped to the requesting organization
+- Authorization mechanisms prevent cross-organization data access
+- No shared data contexts between different customer organizations
+
+Promptless's shared infrastructure provides increased scalability and security, since it reduces the number of infrastructure assets that need to be tracked and maintained and decreases the number of data access points across the system.
+
+## Key Security Measures
+
+While we can't highlight all of Promptless's security measures here, we've highlighted some of the key ones below:
+* Data encryption in transit: All data at rest is encrypted using TLS 1.2 or later.
+* Data encryption at rest: Data stored in Promptless's database is encrypted with AES-256.
+* Data access controls: We use a combination of access controls, including role-based access control (RBAC), to ensure that only authorized users have access to sensitive data.
+* Principle of least privilege: We only give users the minimum permissions they need for their role.
+* Logical separation of data: All data is tagged with customer identifiers, to ensure multiple layers of logical separation between Promptless users
+
+
+For more detailed information about our network architecture or to discuss specific security requirements, please contact our security team at help@gopromptless.ai.
diff --git a/src/content/docs/docs/security-and-privacy/privacy-policy.mdx b/src/content/docs/docs/security-and-privacy/privacy-policy.mdx
new file mode 100644
index 00000000..bb3ddd39
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy/privacy-policy.mdx
@@ -0,0 +1,32 @@
+---
+title: Privacy Policy
+slug: docs/security-and-privacy/privacy-policy
+sidebar:
+ hidden: false
+ order: 44
+---
+# Privacy Policy
+
+Promptless is committed to protecting your privacy and ensuring the security of your information. Our comprehensive privacy policy details how we collect, use, and protect your data when you use our services.
+
+## Privacy Policy Overview
+
+Our privacy policy covers important aspects of data handling, including:
+- Types of information we collect
+- How we use your information
+- Security measures and practices
+- Policy updates and changes
+
+## Complete Privacy Policy
+
+For the complete, current version of our privacy policy, please visit:
+[Promptless Privacy Policy](https://www.gopromptless.ai/privacy)
+
+## Privacy Inquiries
+
+For any questions about our privacy practices or to exercise your privacy rights:
+
+- Email: help@gopromptless.ai
+- Subject line: "Privacy Policy Inquiry"
+
+We aim to respond to all privacy-related inquiries within 48 business hours.
diff --git a/src/content/docs/docs/security-and-privacy/promptless-subprocessors.mdx b/src/content/docs/docs/security-and-privacy/promptless-subprocessors.mdx
new file mode 100644
index 00000000..0d7d630a
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy/promptless-subprocessors.mdx
@@ -0,0 +1,53 @@
+---
+title: Promptless Subprocessors
+slug: docs/security-and-privacy/promptless-subprocessors
+sidebar:
+ hidden: false
+ order: 43
+---
+# Promptless Subprocessors
+
+Promptless uses a number of third party services to deliver our services. This page provides high-level information about the subprocessors that Promptless uses to deliver our core docs automation service. For more detailed information about our security practices, data handling procedures, and privacy commitments, please schedule a call with our team by contacting us at help@gopromptless.ai.
+
+## Language Models and AI Infrastructure Providers
+
+Promptless is designed with a model-agnostic architecture, providing flexibility and choice in AI language models used for documentation generation. This approach offers several key advantages:
+
+Model Selection
+* Support for multiple leading language models
+* Ability to switch between different model providers
+* Custom model integration capabilities
+* Performance optimization across different model types
+
+Enterprise customers have additional flexibility:
+* Tailored hosted models by cloud providers, such as OpenAI on Azure or Anthropic on AWS
+* Use of customer-managed model deployments
+* Custom model fine-tuning options
+* Model performance monitoring and optimization
+* Dedicated model resources
+
+**Note:** We may recommend certain models for different parts of the documentation process based on what produces the best output for each use-case, but the final choice of architecture is up to you. Currently, the default configuration for cloud-hosted customers uses AWS Bedrock, though the system works with a variety of models including Anthropic, OpenAI, and open-source providers.
+
+**Note:** Regardless of model choice, Promptless does not use customer data for pre-training or fine-tuning language models.
+
+## Current Subprocessors
+
+### Infrastructure and Hosting
+- **Amazon Web Services (AWS)**
+ - Primary cloud infrastructure provider
+ - Data center locations: Primary is us-east-2, with secondary locations in other US regions
+ - Services used: EKS, EC2, S3, RDS (Aurora), Lambda
+
+### Authentication and Security
+- **Clerk**: User authentication, SSO, identity management, and security token services
+
+### Monitoring and Analytics
+- **DataDog**: Infrastructure monitoring, application performance monitoring, log management, and security monitoring
+- **Sentry**: Error tracking and monitoring
+- **Helicone**: LLM monitoring and observability
+
+### Third-party Integrations
+
+Promptless supports a number of third-party integrations that customers can choose to use in their projects, such as GitHub, Slack, Intercom, Linear, Notion, Jira, and more.
+
+For the most current information about our subprocessors or to discuss specific security requirements, please contact our security team at help@gopromptless.ai.
diff --git a/src/content/docs/docs/security-and-privacy/single-sign-on-sso-setup.mdx b/src/content/docs/docs/security-and-privacy/single-sign-on-sso-setup.mdx
new file mode 100644
index 00000000..b3b396b4
--- /dev/null
+++ b/src/content/docs/docs/security-and-privacy/single-sign-on-sso-setup.mdx
@@ -0,0 +1,96 @@
+---
+title: Single Sign-On (SSO) Setup
+slug: docs/security-and-privacy/single-sign-on-sso-setup
+sidebar:
+ hidden: false
+ order: 39
+---
+import Steps from '@components/fern/Steps.astro';
+import Step from '@components/fern/Step.astro';
+import Info from '@components/fern/Info.astro';
+
+# Single Sign-On (SSO) Setup
+
+Single Sign-On (SSO) integration enables enterprise organizations to authenticate users through their existing identity provider, streamlining access management and enhancing security across your documentation workflow.
+
++ ← Back to Blog +
++ ← Back to Blog +
+Latest post
+ + +{latest.data.description || latest.data.subtitle}
+ )} + +{entries.length === 1 ? '1 post' : `${entries.length} posts`}
++ {entry.data.description || entry.data.subtitle} +
+ )} +Latest release notes
+ + +See everything shipped in this release window.
+ +{entries.length === 1 ? '1 entry' : `${entries.length} entries`}
+