Build a Knowledge Council Hub in Loop

Create a cross-team collaboration workspace in Microsoft Loop.

Introduction

30 Second Summary

When your team collaborates across half a dozen tools, important documents end up homeless. A charter lives in someone's email, meeting notes scatter across SharePoint folders, and initiative tracking gets buried in a spreadsheet only two people check.

In this project, you will build a Knowledge Council workspace in Microsoft Loop that gives your cross-team council a single collaboration hub. You will also map your entire tool ecosystem to determine exactly where Loop fits alongside everything you already use.

What You'll Build

A fully functional Knowledge Council workspace in Microsoft Loop with living pages for your charter, meetings, and initiative tracking, plus a tool ecosystem map that defines what stays, what moves, and what Loop cannot replace.

By the end of this project, you'll have:

A shared Loop workspace with a council charter, meeting hub, and initiatives tracker ready to share with your 7-member cross-team council.
A synced Loop component embedded in a Teams chat that updates in real time across apps, proving the cross-app collaboration model works.
A Tool Ecosystem Map showing exactly where Loop sits alongside SharePoint, SmartSheets, Salesforce Knowledge, Jira, and Confluence with a clear recommendation for your leadership.
Secret Mission: Build a Coaching Standards page with a synced table component that works across Loop, Teams, and Outlook for cross-team AQI reporting.

Are there any prerequisites?

You need a Microsoft 365 work or school account with Loop access and Microsoft Teams access. No additional software or setup is required.

Create the Knowledge Council Workspace

Your Knowledge Council needs a home. Right now the charter lives nowhere permanent, meeting notes are scattered across email threads, and initiative tracking is buried in tools that not everyone can access.

In this step, you'll create a dedicated workspace in Microsoft Loop and invite all 7 council members. By the end, everyone has access from day one.

In this step, get ready to:

Create a workspace named "Knowledge Council" in Microsoft Loop.
Invite Jessica and the other 5 council members.
Understand how Loop connects to SharePoint behind the scenes.

Navigate to Loop and create a new workspace

Loop is a web app included with your Microsoft 365 subscription. You'll access it through your browser and create the workspace that becomes the council's operational hub.

Open your browser and go to loop.cloud.microsoft.
If prompted, sign in with your work account.
Click Add new workspace.
In the Title field, enter Knowledge Council.
Add an icon if you'd like (this is optional).
In the Invite the team field, type @ followed by Jessica's name to find and select her.
Repeat for each of the other 5 council members.
Click Continue.
In the description field, enter Cross-team hub for KCS standards, coaching alignment, and knowledge strategy.
Click Create.

Your workspace is now live. You'll land on an untitled page inside it.

What is a Loop workspace?

A workspace is a shared space where everyone you invited can see and edit pages together. Think of it as a lightweight team site designed for active collaboration rather than static document storage.

Every page you create inside this workspace is automatically accessible to all 7 members. No sharing links or permission requests needed.

Don't see the Add new workspace button?

Make sure you're signed in with your work account (not a personal Microsoft account). If the button still doesn't appear, your IT admin may have disabled workspace creation. Why can't I create a Loop workspace with my work account?

Also confirm you have a valid OneDrive license. Accounts without OneDrive storage may have limited Loop functionality.

Understand how Loop connects to SharePoint

Your workspace looks like a brand-new app, but it's built on infrastructure you already use.

Where does Loop actually store your content?

Loop files (.loop format) are stored in SharePoint and OneDrive behind the scenes. Your organization's existing governance, permissions, and compliance policies still apply.

The difference is purpose. SharePoint is designed for document storage and publishing (your content standards PDFs, reference docs, policies). Loop is designed for active collaboration where people edit together in real time. They use the same backend but serve different roles.

Your existing SharePoint content doesn't need to move. Loop sits on top as the collaboration layer.

Explore the workspace structure

Look at the left navigation panel in your workspace.
Notice the untitled page that was automatically created when you made the workspace.

This left panel is where pages will stack up as you create them. It becomes the council's table of contents. Every page you add here is accessible to all workspace members without extra sharing steps.

Why not just use a Teams channel or SharePoint site?

Teams channels are optimized for chat-style conversations. SharePoint sites are optimized for document libraries. Loop workspaces are optimized for living documents that multiple people edit simultaneously.

