Local notes / PRODUCT DOSSIER

Obsidian + Sync

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

Investigation: Where should a small team keep shared knowledge? →

Official website ↗Explore in graph →12 cited claims ↓

Obsidian core app plus official Sync for shared vaults; Publish is a separately identified add-on. Excludes community collaboration plugins. · Not established · Obsidian app and service terms; Sync and Publish are separate subscriptions.Revision 2026-09-15.1 · unreviewedNeeds recheck · recheck 2026-10-150 attestations · checked 2026-09-15

What we do not know yet · 3 open gaps

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?

Applies to: 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.

Applicability, 2 recheck triggers & verification plan

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.

Excludes: Executed collaboration, recovery or migration tests; Unlisted third-party plugins and integrations; AI quality, security certification and performance rankings; Unlisted editions and plan entitlements

Recheck when

Changes to app versions, plan entitlements, sharing policies or license terms.
Changes to offline caching, synchronization, recovery retention or export formats.

Needs recheck · due 2026-10-15

Verification plan

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

Provenance & review

Testedknowhow collaboration research

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

Revision 2026-09-15.1 · unreviewed · checked 2026-09-15

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Capability claims · 12 / 17 sourced

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

Collaboration

Document authoringYes

Explore Document authoring →

Edits locally stored Markdown notes.

Scope: Core app; community plugins excluded.

[1]

Live co-editingNo

Explore Live co-editing →

Official shared vaults do not support live editing on the same file.

Scope: Changes appear after synchronization; third-party plugins excluded.

[2]

Shared knowledge spaceYes

Explore Shared knowledge space →

Shares a vault through official Sync.

Scope: Every collaborator needs an active Sync subscription.

[2]

Access control

Distinct collaborator rolesNo

Explore Distinct collaborator roles →

Official shared vaults do not provide distinct viewer and editor roles.

Scope: Collaborators share owner-like permissions; only the owner can invite.

[2]

Per-document accessNo

Explore Per-document access →

Official shared vaults lack fine-grained content permissions.

Scope: Vault sharing only; separate vaults require a separate sharing design.

[2]

Organization

BacklinksYes

Explore Backlinks →

Shows linked and unlinked incoming note references.

Scope: Core Backlinks plugin.

[3]

Content searchYes

Explore Content search →

Searches note and canvas content.

Scope: Excluded files and unsupported attachment bodies are outside content search.

[4]

Continuity & portability

Version recoveryYes

Explore Version recovery →

Can inspect and restore synchronized changes.

Scope: Official Sync history; retention depends on the plan.

[2]

Offline editingYes

Explore Offline editing →

Stores notes on the device for offline use.

Scope: Remote collaboration waits for synchronization.

[1]

Portable contentYes

Explore Portable content →

Keeps notes in local open-format files.

Scope: Native Markdown portability; plugin data and full workspace behavior need separate checks.

[1]

Web publication or public linkYes

Explore Web publication or public link →

Publishes notes as a web knowledge base.

Scope: Separate Obsidian Publish add-on; not implied by Sync.

[1]

End-to-end encrypted syncYes

Explore End-to-end encrypted sync →

Supports end-to-end encrypted shared vaults.

Scope: Collaborators require the vault encryption password; no independent security audit.

[2]

Unknown · 5 capabilities without evidence

Interface images & local attachments

Screenshots & attachments

Image index

Official project screenshots and your own reference images. Images illustrate a UI; they do not verify feature behavior. Uploads stay in this browser.

No screenshots gathered yet.