MS Teams :: Live components / Loop Component

-

  • Live components in Teams chat offer a new way to ideate, create, and make decisions together.

  • Send a component—like a table, task list, or paragraph—where everyone in your chat can edit inline and see changes as they’re made. 

  • This means you can gather ideas and feedback from your team while holding fewer meetings and minimizing the need for long chat threads.

  • Live components are designed for collaboration, the components are always shared as editable by others, even if your tenant is set to default to view-only for other file types.

Features:

  • Get tasks done faster together. Crowd-source an agenda, track a group's action items, or take notes collectively. These are just a few scenarios made easier with live components.

  • Share components. In this release, you can share live components into different Teams chats. Recipients can edit from wherever they are and see updates instantly no matter where the changes were made. In future releases, live components will be supported in Teams meeting notes and channels, Outlook, and eventually across all Microsoft 365 applications.

  • Start in chat, build from there. Every component you create from Teams chat is automatically saved to a file in OneDrive. So, you might begin collaborating in chat then later move to the file, where you have a larger visual space for editing and can add as many components as you like.

Settings management

  • Live components are built with Microsoft Fluid Framework supported across Microsoft 365 suite and controlled from SharePoint Online.

  • SharePoint Online PowerShell module to enable or disable all Fluid Experiences across your Office 365 tenant. Microsoft Fluid Framework defaults to ON for all targeted release tenants.

Storage of .fluid files:

How .fluid are stored?

  • Live components created in Teams are backed by a .fluid file stored in the creator’s OneDrive for Business.

  • Being a file in OneDrive for Business means that users can create, discover, and manage live components (.fluid files) as easily as any Office document.

  • Users can search for content in .fluid files from Office.com and OneDrive for Business. .fluid files work with data governance features like eDiscovery, auditing, reporting, and legal hold.

  • .fluid files will now appear on Office.com and OneDrive for Business, such as in the Recent and Recommended areas. .fluid files can be restored to previous versions from OneDrive for Business.

  • Chat participants must have a OneDrive account to create live components. Without a valid OneDrive account, chat participants might still be able to collaborate on a component created by other users who have a valid OneDrive account, but cannot create their own.

  • Moving a .fluid file from OneDrive to a SharePoint site will result in the live component failing to load in Teams chat.

What happens if the owner of the file leaves the company?