For a 7-person council that needs a charter, meeting system, and initiative tracker that everyone co-owns, Loop's page-based workspace fits better than a chat thread or a folder of files.

Your workspace is ready and your team has access. Next up, you'll build the council's first living document: the charter page.

Build the Council Charter Page

Your Knowledge Council workspace is live and your council members have access. Now it's time to fill it with content that actually drives the council's work.

The council's charter currently has no permanent home. In this step, you'll turn that untitled default page into a living charter document with a clear mission, member roles, and a decision log that the entire council can edit together in real time.

In this step, get ready to:

Create the Knowledge Council Charter page with section headings.
Add a Members table component with all 7 council members.
Build a Decision Log with assignable tasks.

Create the Charter page

A charter gives the council a shared definition of what it exists to do, who's involved, and how decisions get made. Instead of a static document that lives in a folder, this will be a Loop page that any council member can update at any time.

In your Knowledge Council workspace, click the untitled page's title area.
Type Knowledge Council Charter as the page title.
Press / (forward slash) to open the insert menu.
Select Heading and type Mission.
Below the heading, type the council's mission statement: Support, strengthen, and standardize KCS practices across CxO teams.
Press / again and add a Heading called Scope.
Repeat to add headings for Membership and Decision-Making Process.

What does the / menu do?

Pressing / anywhere on a Loop page opens the insert menu. This lets you add tables, checklists, lists, dates, callouts, and other components without leaving the keyboard.

You should now see four section headings stacked on your page: Mission (with the statement below it), Scope, Membership, and Decision-Making Process.

Add a Members table component

The council needs a clear record of who's involved, what team they represent, and what they focus on. A table component keeps this information visible and editable by all members.

Click below the Membership heading.
Press / and select Table.
Create four columns: Name, Team, Role, Focus Area.
Fill in the 7 council members. For example, Jessica's row would be: Jessica | Council Lead | Cross-team alignment.
Add your own row: [Your name] | MPS Knowledge | Knowledge Administration & Standards.
Fill in the remaining 5 members with their team, role, and focus area.

Why a Loop table instead of a SharePoint document?

This table is a live component that stays current as roles evolve. In a SharePoint Word doc, someone has to open the file, edit it, save it, and hope nobody else is editing at the same time.

In Loop, everyone sees and edits the same live content simultaneously. No version conflicts, no stale copies floating around in email attachments.

Your table should now show all 7 council members with their team, role, and focus area filled in.

Don't see the Table option in the / menu?

Make sure you're clicking below the Membership heading before pressing /. The insert menu appears wherever your cursor is positioned on the page. If you still don't see it, try scrolling down in the menu as Table may be further in the list.

Help me find the Table component in the Loop insert menu.

Add a Decision Log

Councils make decisions over time, and those decisions need to be tracked somewhere visible. A task list component lets you assign each open decision to a specific member and mark it complete when resolved.

Click below the Decision-Making Process section.
Press / and select Task list.
Label the component Open Decisions.
Add a task item: Finalize content standard template.
Add another task item: Agree on coaching cadence across teams.
Assign each decision to a council member using the assignee field.

How does this compare to tracking decisions in Jira?

If you currently track decisions in Jira tickets, Loop's task list is lighter-weight. There are no sprint boards, no workflows, and no project overhead.

The tradeoff is simplicity for accessibility. Non-technical council members who don't live in Jira can easily see, edit, and resolve decisions without needing a Jira account.

Your Open Decisions task list should now show both placeholder items with assignees. Each task has a checkbox that any council member can mark complete when a decision is finalized.

Can't assign a task to a council member?

The assignee field uses @ mentions. Make sure you type @ followed by the council member's name. If a member doesn't appear in the suggestions, confirm they were invited to the workspace in Step 1.

Help me assign tasks in a Loop task list component.

Your charter page is complete with a mission statement, member roles, and a live decision tracker. Next up, you'll build a Meeting Hub with a reusable template so every council sync follows a consistent format.

Create a Meeting Hub with a Reusable Template

Your charter gives the council a home for its identity and decisions. The next challenge is meeting coordination. Right now, meeting agendas and notes are ad hoc. Someone types them in a chat, or they end up in a one-off document nobody can find afterwards.

