A shared document workspace
Investigate co-editing, comments and access restrictions together; compare the actual plan and tenant settings.
Productivity & collaboration · docs and knowledge / RESEARCH IN PROGRESS
Where should a small team keep shared knowledge?
Compare how a team writes together, limits access and keeps its knowledge portable. Editors, shared drives and synchronized note vaults have different boundaries; this investigation has no executed results or overall winner.
A scoped answer, with choices.
- Use synthetic meeting notes, a decision log, a small structured table, linked pages and two attachments.
- Distinguish live editing of the same document from file sync and public link sharing.
- Model an owner, an editor, a viewer and an external collaborator; define which content each may access.
- Choose plans, client versions and tenant policies before comparing feature availability.
- Treat document export separately from complete migration of history, comments, permissions and links.
An editor plus a shared file repository
Evaluate Google Docs and Drive as separate components: editing behavior and file ownership need distinct evidence.
Local notes with synchronization
Prioritize local content and portability, then verify collaboration and permissions. Obsidian Sync explicitly lacks live co-editing; Anytype permissions apply at space level.
Claims you can inspect.
Exports accessible pages as HTML or Markdown and database data as CSV.
Exports omit inaccessible content and do not recreate the complete workspace on reimport.
Source: Notion backups and export
Export entire workspace; exclusions; reimport limitation · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Distinguishes viewer, commenter and editor access.
Organization policy and inherited access apply.
Source: Google file sharing
Sharing basics; simultaneous editors; viewer/commenter/editor · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Shared drives retain team files when a contributor leaves.
Work or school accounts with shared drives enabled.
Source: Google shared drives
Shared ownership; files remain after departure; member roles · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Continues editing an already loaded document while offline.
Initial load needs internet; closing or refreshing offline can lose unsynced changes.
Source: Coda offline documents
Offline limitations; lost changes on close or refresh · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗The permissions guide allows guest sharing under tenant conditions; the overview still says external sharing is unavailable.
Unresolved documentation conflict. Confirm tenant, guest identity, sensitivity labels and actual behavior before relying on it.
Source: Microsoft Loop permissions
Content permissions; guest sharing requirements · Checked 2026-09-15
2026-05-14
Inspect original source ↗Source: Microsoft Loop overview
Pages, components, workspaces; known external-sharing limitation · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Official shared vaults do not support live editing on the same file.
Changes appear after synchronization; third-party plugins excluded.
Source: Obsidian shared vaults
Subscriptions; permissions; live editing; version history · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Cannot assign permissions separately for each object.
All space members can view every object in that space.
Source: Anytype collaboration
Shared spaces; roles; per-object limitations; offline sync · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Exports content to local formats but omits chats and discussions.
Desktop export; member references may not survive migration.
Source: Anytype import and export
Desktop formats; files and linked objects; excluded chats and members · Checked 2026-09-15
Living documentation; client and plan not pinned
Inspect original source ↗Evaluate a small shared knowledge fixture
This is a procedure draft, not a working implementation. Package versions and executable artifacts are not yet pinned.
Define the required boundaries
Record whether live same-document editing, per-document restrictions, offline work and portable export are mandatory. Choose a plan and client version for each shortlisted target.
Expected: An explicit requirements sheet; Partial, No and Unknown remain separate.
Authorize an isolated trial
Before execution, agree on test accounts, resource and subscription limits. Create only authorized disposable workspaces with synthetic content. Do not invite real colleagues or upload private files.
Expected: Named accounts and disposable resources with approved access and costs.
Exercise writing and review
On two authorized accounts, edit distinct and overlapping text, add feedback, reconnect after a brief interruption and record what each client displays. For Drive, evaluate file handling separately from its editor.
Expected: Captured edits and observed conflicts or delays; synchronization is not mislabeled live co-editing.
Probe access and departure
Use owner, editor, viewer and external test accounts to check direct links, inherited access, search visibility and one restricted page. Remove only a disposable member and check ownership and retained content. Record local copies separately from revoked server access.
Expected: Observed access boundaries and retained knowledge, including any unsupported per-document restriction.
Check offline work and recovery
Follow each target’s documented preparation, edit a disposable note offline and reconnect. Test close/reopen behavior only with a backed-up synthetic fixture. Make a reversible test edit and restore an earlier version where supported.
Expected: A result for each supported client and plan, including lost edits or unavailable recovery. Preserve raw evidence.
Export and inspect independently
Export the fixture using the documented formats and open it outside the product. Check text, table values, links, attachments, comments, member references and history separately. Record missing parts; clean up only named trial resources.
Expected: A portability checklist with real artifacts and explicit losses; no universal migration claim.
What would count as evidence?
Not attempted
Two editors retain the intended synthetic changes, or the failure is recorded.
Not attempted
Viewer and external accounts cannot alter or view content outside their chosen permissions; unsupported boundaries are recorded.
Not attempted
Prepared offline edits survive reconnect and the explicitly tested close/reopen sequence, or the target fails that requirement.
Not attempted
Team content remains accessible to its intended owner after a disposable collaborator leaves.
Not attempted
Exported text, tables and attachments are independently readable; lost links, comments, history and permissions are listed.
Not attempted
No documentation claim is relabeled as tested; future execution evidence requires the schema extension.
Resolve before calling this a recipe that works
- No multi-user editing, access-control, offline-recovery or migration experiment has run.
- Loop overview and permissions documentation conflict on guest sharing; the chosen tenant must resolve applicability.
- Exact AFFiNE backend edition and license scope require confirmation before a self-hosted deployment.
- Costs, data retention and identity policies depend on the selected accounts and plans.