In this Article
Use Case 1: Improving Collaboration and Productivity within an Organization using Microsoft Teams
Problem
Organization X is facing productivity issues compounded due to the lack of coordination and collaboration between some of its teams. It is in search of an efficient and scalable solution that can:
- Enormously improve interaction within these teams.
- Work with zero-to-minimal learning curve for adaptation.
Solution
Using the Teams Snap Pack, we can build such a solution that automates the management of communication, and hence paves the way to effective collaboration, within and across the teams in the Organization X. This Pipeline demonstrates how we can achieve this.
Understanding the solution
First, let us understand what this Pipeline attempts to do and why.
- Constructed using the Snaps in the Teams Snap Pack, this Pipeline leverages a subset of Microsoft Teams' (hereinafter referred to as 'Teams') capabilities to configure the Teams framework for the organization.
- This framework allows each staff member to communicate through multiple mediums such as chat, audio, video, file/document shares, and so on within and across the various teams/departments in the organization.
By doing so, the organization can enable its entire staff to interact, coordinate, and effectively collaborate and achieve the individual, team, as well as the company's goals for productivity.
Using other Microsoft Products
We can integrate Microsoft Teams, and hence the Teams Snap Pack, with other Microsoft products and services such as Microsoft 365 (Word, PowerPoint, Excel, Outlook), OneDrive, SharePoint Online, Power BI, and Exchange Online seamlessly, if the Organization X uses any of these Microsoft's offerings. SnapLogic has the respective premium Snap Packs that we can leverage for such needs.
Now, let us understand how this Pipeline is constructed.
- The Pipeline begins with creating a new team (preferably one for each department) and then adds the corresponding members to this team.
- Each team contains a 'General' channel by default, which is accessible to all the team members.
- Each team can have one or more owners.
- Once added to the team, team members, based on their permissions, can create topic-based sub-teams (channels) for more localized collaboration towards their goals. These channels can be public (visible to all team members) or private (visible to limited members).
Part 1: Create Teams, Channels and add Members
The first part of the solution Pipeline covers the following activities in the Teams instance.
- Create a public team (Create Team Snap): Any member in the organization can locate and join this team.
- Map the team name and add members to the team (Mapper and Team Operations Snaps)
- Create a channel within the team (Create Channel Snap)
- Map the channel name and add members to the channel (Mapper and Channel Operations Snaps).
| Create Team | Add Team Members |
|---|---|
|
|
| Create Channel | Add Channel Members |
|  |
Part 2: Review Configuration and Start Sending Channel Messages
After configuring the team and the channels, we can now review them and make changes to the team (Team Operations Snap) or channels (Channel Operations Snap), as required. In this use case, we list out the channel members and remove some members who need not be a part of this channel anymore. Later, we send a message to the channel.
| List Channel Members |
|---|
|
| View Output Preview |
 |
To send messages to a channel on behalf of the channel owner or a participant, we can draft the required message using the Send Channel Message Snap. See the required Snap settings below.
| Sending a Message in Channel |
|---|
|
| Message Output Preview |
 |
Conclusion
Using the Teams Snap Pack, we can get the required set of employees onboard (to use Teams), add them into relevant teams and channels. By doing this, we are allowing the users to streamline their interactions and encourage meaningful collaborations that can transform into great ideas well executed for the customers.
Downloads