In this step, you'll build a Meeting Hub page with a structured section for agendas, notes, and action items. Then you'll save it as a reusable template so every future council meeting starts with the same consistent format.

In this step, get ready to:

Create a Meeting Hub page in your Knowledge Council workspace.
Build a meeting section with an agenda checklist, notes area, and action items tracker.
Save the page as a workspace template for future meetings.

Create the Meeting Hub page

The Meeting Hub will be the council's go-to page for every sync. Instead of scattered notes across chats and emails, everything lives in one structured place.

In the left navigation panel of your Knowledge Council workspace, click Create new.
Select Page.
Click the title area at the top and type Meeting Hub.
Below the title, add a brief description: Use this page for council meeting agendas, notes, and action items. Each meeting gets a section below.

You should see your new Meeting Hub page appear in the left navigation alongside the Knowledge Council Charter.

Build a meeting section

Each council meeting will get its own section on this page. You'll build the first one now with all three components a good meeting needs: an agenda, a notes area, and tracked action items.

Press / to open the insert menu.
Select Heading and type a dated title: 2026-06-05 Council Sync.

Why a dated heading?

Each meeting section starts with a date so the page becomes a chronological record. As the council adds more meetings, everyone can scroll to find past discussions and decisions.

Below the heading, press / and select Checklist.
Add the following sample agenda items:
Review content standards draft
Coaching alignment update from each team
Knowbler integration status

What is Knowbler?

Knowbler is an AI-powered knowledge management tool made by SearchUnify. It integrates with Salesforce to auto-generate knowledge articles from case data. It operates entirely inside Salesforce and does not integrate with Microsoft Loop directly.

Below the checklist, type Notes as a label, then press Enter to create a blank paragraph area where members can type discussion notes during the meeting.
Below the notes area, press / and select Task list.
This Task list is for Action Items. Each task can be assigned to a council member with a due date.

Your Meeting Hub page should now have a dated heading, a Checklist with three agenda items, a Notes paragraph section, and a Task list for Action Items.

Don't see the Task list or Checklist options?

Make sure you're pressing / (forward slash) on a new line. The insert menu only appears when your cursor is at the start of an empty line.

If you still don't see these component types, confirm that your account has a valid OneDrive license. People without a valid OneDrive license may have limited Loop component access.

Help me troubleshoot missing component types in Loop

Save the page as a template

You've built a great meeting structure. The problem is that without a template, someone would need to recreate this layout from scratch for every meeting. Saving it as a template means any council member can spin up a new meeting page with the correct format in seconds.

Click the ... menu (More Page options) at the top of your Meeting Hub page.
Select Save page as template.
In the title field, type Council Meeting Notes.
Click Save as template.

How do council members use this template?

For every future meeting, any workspace member can create a new page from this template. The path is: Create new > Page > Use a Loop template > My workspace templates.

The template is saved in your workspace and accessible only to workspace members. They'll see "Council Meeting Notes" in the list and can select it to start a new meeting page with the full structure pre-filled.

Why Loop templates over Confluence templates?

Confluence templates serve the same purpose. The difference is where the resulting pages live. Confluence pages require a separate browser tab and a Confluence login. Loop pages live inside Teams and Outlook as synced components. Council members interact with meeting content from the tools they already have open.

Verify the template was saved by clicking Create new > Page > Use a Loop template > My workspace templates.
You should see Council Meeting Notes listed as an available template.
Press Escape or click away to close the template picker without creating a new page.

Don't see your template in the list?

Make sure you selected My workspace templates (not a different template category). The template only appears in the workspace where it was created.

If the template still doesn't appear, return to the Meeting Hub page, click the ... menu again, and confirm that Save page as template is available. Try saving again with the title Council Meeting Notes.

Help me find my saved Loop template

Your Meeting Hub is ready and templated. Next up, you'll build an Initiatives Tracker to test whether Loop can handle the kind of project tracking you currently do in SmartSheets.

Build an Initiatives Tracker

Your Meeting Hub gives the council a consistent format for every sync. Now you need somewhere to track what the council is actually working on between meetings.