How are .fluid files shared?

  • Live components can be inserted in Teams chat or copied from one chat to another. (Live components aren't yet supported in channels.) They default to the tenant’s existing permissions, but users can change permissions before sending to ensure everyone has access.
  • Opening components from Teams chat in Office.com offers share functionality at the top of the window, similar to the sharing options offered for other Office documents.

What if a .fluid file becomes corrupted or damaged?

  • Version History allows you to review and copy from previous versions of the file.

What apps can open and edit .fluid files?

  • .fluid files can only be opened as links in your browser, such as Office.com, and as live components in Teams chat. If downloaded, they can't be opened again without first uploading them back to OneDrive for Business or SharePoint Online.

Note:

Live components is the first feature of the Microsoft Loop app to become available in Teams.

Please note that "Live components" will be renamed "Loop components" in early 2022

Send a live component

  1. Go to the box where you type a chat message. Select Insert live components   right beneath the box. (Make sure the box is empty—with no text in it—when you do this.)

     2.  Select the type of component you want to insert into your message



  1. Enter content into the component.

  2. When ready, select Send . Everyone in the chat will be able to edit the content inline.

Tip: @Mention people inside the component to show where you’d like them to contribute. They’ll get an activity feed notification that brings them right to the component.

Edit a live component

Simply click where you want to add or edit content and start typing.

When editing, you can type / to insert things like an @mention, date, or even a component. If you want to comment on existing text vs edit it, type //. This will attribute the comment to you.

Tip: Pin the message containing your live component, which puts it at the top of your chat for easy access. To do so, Select More options  Microsoft Teams more options icon  >Pin.

View activity and access

If others are editing while you’re viewing the component, you’ll see different colored cursors within the text and you’ll possibly see text being edited as well.

Avatars appear in the upper right corner to let you know who is viewing, editing, or has recently edited the component. Hover your cursor over any avatar for details.

Select See who has access    to understand who can view or edit the component. Avatars of people who have viewed the component at least once appear here, too.

Share a live component in another chat

  1. Go to the upper right corner of the component and select Copy link .
  2. Switch to a different chat.
  3. Go to the box where you type a message and press Ctrl + V to paste your live component into an empty chat.

The people in your original chat and in this additional chat will be able to edit the content. No matter where people are editing, the component will always show the latest updates.

View and edit the file on Office.com

Live components are automatically saved to OneDrive once sent in chat. Here’s how to navigate from chat to the file on Office.com:

1. Select the linked filename at the top your live component.



2. The file will open on Office.com, where you can view and co-edit the content.

Known issues

·    Live components in chat cannot be edited via Office app when using Teams on Android.

·     If tenant default file permissions are set to Specific people (only the people the user specifies), and the sender removes some users from the Specific people list in the permissions dialog when creating a component, those users may still have access to the content. This issue is due to the access management limitation of the permission dialog and will be fixed in the future release.

·         If the tenant's Conditional Access Policy settings prevent client network to connect to https://pushchannel.1drv.ms, live components will not work as expected for saving real time changes to the service.

Known limitations

·Searching for live components in Teams search will return a link to the component in office.com, not the chat message itself.

·         Live components are disabled in federated chats.

·         B2B guests will not be able to collaborate on live component that is shared with them via Company Share Link unless tenant sets external access option to allow B2B guests have same access level as tenant members.

·         Teams Web client full support of Live components will be available soon.

·         Live components are not supported in Teams channels yet, but their inline editing in channels is planned for more experiences in the future.

·        With tenant default file permissions set to Specific people (only the people the user specifies), copying link to live component and pasting in another chat requires the sender to use permissions dialog and add the recipients in the Specific people option to grant access properly.

·         With tenant default file permissions set to Specific people (only the people the user specifies), creating a live component in group chat with more than 20 members will require the sender to manually select the permission options for the component.

·        Live components in chat will not load only if file was moved to different library. If file is moved to different folder then it will continue to load in chat.

 

Comments

Post a Comment

Popular posts from this blog

Is it CDS, Microsoft Dataflex, Dataverse..?

-
Image
Common Data Service (CDS) — the data storage system that intensifies Dynamics 365 and Power Platform — has changed its name to  Dataverse,   Dataverse does the same thing as CDS — but with a  different name .  Dataverse branding is identical to CDS OR The Dataverse brand is a reworking of the earlier  "Microsoft Dataflex" and "Microsoft Dataflex Pro"  products,     You’ll still be able to store and manage data used by business apps in Dataverse, just like you did in Common Data Service. What Else You Need to Know About Microsoft Dataverse   Benefits of Microsoft Dataverse   Why the change…?   ·         Microsoft wants to make Power Apps and Power Virtual Agents  the core of application development for Microsoft Teams .   ·         And this brings us to  Dataverse for Teams , a spin-off from Dataverse that securely stores and manages  spec...
Read more

SharePoint Sites, Group sites, and Teams Sites: What’s the Difference?

-
SharePoint Sites:   A SharePoint Team Site functions as a hub where many team members can access content, organize content, or collaborate on content. Communication within SharePoint Team Sites is done with commenting on documents in real time, alongside all other team members. Group Sites:   ·         In Office 365, Group Sites compliment a traditional email/Outlook group. Secure but slightly limited in functionality, Group Sites allow for solid and safe file collaboration among groups, the membership and permissions for which can be easily adjusted and managed on a case-by-case basis. ·         Group Sites by default are created whenever an Office 365 group is created, so it is important to establish policies for who is able to create Office 365 groups. ·         Group Sites typically should not house very confidential or sensitive material, as IT and securi...
Read more