M365 Copilot

Brief

Right now, the Microsoft 365 Copilot app uses too many overlapping concepts: Copilot Chats, Conversations, Pages, Notebooks, Instructions, References, and Library. On top of that, the Loop app has its own concepts: Workspaces and Ideas (Pages). Together, these make it hard for users to build a clear mental model of where things live and how they relate.

From a user perspective, it would be much simpler if everything were centered around Loop.

๐Ÿญ. ๐— ๐—ฎ๐—ธ๐—ฒ โ€œ๐—Ÿ๐—ผ๐—ผ๐—ฝ ๐—ฃ๐—ฟ๐—ผ๐—ท๐—ฒ๐—ฐ๐˜๐˜€โ€ ๐˜๐—ต๐—ฒ ๐—–๐—ผ๐—ฟ๐—ฒ ๐—–๐—ผ๐—ป๐—ฐ๐—ฒ๐—ฝ๐˜

Rename Workspaces to Projects inside the Loop app (to match how ChatGPT uses Projects and how people naturally think about work).

Use Loop Projects instead of having both Copilot Notebooks in the Microsoft 365 Copilot app and Loop Workspaces in the Loop app as separate ideas.

๐Ÿฎ. ๐—ฅ๐—ฒ๐—ป๐—ฎ๐—บ๐—ฒ ๐—œ๐—ฑ๐—ฒ๐—ฎ๐˜€ ๐˜๐—ผ ๐—ฃ๐—ฎ๐—ด๐—ฒ๐˜€ ๐—œ๐—ป๐˜€๐—ถ๐—ฑ๐—ฒ ๐—Ÿ๐—ผ๐—ผ๐—ฝ

Ideas are essentially Pages. Rename Ideas to Pages inside the Loop app so the terminology matches the Microsoft 365 Copilot app.

This gives users one clear conceptโ€”Pagesโ€”instead of two near-duplicate terms.

๐Ÿฏ. ๐— ๐—ฎ๐—ธ๐—ฒ ๐—œ๐—ป๐˜€๐˜๐—ฟ๐˜‚๐—ฐ๐˜๐—ถ๐—ผ๐—ป๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—Ÿ๐—ถ๐—ฏ๐—ฟ๐—ฎ๐—ฟ๐˜† ๐—ฅ๐—ฒ๐˜‚๐˜€๐—ฎ๐—ฏ๐—น๐—ฒ ๐—˜๐˜ƒ๐—ฒ๐—ฟ๐˜†๐˜„๐—ต๐—ฒ๐—ฟ๐—ฒ

Allow Instructions to be saved into Library once and reused across Loop Projects, Pages, and Chats.

Clearly surface Library as the place to manage reusable prompts and instructions (a single home for โ€œhow I want Copilot to behaveโ€).

๐Ÿฐ. ๐—Ÿ๐—ฒ๐˜ ๐—–๐—ต๐—ฎ๐˜๐˜€ ๐—Ÿ๐—ถ๐˜ƒ๐—ฒ ๐—œ๐—ป๐˜€๐—ถ๐—ฑ๐—ฒ ๐—Ÿ๐—ผ๐—ผ๐—ฝ ๐—ฃ๐—ฟ๐—ผ๐—ท๐—ฒ๐—ฐ๐˜๐˜€

Make it possible to attach Copilot Chats to Loop Projects/Workspaces, similar to how Instructions, photos, and videos can be attached from Library.

This way, each Project can contain its relevant chats alongside its pages and content, instead of chats feeling like a separate, detached surface.

๐Ÿฑ. ๐—ฆ๐—ถ๐—บ๐—ฝ๐—น๐—ถ๐—ณ๐˜† โ€œ๐—ฅ๐—ฒ๐—ณ๐—ฒ๐—ฟ๐—ฒ๐—ป๐—ฐ๐—ฒ๐˜€โ€ ๐—ถ๐—ป ๐—–๐—ผ๐—ฝ๐—ถ๐—น๐—ผ๐˜ ๐—ก๐—ผ๐˜๐—ฒ๐—ฏ๐—ผ๐—ผ๐—ธ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—Ÿ๐—ผ๐—ผ๐—ฝ ๐—ฃ๐—ฟ๐—ผ๐—ท๐—ฒ๐—ฐ๐˜๐˜€

Instead of exposing References as yet another separate construct:

Either make References a component inside Loop (for example, a โ€œReferencesโ€ block on a page), or

Let me attach a OneDrive folder as the Projectโ€™s References, and have Copilot automatically treat everything inside that scope as references.

๐˜›๐˜ฉ๐˜ช๐˜ด ๐˜ฌ๐˜ฆ๐˜ฆ๐˜ฑ๐˜ด ๐˜ต๐˜ฉ๐˜ฆ ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต๐˜ข๐˜ญ ๐˜ฎ๐˜ฐ๐˜ฅ๐˜ฆ๐˜ญ ๐˜ด๐˜ช๐˜ฎ๐˜ฑ๐˜ญ๐˜ฆ: ๐˜ฆ๐˜ข๐˜ค๐˜ฉ ๐˜“๐˜ฐ๐˜ฐ๐˜ฑ ๐˜—๐˜ณ๐˜ฐ๐˜ซ๐˜ฆ๐˜ค๐˜ต ๐˜ค๐˜ฐ๐˜ฏ๐˜ต๐˜ข๐˜ช๐˜ฏ๐˜ด ๐˜—๐˜ข๐˜จ๐˜ฆ๐˜ด, ๐˜Š๐˜ฉ๐˜ข๐˜ต๐˜ด, ๐˜๐˜ฏ๐˜ด๐˜ต๐˜ณ๐˜ถ๐˜ค๐˜ต๐˜ช๐˜ฐ๐˜ฏ๐˜ด, ๐˜ข๐˜ฏ๐˜ฅ ๐˜™๐˜ฆ๐˜ง๐˜ฆ๐˜ณ๐˜ฆ๐˜ฏ๐˜ค๐˜ฆ๐˜ด.

๐—ง๐—ต๐—ถ๐˜€ ๐—ฐ๐—ผ๐˜‚๐—น๐—ฑ ๐—ฎ๐—น๐˜€๐—ผ ๐—ฎ๐˜ƒ๐—ผ๐—ถ๐—ฑ ๐˜๐—ต๐—ฒ ๐—ฐ๐—ผ๐—ป๐—ณ๐˜‚๐˜€๐—ถ๐—ผ๐—ป ๐—ฏ๐—ฒ๐˜๐˜„๐—ฒ๐—ฒ๐—ป ๐—–๐—ผ๐—ฝ๐—ถ๐—น๐—ผ๐˜ ๐—ก๐—ผ๐˜๐—ฒ๐—ฏ๐—ผ๐—ผ๐—ธ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—ข๐—ป๐—ฒ๐—ก๐—ผ๐˜๐—ฒ ๐—ก๐—ผ๐˜๐—ฒ๐—ฏ๐—ผ๐—ผ๐—ธ๐˜€.