This step tests whether Loop can replace the kind of project tracking you currently do in SmartSheets. You'll build an Initiatives Tracker page with assigned tasks, due dates, and milestone progress that all 7 council members can see and update.

In this step, get ready to:

Create an Initiatives Tracker page with a description.
Add a Task list component with real council initiatives, owners, and due dates.
Add a Progress tracker component with key milestones.

Create a new page called Initiatives Tracker

In the left navigation panel of your Knowledge Council workspace, click Create new > Page.
Click the title area at the top of the new page and type Initiatives Tracker.
Below the title, type a brief description: Active council initiatives with owners, status, and target dates.

You should now see a new page titled "Initiatives Tracker" in the left navigation alongside your Charter and Meeting Hub pages.

Insert a Task list component with council initiatives

Loop's Task list component lets you assign work to specific people with due dates. Each task shows assignee, due date, and completion status.

Below your description, press / to open the insert menu.
Select Task list from the menu.
Add your first task: type Define unified content standard template. Assign it to yourself and set the due date to 2026-07-01.
Add a second task: Establish coaching cadence expectations. Assign it to Jessica.
Add a third task: Evaluate Knowbler pilot criteria. Assign it to whoever CC designates for that work.
Add a fourth task: Build cross-team article quality reporting. Assign it to yourself.

Your Task list should now show four initiatives, each with an assignee and status indicator.

Where SmartSheets is still stronger

SmartSheets has Gantt charts, automations, conditional formatting, and forms for data intake. Loop's task list is simpler but lives where people already work.

For council-level initiative tracking (7 people, a dozen items), Loop is sufficient. For your detailed Knowledge Cleanup Project with hundreds of rows and formulas, SmartSheets or Excel remains the right tool.

Add a Progress tracker component

The Progress tracker gives Jessica and the council a visual at-a-glance view of where key milestones stand. This is something a static SharePoint doc cannot provide.

Below your Task list, press / to open the insert menu again.
Select Progress tracker.
Add your first milestone: Content Standards v1 finalized.
Add a second milestone: Coaching framework documented.
Add a third milestone: Knowbler pilot launched.

Your Initiatives Tracker page now has both a detailed task list and a high-level progress view.

Why both a Task list and a Progress tracker?

The Task list tracks granular work items with owners and due dates. The Progress tracker shows milestone-level status that's easy to scan in a meeting or quick check-in.

SmartSheets can do this too, but it requires everyone to have SmartSheets access and navigate to the right sheet. Loop keeps this visible inside Teams and Outlook.

Don't see Progress tracker in the menu?

Make sure you're pressing / on a blank line below your Task list. If you're typing inside an existing component, the insert menu won't appear. Click outside the Task list first, then press /.

help me find the Progress tracker component in Loop

Your workspace now has three pages covering the council's core needs: a charter, meetings, and active work tracking. Next up, you'll connect this content to Teams so council members can interact with it without ever opening Loop directly.

Connect Loop to Teams with a Synced Component

Your Knowledge Council workspace now has a charter, meeting hub, and initiative tracker. The content is organized and ready for collaboration. There's one problem: most council members spend their day in Microsoft Teams, not in the Loop app.

In this step, you'll bridge that gap by sharing Loop components directly inside a Teams chat. Edits made in Teams sync back to Loop instantly, so council members never need to leave their primary workspace to participate.

In this step, get ready to:

Share a Loop task list component in a Teams group chat.
Copy the Initiatives Tracker component from your workspace into Teams.
Test real-time sync between Loop and Teams.

Share a Loop component in a Teams chat

Loop components aren't limited to the Loop app. You can create them directly inside a Teams chat, where everyone in the conversation can edit inline without switching apps.

Press Cmd+Space (macOS) or the Windows key (Windows) to open your search bar.
Type Teams and press Enter to open Microsoft Teams.
Find or create a group chat with council members. If you want to test first, create a chat with just yourself.
In the compose box at the bottom of the chat, select Loop components.
Select Task list from the component types.
Add a few items from your Initiatives Tracker, such as "Define unified content standard template" with your name and a due date of 2026-07-01.
Click Send.

Everyone in the chat can now edit this task list directly inside Teams.

What is a Loop component in Teams?

