Real team workflow examples,
not hypotheticals
Six ways teams actually use Team Relay to collaborate in Obsidian — engineering, product, support, distributed teams, onboarding, and leadership. Pick the one closest to your team.
These are team workflow examples drawn from how teams actually run Team Relay day to day: a shared Obsidian vault, edited live by more than one person, staying in sync across engineering, product, support, and leadership — without turning into a merge-conflict mess or leaving Obsidian for a different tool.
Specs that stay live for humans and AI agents alike
A PRD or architecture doc lives in the vault. Two engineers edit it together during a design review, changes land in real time, and Claude Code or Codex reads the same file through Team Relay's MCP server — so the agent's context and the humans' context are never out of sync with each other.
Two engineers co-edit an architecture doc, decisions captured as they're made.
Claude Code reads the current spec via MCP — not a version copy-pasted three revisions ago.
Product & design
Live roadmaps, published to the world
PM and designer co-edit a roadmap doc during planning, embedding images and comments inline. When it's ready, the same note is web-published as a public roadmap page — no copy into a separate CMS.
Support & customer success
One internal KB, always current
Support agents co-edit troubleshooting runbooks as they resolve tickets, so the fix goes into the shared knowledge base the same day — not weeks later in a backlog of "update the docs" tasks.
Distributed & remote teams
Async across time zones, no merge conflicts
Someone in Berlin edits a note while someone in São Paulo edits the same file hours later. CRDT sync merges both — no "who has the latest version" thread, no overwritten paragraphs.
Onboarding new hires
One onboarding doc, kept current by everyone
The onboarding folder gets small fixes from whoever notices something's out of date — a new hire reading it this week sees the current process, not what was true when the doc was first written.
Leadership & exec reporting
Strategy docs, drafted together, published selectively
Founders co-write a quarterly strategy note in real time, then publish an edited version externally via web-publish — internal drafting and external communication from the same source note.
These workflows, without Team Relay
| Notion / Confluence | Google Docs | Plain Obsidian Sync | Team Relay | |
|---|---|---|---|---|
| Real-time co-editing | ✓ | ✓ | ✗ | ✓ |
| Files stay local Markdown | ✗ | ✗ | ✓ | ✓ |
| AI agents read via MCP | Custom API | Custom API | File system only | ✓ |
| Publish selected notes externally | Limited | ✗ | ✗ | ✓ |
| Pricing model | Per-seat | Per-seat (Workspace) | Free | Free self-hosted, flat hosted |
Team Relay use cases — FAQ
Common questions about applying these workflows to your own team.
What are some real Team Relay use cases?
Engineering teams keeping specs and PRDs live for both humans and AI coding agents; product/design teams co-editing roadmaps and publishing them as public pages; support teams maintaining a shared internal knowledge base; distributed teams collaborating across time zones without merge conflicts; onboarding docs that stay current for every new hire; and leadership publishing internal strategy docs to a curated external page.
Do these workflows require everyone to know Obsidian already?
No. Real-time collaboration in Team Relay looks and feels like editing any shared document — cursors, presence, live text. Non-technical teammates (support, product, leadership) use it the same way they'd use a Google Doc; the Obsidian-specific features (plugins, linking, graph view) are optional extras for people who want them.
Can I use these workflows without self-hosting?
Yes. The hosted tier gets any of these workflows running in minutes with no server to manage. Self-hosting is available for teams that want full data control, and both share the same real-time collaboration engine.
How is this different from Notion or Confluence for these use cases?
Same collaborative editing experience, but your notes stay as local Markdown files you own — no vendor lock-in, works with your existing Obsidian vault and plugins, and AI coding agents can read the same files directly via the MCP server rather than through a proprietary API.
Find your team's workflow
Try the hosted tier free, or deploy self-hosted for full data control.