vendor-documentation · locator & rights
Subscriptions; permissions; live editing; version history
Link and original paraphrase only; upstream rights retained.
Continuity & portability / FEATURE
End-to-end encrypted sync
Vendor documents that synchronized content is encrypted with keys unavailable to the service operator. This is not an independent security audit.
2connected products
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.
2 products have Yes or Partial documentation. Review freshness and attestation counts describe the dossier, not runtime quality. Gaps below are product-wide, not necessarily specific to this feature.
Unknown — no evidence recorded
3 open gaps · applicability & verification plan
What we do not know yet about Notion
- 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?
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.
Hosted Notion workspace; desktop/mobile required for the cited offline mode.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Unknown — no evidence recorded
3 open gaps · applicability & verification plan
What we do not know yet about Google Docs
- 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?
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.
Google Docs in Google Workspace; Drive storage and organization are a separate target.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Unknown — no evidence recorded
4 open gaps · applicability & verification plan
What we do not know yet about Google Drive
- 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?
- Document editing, offline editing and document revision recovery are not inherited from Google Docs in this Drive dossier.
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.
Google Workspace Drive, including shared drives where enabled; excludes Docs, Sheets and Slides editing engines.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Unknown — no evidence recorded
3 open gaps · applicability & verification plan
What we do not know yet about Coda (Superhuman Docs)
- 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?
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.
Hosted Coda document workspace; current branding is Superhuman Docs. Pack behavior is excluded.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Unknown — no evidence recorded
3 open gaps · applicability & verification plan
What we do not know yet about Confluence Cloud
- 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?
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.
Confluence Cloud with the space features enabled; excludes Data Center and Marketplace apps.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Unknown — no evidence recorded
4 open gaps · applicability & verification plan
What we do not know yet about Microsoft Loop
- 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?
- Resolve the conflict between the overview and the dated guest-permissions guide on an authorized test tenant.
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.
Work or school Microsoft 365 tenant; excludes personal-account and Copilot-specific capabilities.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Unknown — no evidence recorded
4 open gaps · applicability & verification plan
What we do not know yet about AFFiNE
- 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?
- The README describes CE as MIT, while root licensing routes backend/native code to separate terms. Resolve exact build and component licensing before deployment.
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Repository revision 2af30773aecd567f09b346e7b72fc69143144057; deployed release not pinned.
AFFiNE clients with a selected cloud or self-hosted backend; pin edition and team entitlements.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
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.
3 open gaps · applicability & verification plan
What we do not know yet about Obsidian + Sync
- 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?
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Sources · 1
End-to-end encrypted syncYes
Explore End-to-end encrypted sync →
Encrypts shared content before synchronization.
Scope: Keys are shared with invited participants; security not independently audited.
4 open gaps · applicability & verification plan
What we do not know yet about Anytype
- 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?
- Immediate sync is documented, but simultaneous same-document co-editing semantics have not been established in this package.
Applicability
Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Desktop repository revision 14cf1e6efcb4e3bf2d425afe92fdfecc1f603574.
Anytype clients and a chosen Anytype or self-hosted network; per-object permission boundaries are excluded.
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
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
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Sources · 1
vendor-documentation · locator & rights
Shared spaces; roles; per-object limitations; offline sync
Link and original paraphrase only; upstream rights retained.