A Loop component in Teams is a live, editable block of content that stays connected to Loop. Unlike sharing a link to a file (where someone has to click through to open it), a Loop component renders right inside the chat message.

This is the key differentiator from SharePoint and SmartSheets. The content meets people where they already are instead of asking them to navigate to a separate tool.

Don't see the Loop components option?

The Loop components option only appears for users with a valid OneDrive license. If you don't see it in the compose box, check with your IT team that your account has OneDrive access enabled.

help me find the Loop components option in Teams

Copy a component from your workspace into Teams

Creating a fresh component in Teams is useful, but the real power is sharing an existing component from your Loop workspace. This means the same task list lives in both places and stays in sync.

Switch back to your Knowledge Council workspace in Microsoft Loop (the browser tab from earlier).
Open the Initiatives Tracker page from the left navigation.
Hover over the task list component (the one with your four council initiatives).
Click the Copy link icon in the upper-right corner of the component.
Switch back to your Teams group chat.
Click into the compose box and paste with Ctrl+V (Windows) or Cmd+V (macOS).
Click Send.

This component is now live in both Loop and Teams. Edits in either place sync instantly.

Why copy from the workspace instead of creating fresh?

When you copy a component link from your workspace and paste it into Teams, it's the same component in both places. Any edit syncs across all locations in real time.

If you created a new task list directly in Teams instead, it would be a separate component. You'd end up with two lists to maintain. Copying the link keeps everything as a single source of truth.

How does this compare to SharePoint or SmartSheets?

You can link to a SharePoint file or a SmartSheets dashboard from Teams, but you can't edit it inline inside a Teams message. Loop components are the only option that lets council members interact with shared content without leaving the conversation.

Test the sync

Seeing the sync in action is what makes this feature click. A quick test proves the component is truly connected across both apps.

In Teams, edit the task list component you just pasted. Mark a task complete or add a new task item.
Switch back to your Loop workspace and open the Initiatives Tracker page.
Confirm that your change from Teams appears on the task list in Loop.

The change should appear almost instantly. This is the core value proposition for the council: members who live in Teams never need to open Loop separately, while you and Jessica can manage everything from the workspace view.

Test the reverse direction too

Try editing the task list in Loop (add a new task or change a due date) and confirm it updates in your Teams chat. Two-way sync means either app is a valid entry point for the same content.

Changes not syncing between Loop and Teams?

Make sure you pasted the copied component link and didn't just type similar content in Teams. The sync only works when both locations reference the same underlying component.

Try refreshing both the Loop browser tab and your Teams window. Real-time sync requires an active connection.

help me troubleshoot Loop component sync between Teams and the Loop app

Your Loop workspace is now connected to Teams. Council members can interact with shared content from wherever they already work. Next up, you'll map your entire tool ecosystem to clarify exactly where Loop fits alongside SharePoint, SmartSheets, Salesforce, and everything else.

Map Your Tool Ecosystem

Your Knowledge Council workspace is live and connected to Teams. Council members can now access the charter, track initiatives, and collaborate on meeting agendas from wherever they already work.

The final piece is the most important one for your recommendation to Jessica and CC. You need a clear map showing exactly where Loop fits alongside everything your teams already use. This page becomes the evidence behind your recommendation.

In this step, get ready to:

Create a Tool Ecosystem Map page with a table covering all 10 tools your team uses.
Write a summary of what moves to Loop and what stays put.
Document Loop's limitations honestly so your recommendation is credible.

Create the Tool Ecosystem Map page

This page is the key deliverable for your recommendation to Jessica and CC. It shows where every tool fits in the council's workflow and draws a clear line between what moves to Loop and what stays where it is.

In the left navigation of your Knowledge Council workspace, click Create new > Page.
Title the page Tool Ecosystem Map.
Add a brief description below the title: Active council initiatives with owners, status, and target dates.

Wait, that description is for the Initiatives Tracker. Use this description instead:

Type this description below the title: "Where each tool fits in the council's workflow and what moves to Loop."
Press / to open the insert menu and select Table.
Set up four columns: Tool, What It Does for the Council, Stays/Moves/Complements Loop, Notes.

Now fill in each row. Here is what to enter for each tool:

