Teams Channel Feed¶
The Channel Feed web part allows user's to display activity in a Microsoft Teams Channel.
Features¶
Most channel activity is surfaced in the web part, including users joining/leaving a channel, members being added/removed from the Team, and calls happening within the channel
Messages marked as Important are highlighted in the same way as they are done in Teams.
Messages from the current user are highlighted in the same way as in Teams, with a theme-coloured border on the left side of the message.
Configuration¶
The following configuration options are available
| Setting | Description |
|---|---|
| Select Channel | Use this to select the Channel for which to show the feed |
| Show Header | Optionally show or hide a header that displays the Team & Channel name |
| Collapse all replies | Optionally hide all or show all replies to a channel message on first load. Users can still expand each thread |
| Number of Channel Messages to show | Set the number of messages to display. The most recent activity is always show, this limits the number that are displayed |
| Sort Messages By | Use this to show newest at the top of the feed, or oldest at the top |
| Height | Use this to fix the height of the web part to a static height. If set to 0, the web part height grows dynamically based on the number of items displayed |
API Permissions¶
This feature is new to Mercury Web Parts version 1.26.0.0. An Administrator must grant additional Permissions in the SharePoint Admin Center (under API Access) in order for this feature to work. If the permissions have not been granted, this will be met with an error.
Admins will need to grant the three following permission scopes:
- Team.ReadBasic.All
- Channel.ReadBasic.All
- ChannelMessage.Read.All
Content Visibility¶
The user must be a member of the selected Team in order to show content from the channel. If they are not a member they will receive a warning about permissions and the feed will not show.
It is therefore recommended that for widespread use (such as on an Intranet Homepage) to use this web part with a Org-Wide team channel.
For Team Sites (connected to Teams), where site access is controlled by the Team membership, this web part is a great way to summarise activity in a Channel for that Team.
Config Repository¶
This web part supports use of the config repository, to allow users to save and load configurations of web parts with ease.
Loading a config file will populate the web part properties with properties from the incoming file.
SharePoint¶
Saving to SharePoint allows collaboration between users in a tenant.
The path the file is saved to is tenant-name/Site Assets/Mercury Assets/webpart-name.json.
Permissions¶
To save a file to SharePoint, edit permissions are required on the root Site Assets library.
To load a file from SharePoint, read permissions are required on the root Site Assets library.
OneDrive¶
Saving to OneDrive allows a user to save a file locally, this is the best option when a user does not have the required permissions to save to SharePoint.
The path the file is saved to is Mercury Assets/webpartname.json.