[{"data":1,"prerenderedAt":959},["ShallowReactive",2],{"search":3,"content-guide\u002Fchat":442,"surround-\u002Fguide\u002Fchat":954},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,216,220,224,228,232,236,240,244,248,252,256,260,264,268,272,276,280,284,288,292,296,300,304,308,312,316,320,323,327,331,335,339,343,347,351,355,359,363,367,371,375,379,383,387,391,395,399,403,407,411,415,419,423,426,430,434,438],{"path":5,"title":6,"description":7},"\u002Fguide","Guide","Product guides for Owlat — a modular, self-hosted email platform. Learn how to send campaigns, run a personal mailbox, manage a team inbox, and more.",{"path":9,"title":10,"description":11},"\u002Fguide\u002Fgetting-started","Welcome to Owlat","Set up your Owlat workspace and send your first email — from deploying the stack to verifying a domain, building your audience, and launching a campaign.",{"path":13,"title":14,"description":15},"\u002Fguide\u002Fcontact-properties","Contact Properties","Custom fields that extend built-in contact data with your own values for segmentation.",{"path":17,"title":18,"description":19},"\u002Fguide\u002Ftopics","Topics","Topics are explicit audience groups you manage by hand — ideal for opt-in subscribers, imported cohorts, and organized contact buckets you target with campaigns.",{"path":21,"title":22,"description":23},"\u002Fguide\u002Fsegments","Segments","Build dynamic, rule-based contact groups from properties, email activity, and topic membership, re-evaluated from current data each time they're used.",{"path":25,"title":26,"description":27},"\u002Fguide\u002Fforms","Forms","Form Endpoints collect new contacts from your website or landing pages by exposing a public endpoint that accepts submissions and feeds them into a topic.",{"path":29,"title":30,"description":31},"\u002Fguide\u002Fcampaigns","Campaigns & Reporting","Build and send marketing campaigns to a topic or segment with the five-step wizard, optional A\u002FB testing, and full delivery reporting.",{"path":33,"title":34,"description":35},"\u002Fguide\u002Fab-testing","A\u002FB Testing","Compare two variants of a campaign on a test group, then automatically or manually send the winning version to the rest of your audience.",{"path":37,"title":38,"description":39},"\u002Fguide\u002Fautomations","Automations","Send emails automatically based on triggers, delays, and conditions — build welcome series, trial flows, and follow-ups once and let Owlat run them.",{"path":41,"title":42,"description":43},"\u002Fguide\u002Ftransactional","Transactional Emails","One-to-one emails your application triggers in response to a user action — password resets, order confirmations, welcome emails, and similar notifications.",{"path":45,"title":46,"description":47},"\u002Fguide\u002Fcreate-campaign","Create a Campaign","Walk through Owlat's five-step campaign wizard: Basics, Audience, Content, A\u002FB Test, and Review & Send.",{"path":49,"title":50,"description":51},"\u002Fguide\u002Fsend-campaign","Send & Monitor a Campaign","How to send your campaign and track its performance with real-time metrics.",{"path":53,"title":54,"description":55},"\u002Fguide\u002Fquick-start","Quick Start","The fastest path from a blank Owlat workspace to a live email campaign, from your first template through sending and reviewing results.",{"path":57,"title":58,"description":59},"\u002Fguide\u002Ftransactional-setup","Transactional Email Setup","Set up and send transactional emails like password resets and order confirmations via the Owlat API and SDKs.",{"path":61,"title":62,"description":63},"\u002Fguide\u002Fdeliverability","Deliverability","Verify sending domains, manage your blocklist, monitor sending reputation, and stay compliant so your emails reach the inbox.",{"path":65,"title":66,"description":67},"\u002Fguide\u002Fapi-keys-webhooks","API Keys & Webhooks","Create API keys for programmatic access and set up outbound webhooks to receive real-time notifications for email and contact events.",{"path":69,"title":70,"description":71},"\u002Fguide\u002Ffeature-flags","Feature flags","Owlat is modular — every feature listed in this guide can be turned on or off. This page is the user-facing overview of how to do it.",{"path":73,"title":74,"description":75},"\u002Fguide\u002Fteam-permissions","Team & Permissions","Use role-based access to control what each member of your organization can do, with Owner, Admin, and Editor roles.",{"path":77,"title":78,"description":79},"\u002Fguide\u002Faudit-logs","Audit Logs","A chronological record of significant actions in your Owlat organization, so you can see who did what and when.",{"path":81,"title":82,"description":83},"\u002Fguide\u002Fshare-links","Share Links","Create temporary preview links to share email designs with stakeholders who don't have dashboard access.",{"path":85,"title":86,"description":87},"\u002Fguide\u002Fpostbox","Postbox — Personal Email","Per-user mailboxes with a webmail interface and native IMAP\u002FSMTP support. Run your own Gmail-equivalent personal mailbox on your Owlat instance.",{"path":89,"title":90,"description":91},"\u002Fguide\u002Fmigrate-from-google","Migrate from Google","Import your full Gmail history into Owlat over IMAP, and let your AI assistant learn from every imported conversation.",{"path":93,"title":94,"description":95},"\u002Fguide\u002Fteam-inbox","Team Inbox","Triage inbound email as a team: read AI-classified threads, approve, edit or reject agent drafts, work the review queue, and manage quarantine.",{"path":97,"title":98,"description":99},"\u002Fguide\u002Femail-editor","Email Editor","A block-based visual editor for building responsive emails that render consistently across desktop, mobile, Outlook, Gmail, and Apple Mail.",{"path":101,"title":102,"description":103},"\u002Fguide\u002Fai-agent","AI Agent & Autonomy","Configure the AI agent that classifies and drafts replies to inbound mail: auto-reply settings, the health dashboard, circuit breakers, autonomy rules, and the knowledge backfill.",{"path":105,"title":106,"description":107},"\u002Fguide\u002Fknowledge-graph","Knowledge Graph","Browse, search, and manage Owlat's typed organizational knowledge — the 7 entry types, source attribution, confidence decay, relations, and how entries are extracted from mail.",{"path":109,"title":110,"description":111},"\u002Fguide\u002Ffiles","Files","Upload, browse, search, tag, and version documents in the file library.",{"path":113,"title":114,"description":115},"\u002Fguide\u002Fchat","Team Chat","Use Owlat's built-in team chat: public and private channels, direct messages, mentions, attachments, and channels linked to an inbox conversation.",{"path":117,"title":118,"description":119},"\u002Fguide\u002Fcode-tasks","Code Tasks","Queue coding-agent tasks, watch them move from queued through review, and run the code-worker sidecar that opens the pull requests.",{"path":121,"title":122,"description":123},"\u002Fguide\u002Faudience-data","Audience Data: Identities, Relationships & Timeline","Unify a contact across email, phone, and messaging channels, merge duplicates, map relationships, and read the cross-channel interaction timeline.",{"path":125,"title":126,"description":127},"\u002Fguide\u002Fimporting-contacts","Importing & Exporting Contacts","Bring contacts into Owlat from a CSV or from Mailchimp and Stripe, export them back out, and run bulk operations on your audience.",{"path":129,"title":130,"description":131},"\u002Fguide\u002Faccount","Your Account & Data","Export your data as JSON or CSV, request account deletion with a 30-day grace period, and use the onboarding checklist and the public preference center.",{"path":133,"title":134,"description":135},"\u002Fguide\u002Fchannels","Communication Channels","Configure SMS, WhatsApp, and generic-webhook channels, monitor channel health, and understand which channels are fully live today.",{"path":137,"title":138,"description":139},"\u002Fguide\u002Fdesktop-app","Desktop App","Install the Owlat desktop app, connect one or more workspaces, switch between them, and use native notifications, tray badges, shortcuts, and deep links.",{"path":141,"title":142,"description":143},"\u002Fguide\u002Femail-templates","Email Templates","Reusable email designs that define the structure, content, and personalization of every campaign and transactional message you send in Owlat.",{"path":145,"title":146,"description":147},"\u002Fguide\u002Fai-assistant","AI Assistant","Owlat's multi-turn, streaming, tool-calling AI assistant — a private chat surface that can search your workspace and draft copy, plus @assistant replies inside team chat.",{"path":149,"title":150,"description":151},"\u002Fguide\u002Fsecurity-scanning","Sending Security & Scanning","Owlat's security scanning: a content check for spam and phishing, an attachment scan for malware, and a Google Safe Browsing URL check. Suspicious content goes to a review queue.",{"path":153,"title":154,"description":155},"\u002Fguide\u002Fsystem-updates","System & Updates","The owner-only System & Updates screen: your current Owlat version, container health, LLM spend, and the in-app one-click updater with history.",{"path":157,"title":158,"description":159},"\u002Fguide\u002Foperating-modes","Operating Modes","The different ways to run Owlat at a company — read external mailboxes over IMAP, send transactional or marketing email through a delivery provider, host your own mail server, or run a team inbox with AI — and the rules that keep each combination coherent.",{"path":161,"title":162,"description":163},"\u002Fguide\u002Fsaved-blocks","Saved Blocks","Create reusable, linked content blocks you can drop into any email — edit one and every email that uses it updates automatically.",{"path":165,"title":166,"description":167},"\u002Fguide\u002Fmedia-library","Media Library","Manage, organize, search, and reuse images and files across your emails from one centralized hub.",{"path":169,"title":170,"description":171},"\u002Fguide\u002Femail-theme","Email Theme","Set your organization's default colors, font, and email width so every new template starts from a consistent baseline.",{"path":173,"title":174,"description":175},"\u002Fguide\u002Ftranslations","Translations","Send one email in multiple languages: add per-language translations to a single template and Owlat picks the right version for each recipient.",{"path":177,"title":178,"description":179},"\u002Fguide\u002Fcontacts","Contacts","How to add, view, organize, and manage contacts in Owlat, including sources, the contact detail tabs, and subscription compliance.",{"path":181,"title":182,"description":183},"\u002Fapi","API Overview","Owlat exposes authenticated API endpoints under your Convex site URL.",{"path":185,"title":186,"description":187},"\u002Fapi\u002Fwebhooks","Webhooks","Owlat supports both outbound customer webhooks and inbound provider webhooks.",{"path":189,"title":190,"description":191},"\u002Fapi\u002Fpublic-endpoints","Public Endpoints","These routes are public-facing and usually accessed from email links or embedded forms.",{"path":193,"title":194,"description":195},"\u002Fapi\u002Fwebhook-payloads","Webhook Payloads","The authoritative wire contract for outbound webhooks: envelope, signature headers, per-event data shapes, and payload versioning.",{"path":197,"title":198,"description":199},"\u002Fapi\u002Finbound-channels","Inbound Channel Webhooks","Provider webhook reference for inbound SMS, WhatsApp, and generic-channel messages, plus the MTA mailbox and credential callbacks.",{"path":201,"title":202,"description":203},"\u002Fapi\u002Fauthentication","Authentication","Secure API access with organization-scoped API keys.",{"path":205,"title":206,"description":207},"\u002Fapi\u002Fsdk","TypeScript SDK","Typed client for the Owlat API, usable from Node.js, Bun, Deno, or any server-side JavaScript runtime.",{"path":209,"title":210,"description":211},"\u002Fapi\u002Fsdk-java","Java SDK","The official `owlat-sdk` package provides a typed client for interacting with the Owlat API from any JVM application. Requires Java 11+.",{"path":213,"title":214,"description":215},"\u002Fapi\u002Fcontacts","Contacts API","Manage contacts for your organization.",{"path":217,"title":218,"description":219},"\u002Fapi\u002Ftopics","Topics API","Manage topic membership through authenticated endpoints.",{"path":221,"title":222,"description":223},"\u002Fapi\u002Fevents","Events API","Send contact events to drive segmentation and automation triggers.",{"path":225,"title":226,"description":227},"\u002Fapi\u002Ftransactional","Transactional API","Send published transactional templates to a recipient.",{"path":229,"title":230,"description":231},"\u002Fapi\u002Fforms","Forms API","Capture subscribers through public form endpoints.",{"path":233,"title":234,"description":235},"\u002Fdeveloper","Developer Guide","Technical architecture, feature-flag model, and provider abstractions used by Owlat.",{"path":237,"title":238,"description":239},"\u002Fdeveloper\u002Fmta-system","MTA System","Owlat's custom Mail Transfer Agent for direct SMTP delivery with intelligent rate limiting, bounce processing, and IP warming.",{"path":241,"title":242,"description":243},"\u002Fdeveloper\u002Ffeature-flags","Feature flags — developer reference","How the Owlat feature flag system works: single source of truth, dependency resolution, docker profile mapping, and how to add a new flag.",{"path":245,"title":246,"description":247},"\u002Fdeveloper\u002Fhow-email-works","How Email Works","A technical deep-dive into how email actually works — from SMTP and DNS to authentication, deliverability, and the differences between marketing and private email.",{"path":249,"title":250,"description":251},"\u002Fdeveloper\u002Femail-security","Email Security","Content scanning, attachment validation, URL reputation checking, and malware detection for outbound emails.",{"path":253,"title":254,"description":255},"\u002Fdeveloper\u002Fpostbox-architecture","Postbox Architecture","How the Postbox personal-mail feature is wired — schema, IMAP server, app-password auth, outbound relay, inbound delivery, and external mailboxes.",{"path":257,"title":258,"description":259},"\u002Fdeveloper\u002Fproviders","Providers","Pluggable provider abstractions for LLM, email sending, notifications, vector stores, and analytics, selected per-deployment so self-hosters can swap implementations without code changes.",{"path":261,"title":262,"description":263},"\u002Fdeveloper\u002Fcampaign-internals","Campaign Internals","How the campaign backend works: two status machines, send pre-flight, the send orchestrator, emailSends records, and the priority workpools.",{"path":265,"title":266,"description":267},"\u002Fdeveloper\u002Faudience-internals","Audience Internals","Backend reference for contact resolution, the double opt-in lifecycle, topic subscription, the conditions registry, and segment evaluation.",{"path":269,"title":270,"description":271},"\u002Fdeveloper\u002Fautomation-internals","Automation Internals","How the automation run engine works: the step walker, the lifecycle state machine, trigger fanout, the three step types, and the resilience cron.",{"path":273,"title":274,"description":275},"\u002Fdeveloper\u002Fdeliverability-infrastructure","Deliverability Infrastructure","The Convex-side deliverability backend: provider routing, health-aware failover, sending reputation with auto-enforcement, IP warming cache, the blocklist, and the content-scan gate.",{"path":277,"title":278,"description":279},"\u002Fdeveloper\u002Farchitecture","Architecture Overview","Owlat follows a modern serverless architecture with real-time capabilities.",{"path":281,"title":282,"description":283},"\u002Fdeveloper\u002Fplatform-operations","Platform Operations","Operator reference for abuse status and the sending gate, the platform-admin roster, content review, org deletion, in-app self-update, dev endpoints, crons, and migrations.",{"path":285,"title":286,"description":287},"\u002Fdeveloper\u002Fscopes","Scopes","What each app and package in the Owlat monorepo is responsible for.",{"path":289,"title":290,"description":291},"\u002Fdeveloper\u002Fself-hosting","Self-Hosting","Deploy Owlat on your own infrastructure with Docker Compose. Complete guide from first boot to production.",{"path":293,"title":294,"description":295},"\u002Fdeveloper\u002Fself-hosting-config","Self-Hosting Configuration","Complete reference for Docker environment variables, Convex backend variables, service topology, and volume persistence.",{"path":297,"title":298,"description":299},"\u002Fdeveloper\u002Fself-hosting-dns-email","DNS & Email Setup","Configure DNS records, DKIM signing, SPF, DMARC, and bounce handling for reliable email delivery.",{"path":301,"title":302,"description":303},"\u002Fdeveloper\u002Fself-hosting-production","Production Deployment","Secure your self-hosted Owlat instance with TLS, firewall rules, backups, and monitoring.",{"path":305,"title":306,"description":307},"\u002Fdeveloper\u002Fself-hosting-maintenance","Maintenance & Updates","Keep your self-hosted Owlat instance up to date, manage backups, scale performance, and troubleshoot common issues.",{"path":309,"title":310,"description":311},"\u002Fdeveloper\u002Fself-hosting-desktop","Desktop Installer","Install Owlat on a bare Linux VPS straight from the desktop app over SSH — no terminal — with a live, animated provisioning timeline.",{"path":313,"title":314,"description":315},"\u002Fdeveloper\u002Fsetup-cli","Setup CLI & Installer","Operator reference for the Owlat self-host tooling: the install.sh one-liner, the owlat-setup CLI, the convex-deploy flow, and admin bootstrap.",{"path":317,"title":318,"description":319},"\u002Fdeveloper\u002Fconvex","Convex Backend","Owlat uses Convex as its serverless backend, providing real-time subscriptions, ACID transactions, and TypeScript-first development.",{"path":321,"title":202,"description":322},"\u002Fdeveloper\u002Fauthentication","Owlat uses BetterAuth with the Convex adapter for authentication and organization (team) management.",{"path":324,"title":325,"description":326},"\u002Fdeveloper\u002Femail-system","Email System","Owlat's email system consists of a visual editor, template management, and multi-provider sending infrastructure.",{"path":328,"title":329,"description":330},"\u002Fdeveloper\u002Femail-renderer","Email Renderer","The @owlat\u002Femail-renderer package converts editor JSON blocks into production-ready HTML emails with cross-client compatibility, CSS inlining, dark mode, and Outlook VML fallbacks.",{"path":332,"title":333,"description":334},"\u002Fdeveloper\u002Fenvironment-variables","Environment Variables","Reference for every environment variable Owlat reads across the Convex backend, web app, MTA, IMAP server, and mail-sync worker.",{"path":336,"title":337,"description":338},"\u002Fdeveloper\u002Fcomponents","Component Library","Reference for the reusable, auto-imported Vue UI components shipped in the packages\u002Fui layer.",{"path":340,"title":341,"description":342},"\u002Fdeveloper\u002Fdecisions","Architectural Decision Records","The architectural decision records for the Owlat project, each capturing the context, the decision, and the trade-offs involved.",{"path":344,"title":345,"description":346},"\u002Fdeveloper\u002Fdecisions\u002F009-model-routing","ADR-009: Task-Based Model Routing","Why Owlat supports per-task LLM model selection instead of using a single model for all pipeline steps.",{"path":348,"title":349,"description":350},"\u002Fdeveloper\u002Fdecisions\u002F010-listing-engine","ADR-010: Listing Engine","Why Owlat replaced four incompatible list-query contracts with one generic listing engine driven by per-entity descriptors.",{"path":352,"title":353,"description":354},"\u002Fdeveloper\u002Fdecisions\u002F001-custom-email-renderer","ADR-001: Custom Email Renderer Over MJML","Why Owlat built a custom table-based HTML email renderer instead of using MJML, gaining full control over VML, dark mode, and per-client rendering.",{"path":356,"title":357,"description":358},"\u002Fdeveloper\u002Fdecisions\u002F002-convex-backend","ADR-002: Convex as Backend","Why Owlat chose Convex over PostgreSQL and Firebase for real-time reactivity, co-located TypeScript logic, and zero-config scaling.",{"path":360,"title":361,"description":362},"\u002Fdeveloper\u002Fdecisions\u002F003-notion-like-builder","ADR-003: Notion-like Email Builder","Why Owlat replaced the traditional 3-panel email editor with a Notion-like single-column canvas for inline WYSIWYG editing.",{"path":364,"title":365,"description":366},"\u002Fdeveloper\u002Fdecisions\u002F004-monorepo-bun-workspaces","ADR-004: Monorepo with Bun Workspaces","Why Owlat uses a monorepo with Bun workspaces and Turborepo for fast installs, atomic cross-package changes, and cached CI.",{"path":368,"title":369,"description":370},"\u002Fdeveloper\u002Fdecisions\u002F005-custom-mta","ADR-005: Custom MTA","Why Owlat built a custom Mail Transfer Agent instead of relying solely on third-party email providers.",{"path":372,"title":373,"description":374},"\u002Fdeveloper\u002Fdecisions\u002F006-self-hosted-convex","ADR-006: Self-Hosted Convex","Why Owlat uses the open-source Convex backend for self-hosting instead of migrating to a different database.",{"path":376,"title":377,"description":378},"\u002Fdeveloper\u002Fdecisions\u002F007-pluggable-llm","ADR-007: Pluggable LLM Provider","Why Owlat uses the Vercel AI SDK with a provider abstraction layer instead of hardcoding a single LLM vendor.",{"path":380,"title":381,"description":382},"\u002Fdeveloper\u002Fdecisions\u002F008-process-architecture","ADR-008: Agent Process Architecture","Why Owlat processes inbound messages with a self-scheduling step walker plus a lifecycle coordinator instead of one sequential function.",{"path":384,"title":385,"description":386},"\u002Fexamples","Examples","Copy-pasteable integration patterns for common Owlat use cases.",{"path":388,"title":389,"description":390},"\u002Fexamples\u002Fwelcome-email","Welcome Email","Send a personalized welcome email when a new user signs up.",{"path":392,"title":393,"description":394},"\u002Fexamples\u002Fbilling-email","Billing Email","Send a billing receipt with an invoice PDF attached after a successful payment.",{"path":396,"title":397,"description":398},"\u002Fexamples\u002Fevent-automation","Event Automation","Trigger automations with custom events for trial lifecycle, feature adoption, and more.",{"path":400,"title":401,"description":402},"\u002Fexamples\u002Fcontact-sync","Contact Sync","Sync contacts from your database to Owlat using upsert patterns and bulk operations.",{"path":404,"title":405,"description":406},"\u002Fexamples\u002Fwebhook-handler","Webhook Handler","Handle Owlat delivery webhooks with signature verification and event routing.",{"path":408,"title":409,"description":410},"\u002Fexamples\u002Fmultilingual-email","Multilingual Email","Send emails in the recipient's preferred language using template translations.",{"path":412,"title":413,"description":414},"\u002Fvision","Vision","Where Owlat is heading — from email platform to unified communication intelligence powered by AI agents.",{"path":416,"title":417,"description":418},"\u002Fvision\u002Fself-hosting","Self-Hosting Architecture","How Owlat runs as a fully self-hosted stack using Docker Compose — open-source Convex backend, custom MTA, and a pluggable LLM provider.",{"path":420,"title":421,"description":422},"\u002Fvision\u002Fagent-pipeline","Agent Pipeline","Technical architecture for the inbound email agent pipeline — step modules, the walker, security scanning, threading, and human review.",{"path":424,"title":106,"description":425},"\u002Fvision\u002Fknowledge-graph","Technical architecture for Owlat's typed knowledge storage — how organizational knowledge is stored, searched, decayed, and maintained.",{"path":427,"title":428,"description":429},"\u002Fvision\u002Fmulti-channel","Multi-Channel & CRM","Technical architecture for channel adapters, unified messaging, contact identity unification, and the CRM hub.",{"path":431,"title":432,"description":433},"\u002Fvision\u002Ffile-system","Semantic File System","Technical architecture for Owlat's semantic file storage — version tracking with provenance today, plus the planned embedding-based retrieval and auto-tagging layer.",{"path":435,"title":436,"description":437},"\u002Fvision\u002Fdesktop-app","Desktop App & Advanced Agents","Architecture of the Owlat desktop shell, visualization agent, adaptive dashboard, agent health, graduated autonomy, and coding agents.",{"path":439,"title":440,"description":441},"\u002Fvision\u002Froadmap","Roadmap","What's planned next for Owlat — the documented-but-unbuilt pieces still being wired, and the enhancements on our radar.",{"id":443,"title":114,"body":444,"description":115,"extension":948,"meta":949,"navigation":950,"path":113,"seo":951,"stem":952,"__hash__":953},"content\u002F1.guide\u002F33.chat.md",{"type":445,"value":446,"toc":925},"minimark",[447,465,485,496,501,508,557,560,565,584,588,603,607,614,618,624,641,647,651,666,692,696,707,711,721,736,739,742,776,779,795,798,802,816,820,829,860,869,872,876,920],[448,449,450,451,454,455,459,460,464],"p",{},"Team chat is Owlat's built-in, Slack-style messaging surface for your team. It lives next to the ",[452,453,94],"a",{"href":93}," so the people handling customer email can talk to each other in the same app — and even pin a customer conversation inside a channel to discuss it together. Chat lives at ",[456,457,458],"strong",{},"Dashboard → Chat"," (",[461,462,463],"code",{},"\u002Fdashboard\u002Fchat",").",[466,467,470],"callout",{"title":468,"type":469},"Behind a feature flag","info",[448,471,472,473,476,477,480,481,484],{},"Team chat is gated by the ",[461,474,475],{},"chat"," feature flag and is off by default. An owner or admin enables it under feature flags before the ",[456,478,479],{},"Chat"," area appears. See ",[452,482,483],{"href":69},"Feature Flags",".",[448,486,487,488,491,492,484],{},"Any team member can take part in chat. Renaming, archiving, managing members, and linking email threads are reserved for ",[456,489,490],{},"room admins"," (and for owners\u002Fadmins, who can govern any room). See ",[452,493,495],{"href":494},"#channel-members-and-roles","Channel members and roles",[497,498,500],"h2",{"id":499},"channels","Channels",[448,502,503,504,507],{},"A ",[456,505,506],{},"channel"," is a named room for a topic, team, or project. Channels come in two flavors:",[509,510,511,527],"table",{},[512,513,514],"thead",{},[515,516,517,521,524],"tr",{},[518,519,520],"th",{},"Visibility",[518,522,523],{},"Who can see it",[518,525,526],{},"Who can post",[528,529,530,544],"tbody",{},[515,531,532,538,541],{},[533,534,535],"td",{},[456,536,537],{},"Public",[533,539,540],{},"Every team member can browse and read it",[533,542,543],{},"Members only — readers must join first",[515,545,546,551,554],{},[533,547,548],{},[456,549,550],{},"Private",[533,552,553],{},"Only its members; hidden from everyone else",[533,555,556],{},"Members only",[448,558,559],{},"Channel names are unique across the workspace (case-insensitive), capped at 80 characters, and an optional description can be up to 280 characters.",[561,562,564],"h3",{"id":563},"create-a-channel","Create a channel",[448,566,567,568,571,572,575,576,579,580,583],{},"From the chat sidebar, click ",[456,569,570],{},"New channel",". Give it a name, an optional description, and choose ",[456,573,574],{},"public"," or ",[456,577,578],{},"private",". You can also add a few teammates as initial members while creating it. Whoever creates the channel becomes its first ",[456,581,582],{},"admin","; any initial members you add join as plain members.",[561,585,587],{"id":586},"browse-and-join","Browse and join",[448,589,590,591,594,595,598,599,602],{},"Click ",[456,592,593],{},"Browse channels"," to see every public channel in the workspace and join the ones you want. You can also open a public channel without joining — you'll see its history in a read-only preview with a ",[456,596,597],{},"Join to send messages"," banner at the top. Click ",[456,600,601],{},"Join"," to start posting. Private channels never show up in browse; you only reach them by being invited.",[561,604,606],{"id":605},"archive-a-channel","Archive a channel",[448,608,609,610,613],{},"A room admin can ",[456,611,612],{},"archive"," a channel. Archived channels drop out of the sidebar and the browse list, and no one can post to them, but their history is preserved. An admin can unarchive a channel later to bring it back.",[497,615,617],{"id":616},"direct-messages","Direct messages",[448,619,503,620,623],{},[456,621,622],{},"direct message (DM)"," is a private conversation between you and one or more teammates — 1:1 or a small group.",[625,626,627,635,638],"ul",{},[628,629,630,631,634],"li",{},"Start one with ",[456,632,633],{},"New DM"," in the sidebar and pick the people to include.",[628,636,637],{},"DMs are deduplicated by their participant set: starting a DM with the same people always reopens the existing conversation rather than creating a duplicate.",[628,639,640],{},"The sidebar labels a 1:1 DM with the other person's name; a group DM shows the first few names plus a \"+N more\" suffix.",[466,642,644],{"title":643,"type":469},"DMs can't be left or edited",[448,645,646],{},"You can't add or remove people in an existing DM, and you can't leave one — to change the participants, just start a new DM with the people you want. (Channels work differently: members come and go freely.)",[497,648,650],{"id":649},"sending-editing-and-deleting-messages","Sending, editing and deleting messages",[448,652,653,654,657,658,661,662,665],{},"Type in the composer at the bottom of a room and press ",[456,655,656],{},"Enter"," to send; ",[456,659,660],{},"Shift+Enter"," inserts a newline. Messages are plain text (up to 8,000 characters) and ",[461,663,664],{},"@","-mentions are highlighted inline. You must be a member of the room to post — opening a public channel as a non-member shows the preview banner instead of a composer.",[625,667,668,677],{},[628,669,670,673,674,484],{},[456,671,672],{},"Edit"," — hover your own message and click the pencil. Only the author can edit a message; edited messages are marked ",[456,675,676],{},"edited",[628,678,679,682,683,686,687,691],{},[456,680,681],{},"Delete"," — hover and click the trash icon. You can delete your own messages; a ",[456,684,685],{},"room admin"," (or an owner\u002Fadmin) can delete anyone's. Deletes are soft: the message is replaced with ",[688,689,690],"em",{},"\"this message was deleted\""," rather than removed outright.",[561,693,695],{"id":694},"read-tracking-and-unread-badges","Read tracking and unread badges",[448,697,698,699,702,703,706],{},"Owlat tracks how far you've read in each room. When you're viewing a room, it's marked read automatically as new messages arrive. The sidebar shows an ",[456,700,701],{},"unread count"," per room for messages you haven't seen (your own messages and deleted messages don't count). Very busy rooms are shown as ",[456,704,705],{},"100+"," rather than an exact number.",[497,708,710],{"id":709},"mentions","Mentions",[448,712,713,714,716,717,720],{},"Type ",[461,715,664],{}," in the composer to bring up a picker of teammates; choosing one inserts a handle like ",[461,718,719],{},"@alice.smith",". Handles resolve against each person's email local-part or their slugified name.",[625,722,723,730,733],{},[628,724,725,726,729],{},"A resolved mention notifies that person ",[456,727,728],{},"only if they're a member of the room"," — mentioning a non-member in a private channel or DM is silently dropped, so a message preview never leaks to someone without access.",[628,731,732],{},"Mentioning yourself never notifies you.",[628,734,735],{},"Your unread mentions feed a separate badge so a direct ping stands out from ordinary unread activity. Mentions are cleared as you read the room they were posted in.",[497,737,495],{"id":738},"channel-members-and-roles",[448,740,741],{},"Every room has a membership list with two per-room roles:",[509,743,744,754],{},[512,745,746],{},[515,747,748,751],{},[518,749,750],{},"Role",[518,752,753],{},"Can do",[528,755,756,766],{},[515,757,758,763],{},[533,759,760],{},[456,761,762],{},"Member",[533,764,765],{},"Read and post in the room",[515,767,768,773],{},[533,769,770],{},[456,771,772],{},"Admin",[533,774,775],{},"Everything a member can, plus: rename and re-describe the channel, archive\u002Funarchive it, add and remove members, promote\u002Fdemote other members, and link or unlink an email thread",[448,777,778],{},"A few guardrails keep channels governable:",[625,780,781,788],{},[628,782,783,784,787],{},"A channel always keeps at least one admin — you can't leave, demote, or remove the ",[456,785,786],{},"last"," admin without handing the role to someone else first.",[628,789,790,791,794],{},"Owners and admins of the workspace hold the ",[461,792,793],{},"chat:manage"," permission, which lets them administer any channel (and delete any message) even if they aren't a per-room admin. This is the escape hatch for governing rooms they didn't create.",[448,796,797],{},"Open the members panel from the room header to see who's in a room and manage roles. Leaving a room is for channels only — DMs can't be left.",[497,799,801],{"id":800},"attachments","Attachments",[448,803,804,805,808,809,811,812,815],{},"Attach files to a message with the paperclip button, or paste an image directly into the composer. Each file is capped at ",[456,806,807],{},"25 MiB",". Uploaded files become first-class assets in your ",[452,810,166],{"href":165}," (tagged ",[461,813,814],{},"chat-attachment","), so they're browsable there too. Attachment download links are gated on room access: only members of a private channel or DM can fetch the files posted in it.",[497,817,819],{"id":818},"linking-a-channel-to-an-inbox-conversation","Linking a channel to an inbox conversation",[448,821,822,823,826,827,484],{},"A channel can be ",[456,824,825],{},"linked to an inbox conversation thread"," so the whole team can discuss a customer email in context. This is the bridge between team chat and the ",[452,828,94],{"href":93},[830,831,832,836,846,850,853,857],"steps",{},[561,833,835],{"id":834},"open-the-link-dialog","Open the link dialog",[448,837,838,839,842,843,484],{},"In a channel header, a room admin clicks ",[456,840,841],{},"Link an email thread"," and searches the workspace's inbox threads. Once a thread is already linked, the button reads ",[456,844,845],{},"Change linked email",[561,847,849],{"id":848},"pick-a-thread","Pick a thread",[448,851,852],{},"Choose the conversation to attach. The channel can carry one linked thread at a time; linking a new one replaces the previous link.",[561,854,856],{"id":855},"discuss-in-context","Discuss in context",[448,858,859],{},"A pinned, read-only panel appears at the top of the channel showing the conversation's subject, status, and recent inbound messages. Your team discusses it in the channel below.",[466,861,863],{"title":862,"type":469},"Replies still go through the inbox",[448,864,865,866,868],{},"The linked panel is read-only — it's for discussion, not for replying. Customer replies still flow through the ",[452,867,94],{"href":93}," and its review and approval pipeline. From an inbox thread you can also see #channel chips for any channels that reference it and jump straight there.",[448,870,871],{},"Only channels can be linked — DMs cannot. A room admin can remove the link at any time from the same dialog.",[497,873,875],{"id":874},"permissions-at-a-glance","Permissions at a glance",[509,877,878,888],{},[512,879,880],{},[515,881,882,885],{},[518,883,884],{},"Capability",[518,886,887],{},"Who",[528,889,890,902,912],{},[515,891,892,895],{},[533,893,894],{},"Read public channels, post (after joining), DMs, mentions, attachments",[533,896,897,898,901],{},"Any team member (",[461,899,900],{},"chat:participate",")",[515,903,904,907],{},[533,905,906],{},"Rename \u002F archive a channel, manage members, link an email thread",[533,908,909,910,901],{},"The channel's admins, or workspace owners\u002Fadmins (",[461,911,793],{},[515,913,914,917],{},[533,915,916],{},"Delete another person's message",[533,918,919],{},"Message author, the room's admins, or workspace owners\u002Fadmins",[448,921,922,923,484],{},"For how chat fits into the wider role model, see ",[452,924,74],{"href":73},{"title":926,"searchDepth":927,"depth":927,"links":928},"",2,[929,935,936,939,940,941,942,947],{"id":499,"depth":927,"text":500,"children":930},[931,933,934],{"id":563,"depth":932,"text":564},3,{"id":586,"depth":932,"text":587},{"id":605,"depth":932,"text":606},{"id":616,"depth":927,"text":617},{"id":649,"depth":927,"text":650,"children":937},[938],{"id":694,"depth":932,"text":695},{"id":709,"depth":927,"text":710},{"id":738,"depth":927,"text":495},{"id":800,"depth":927,"text":801},{"id":818,"depth":927,"text":819,"children":943},[944,945,946],{"id":834,"depth":932,"text":835},{"id":848,"depth":932,"text":849},{"id":855,"depth":932,"text":856},{"id":874,"depth":927,"text":875},"md",{},true,{"title":114,"description":115},"1.guide\u002F33.chat","Q3PAbIKSkeEyVyyKYykUwBtQKC_mPu38wYlzSB4IsNc",[955,957],{"title":110,"path":109,"stem":956,"children":-1},"1.guide\u002F32.files",{"title":118,"path":117,"stem":958,"children":-1},"1.guide\u002F34.code-tasks",1782846430989]