Knowledge workspace / PRODUCT DOSSIER

Microsoft Loop

Shared pages and portable components within a Microsoft 365 tenant.

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

Official website ↗Explore in graph →6 cited claims ↓

Work or school Microsoft 365 tenant; excludes personal-account and Copilot-specific capabilities. · Not established · Microsoft 365 product terms and applicable subscription agreement.Revision 2026-09-15.1 · unreviewedNeeds recheck · recheck 2026-10-150 attestations · checked 2026-09-15

What we do not know yet · 4 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?
Resolve the conflict between the overview and the dated guest-permissions guide on an authorized test tenant.

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

Applicability, 2 recheck triggers & verification plan

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 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 · 6 / 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 →

Authors flexible pages containing notes and components.

Scope: Loop pages in the work/school app.

[1]

Live co-editingYes

Explore Live co-editing →

Provides real-time co-authoring in shared content.

Scope: Supported Loop clients and Microsoft 365 context.

[3]

Shared knowledge spaceYes

Explore Shared knowledge space →

Groups project content into shared workspaces.

Scope: Workspace creation depends on tenant policy and entitlement.

[1]

Access control

Distinct collaborator rolesYes

Explore Distinct collaborator roles →

Can share pages or components with edit or read-only access.

Scope: Workspace members have edit access to every page in that workspace.

[2]

Per-document accessYes

Explore Per-document access →

Supports sharing an individual page or component.

Scope: Page links do not reduce access already granted by workspace membership.

[2]

External collaboratorsPartial1 contradictions

Explore External collaborators →

The permissions guide allows guest sharing under tenant conditions; the overview still says external sharing is unavailable.

Scope: Unresolved documentation conflict. Confirm tenant, guest identity, sensitivity labels and actual behavior before relying on it.

Contradictions

microsoft-loop-overview

[1][2]

Unknown · 11 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.