SharePoint | Stores content standards docs, policies, reference materials | Stays (Loop stores its files IN SharePoint. SharePoint = document archive. Loop = collaboration layer on top.) | Content standards PDFs don't move. Loop links to them.
SmartSheets | Coaching forms, detailed trackers (Knowledge Cleanup), automations | Stays for complex tracking and forms. Loop replaces only lightweight initiative tracking. | SmartSheets forms have no Loop equivalent. Keep SmartSheets for data intake.
Salesforce Knowledge | Knowledge base articles, case-linked content, article lifecycle | Stays entirely. Loop has zero integration with Salesforce. | Loop is for council coordination. Salesforce is for the KB itself.
Knowbler (if approved) | AI-generated article drafts from cases inside Salesforce | Stays inside Salesforce Service Console. Complements Loop. | Council uses Loop to plan Knowbler rollout and coach standards. Knowbler operates in Salesforce.
Jira | Ticketing for larger projects, sprint work | Stays for engineering/complex work. Loop replaces only lightweight task tracking for the council. | If council work is simple enough, Loop task lists suffice. Complex projects stay in Jira.
Confluence | Team wikis, documentation spaces | Partially replaced by Loop for council content. | Loop workspaces serve a similar function to a Confluence space but with Teams/Outlook sync. Existing Confluence content doesn't need to migrate.
Teams | Chat, meetings, channels | Stays. Loop components embed directly in Teams. | Teams is where Loop comes alive. They're complementary.
Outlook | Email, calendar | Stays. Loop components embed in emails and calendar items. | Council updates can include live-editable Loop tables right in the email body.
Excel | Analytics, reports, detailed data | Stays entirely. Loop has no analytics capability. | Your KB reporting and data pulls remain in Excel.
Lucent (your app) | Per-agent AQI tracking, coaching scheduling | Stays for operational detail. | Loop could be the council-facing summary layer. Lucent remains your granular tool.

Why map every tool explicitly?

Leadership recommendations fail when they're vague about what changes. By categorizing each tool as "stays", "moves", or "complements", you give Jessica and CC a clear picture with no ambiguity.

This also protects you from scope creep. When someone asks "should we move X to Loop?" you already have a documented answer.

Confirm your table has 10 rows (one per tool) and all four columns filled in.

Table columns not showing correctly?

If your table only shows a few columns, click on a column header and use the + icon on the right edge to add more columns. Make sure each column header matches the names above exactly.

Help me set up a table in Microsoft Loop with the right columns.

Add a "What Moves to Loop" summary

The table gives the detail. Now you need a clear, concise recommendation that anyone can read in 30 seconds.

Click below your table to position your cursor after it.
Press / and add a Heading called "What Moves to Loop."
Below the heading, type a paragraph summarizing your recommendation based on your hands-on experience in this project.

Your summary should state that the council should use Loop for:

The charter (currently homeless).
Meeting agendas and notes (currently ad hoc).
Lightweight initiative tracking (currently over-engineered in SmartSheets for this purpose).
Cross-team visibility (currently scattered across SharePoint folders).

What makes this recommendation credible?

You've now built every piece of the workspace yourself. You can speak from direct experience about what Loop does well and where it falls short. That lived experience beats any slide deck.

Document what Loop cannot do

Honest limitations are what make your recommendation trustworthy. If you only present the positives, leadership will ask the hard questions themselves. Better to answer them upfront.

Press / and add a Heading called "Loop Gaps for Our Use Case."
Below the heading, document each limitation as its own line.

Include these specific gaps:

No forms. SmartSheets keeps your coaching intake forms because Loop has no form builder.
No Salesforce integration. Knowledge base work stays in Salesforce. Loop cannot connect to it.
No analytics or reporting. Excel keeps your data work. Loop has no charting or calculation capabilities.
No external sharing. If the council ever needs to share with vendors or contractors, Loop won't work. All members must be within your organization.
No Gantt charts or automations. Complex project tracking stays in SmartSheets or Jira.

Why document limitations in the workspace itself?

By putting this directly in the Loop workspace, Jessica and other council members can see the limitations in context. They don't need to ask you "can Loop do X?" because the answer is already documented next to the recommendation.

