# Obsidian + Sync

Local Markdown notes with shared-vault synchronization; official Sync is distinct from live co-editing.

Revision: 2026-09-15.1 · Review: unreviewed

Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

## Applicability

Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.. Obsidian core app plus official Sync for shared vaults; Publish is a separately identified add-on. Excludes community collaboration plugins..

## Claims

- **yes · documented**: Edits locally stored Markdown notes. [Obsidian overview](https://obsidian.md/) Scope: Core app; community plugins excluded.
- **yes · documented**: Shares a vault through official Sync. [Obsidian shared vaults](https://obsidian.md/help/sync/collaborate) Scope: Every collaborator needs an active Sync subscription.
- **yes · documented**: Can inspect and restore synchronized changes. [Obsidian shared vaults](https://obsidian.md/help/sync/collaborate) Scope: Official Sync history; retention depends on the plan.
- **yes · documented**: Stores notes on the device for offline use. [Obsidian overview](https://obsidian.md/) Scope: Remote collaboration waits for synchronization.
- **yes · documented**: Keeps notes in local open-format files. [Obsidian overview](https://obsidian.md/) Scope: Native Markdown portability; plugin data and full workspace behavior need separate checks.
- **yes · documented**: Shows linked and unlinked incoming note references. [Obsidian backlinks](https://obsidian.md/help/Plugins/Backlinks) Scope: Core Backlinks plugin.
- **yes · documented**: Searches note and canvas content. [Obsidian search](https://obsidian.md/help/Plugins/Search) Scope: Excluded files and unsupported attachment bodies are outside content search.
- **yes · documented**: Publishes notes as a web knowledge base. [Obsidian overview](https://obsidian.md/) Scope: Separate Obsidian Publish add-on; not implied by Sync.
- **yes · documented**: Supports end-to-end encrypted shared vaults. [Obsidian shared vaults](https://obsidian.md/help/sync/collaborate) Scope: Collaborators require the vault encryption password; no independent security audit.
- **no · documented**: Official shared vaults do not support live editing on the same file. [Obsidian shared vaults](https://obsidian.md/help/sync/collaborate) Scope: Changes appear after synchronization; third-party plugins excluded.
- **no · documented**: Official shared vaults do not provide distinct viewer and editor roles. [Obsidian shared vaults](https://obsidian.md/help/sync/collaborate) Scope: Collaborators share owner-like permissions; only the owner can invite.
- **no · documented**: Official shared vaults lack fine-grained content permissions. [Obsidian shared vaults](https://obsidian.md/help/sync/collaborate) Scope: Vault sharing only; separate vaults require a separate sharing design.

## Open questions

- Which client versions, plan and administrator policies apply to the team?
- What survives a representative export: links, attachments, comments, permissions and history?
- How do simultaneous edits, temporary disconnection and member departure behave on the chosen setup?

## Verification plan

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Last checked: 2026-09-15. Recheck by: 2026-10-15.

Content rights: Unlicensed prototype; redistribution decision pending.