Think of a Loop component not as something you create inside an app, but as a living block of content that you can place across different apps. This is the core of component-first collaboration: the data lives in the component itself, which acts as the single source of truth. You are simply surfacing that live data in Teams, Outlook, or OneNote.

This approach fundamentally changes workflow. Instead of copying and pasting information between apps, which creates stale copies, you embed one live component. An update made in a Teams chat is instantly reflected in the same component pinned in a OneNote project notebook. It's a single, synchronized block of content with multiple windows.

A component's behavior adapts to its environment. Where you place it should depend on the kind of collaboration you need.

For example, you might start a task list component in a Teams chat during a project sync. After the meeting, you can send that same component in an Outlook email to a wider group for awareness. Finally, you can embed it into your project's OneNote page, where it will live as the official record of tasks, always up to date no matter where it's edited.

Efficiently creating and managing components relies on two key commands: the forward slash (/) and the at-symbol (@).

The '/' command is your insertion tool. Typing / in a supported app brings up a menu of components you can add on the fly. This goes beyond simple lists. You can instantly insert a Progress Tracker to visualize project milestones, a Q&A table for an impromptu FAQ session, or a full-fledged Task List.

The '@' mention system is where orchestration becomes powerful. When you're inside a Task List component, typing '@' and selecting a person’s name doesn't just tag them—it assigns them the task. This action triggers notifications across the Microsoft 365 ecosystem, sending an alert to their Outlook inbox and a notification in their Teams activity feed. The person can view and act on the task from wherever they receive the alert.

Because components are independent files, they have their own history and permissions. At the top of any component, you can see who has access and click to manage sharing settings. You can generate a link that grants access to the component itself, separate from the chat or document where it's hosted. This allows you to bring in a collaborator on a specific piece of information without giving them access to the entire conversation.

Mistakes are easy to fix. Every Loop component maintains its own version history. Simply click the component's title or the 'See who has access' icon and find the 'Version History' option. This allows you to view previous versions and restore them if needed, providing a safety net for collaborative work. It's like an 'undo' button that works across every app the component lives in.

Adopting a component-first workflow means you spend less time hunting for information and more time acting on it. With a single source of truth for your tasks, tables, and notes, your team stays aligned, no matter which app they prefer to work in.