Review your Tool Ecosystem Map page from top to bottom. You should see the filled-in table, the "What Moves to Loop" summary, and the "Loop Gaps for Our Use Case" section.

Page looking cluttered or hard to scan?

Make sure each section has its own heading. The table, the summary, and the gaps section should each be clearly separated with a heading so readers can jump to what they need.

How do I organize a Loop page with clear sections?

Your Tool Ecosystem Map is complete. You now have a clear, experience-backed recommendation ready to share with Jessica and CC. Next up, take on the Secret Mission to prototype a coaching standards system that bridges Loop, Teams, and Outlook.

Secret mission

Build a Coaching Standards Sharing System

Your council needs a way for coaches across all teams to report AQI metrics without opening yet another tool. Can you build a coaching standards page that syncs live between Loop and Outlook, so Jessica could send a monthly check-in email where each coach updates their row right in the message?

Clean Up Your Resources

This project runs entirely within Microsoft Loop, Teams, and Outlook, so there are no ongoing costs. Decide whether to keep your resources running, pause them to come back later, or delete them entirely.

Resources you used:

Knowledge Council workspace in Microsoft Loop (contains all 5 pages: Charter, Meeting Hub, Initiatives Tracker, Tool Ecosystem Map, Coaching Standards & AQI Reporting).
Council Meeting Notes workspace template saved in Loop.
Loop task list component shared in a Teams group chat (synced with Initiatives Tracker page).
Loop table component pasted into an Outlook email draft (synced with Coaching Standards & AQI Reporting page).

Keep everything running

No action needed. Choose this if you plan to share the workspace with Jessica and the council, or if you want to continue building on what you created.

Your Knowledge Council workspace stays accessible at loop.cloud.microsoft for all invited members.
The Loop components in Teams and Outlook remain live and editable by anyone in the chat or email thread.
Your workspace template remains available for future meetings.
Loop files are stored in your OneDrive/SharePoint storage and count toward your Microsoft 365 storage quota.

Pause - I'll come back to this later

There are no running processes to stop. Loop workspaces are persistent and do not consume compute resources. Your content stays where it is until you return.

Discard the Outlook email draft containing the Loop table component if you do not plan to send it. Open the draft in Outlook and click Discard.
Leave the Teams chat message with the Loop component in place. It will not generate notifications unless someone edits it.
Your workspace and all pages will be waiting for you at loop.cloud.microsoft whenever you return.

Delete - I don't want to use this again

Remove all project resources completely. Follow each step below to clean up everything you created.

Delete the Loop component message in Teams. Open the Teams group chat, find the message containing the Loop task list component, hover over it, select More options (the ... icon), then select Delete. This removes the message from the chat. The underlying .loop file remains in your OneDrive until you delete it separately.
Discard the Outlook email draft. Open the draft containing the Loop table component and click Discard to remove it.
Delete the Knowledge Council workspace. Go to loop.cloud.microsoft and select Grid view. Find the Knowledge Council workspace, click More (the ... icon on the workspace tile), then select Delete. Confirm the deletion. This removes all pages and templates inside the workspace permanently.
Clean up residual .loop files in OneDrive. Loop components sent in Teams are stored as .loop files in your OneDrive. Open OneDrive for Business, navigate to the Loop folder inside My files, and delete any .loop files related to this project.

Workspace deletion is permanent

Once you delete a Loop workspace, it cannot be restored. Make sure you have copied any content you want to keep (such as your Tool Ecosystem Map) before deleting.

Nice Work!

You did it. You've built a working Knowledge Council hub in Microsoft Loop and mapped exactly where it fits in your existing tool ecosystem.

Here's what you accomplished:

Created a shared Loop workspace with living pages for your council charter, meeting hub, and initiatives tracker that all 7 members can access and edit in real time.
Connected Loop to Teams with synced components that update across apps instantly, proving the council can collaborate without leaving their existing workflow.
Mapped your entire tool ecosystem with a clear verdict on what stays (SharePoint, SmartSheets, Salesforce, Excel, Jira, Lucent), what moves to Loop (charter, meeting notes, lightweight tracking), and what Loop cannot do.
Prototyped a coaching standards reporting system that syncs across Loop, Teams, and Outlook while respecting what SmartSheets and Lucent do better.

Ready to quiz yourself?