Teams Web Microsoft

Microsoft Teams Webhooks and connectors are a simple way to connect your web services to channels and teams inside Microsoft Teams. Outgoing webhooks allow your users to send text messages from a channel to your web services. Connectors allow users to subscribe to receive notifications and messages from your web services. Microsoft Teams video training. Intro to Microsoft Teams. Set up and customize your team. Collaborate in teams and channels. Work with posts and messages. Upload and find files. Start chats and calls. Manage meetings. Set up and attend live events. Explore apps and tools.

-->

Note

Review the following information to understand chat, teams, channels, & apps in Teams. Then, go to Chat, teams, channels, & apps in Teams to walk through a list of decisions important to your Teams rollout.

Let’s get started by thinking about how Microsoft Teams allows individual teams to self-organize and collaborate across business scenarios:

  • Teams are a collection of people, content, and tools surrounding different projects and outcomes within an organization.

    • Teams can be created to be private to only invited users.
    • Teams can also be created to be public and open and anyone within the organization can join (up to 10,000 members).

    A team is designed to bring together a group of people who work closely to get things done. Teams can be dynamic for project-based work (for example, launching a product, creating a digital war room), as well as ongoing, to reflect the internal structure of your organization (for example, departments and office locations). Conversations, files and notes across team channels are only visible to members of the team.

  • Channels are dedicated sections within a team to keep conversations organized by specific topics, projects, disciplines—-whatever works for your team! Files that you share in a channel (on the Files tab) are stored in SharePoint. To learn more, read How SharePoint Online and OneDrive for Business interact with Teams.

    • Channels are places where conversations happen and where the work actually gets done. Channels can be open to all team members or, if you need a more select audience, they can be private. Standard channels are for conversations that everyone in a team can participate in and private channels limit communication to a subset of people in a team.
    • Channels are most valuable when extended with apps that include tabs, connectors, and bots that increase their value to the members of the team. To learn more, see Apps, bots, & connectors in Teams.

For help using teams and channels, check out Teams and channels.

View this short video to learn more about best practices for creating teams and channels.

Microsoft

Membership, roles, and settings

Microsoft teams web version

Team membership

When Microsoft Teams is activated for your entire organization, designated team owners can invite any employee they work with to join their team. Microsoft Teams makes it easy for team owners to add people in the organization based on their name. Depending on your organization's settings guests who are team members but outside of your organization can also be added to your teams. See Guest Access in Microsoft Teams for more information.

Team owners can also create a team based on an existing Microsoft 365 group. Any changes made to the group will be synced with Microsoft Teams automatically. Creating a team based on an existing Microsoft 365 group not only simplifies the process of inviting and managing members, but also syncs group files inside of Microsoft Teams.

Team roles

There are two main roles in Microsoft Teams:

  • Team owner - The person who creates the team. Team owners can make any member of their team a co-owner when they invite them to the team or at any point after they’ve joined the team. Having multiple team owners lets you share the responsibilities of managing settings and membership, including invitations.
  • Team members - The people who the owners invite to join their team.

In addition, if moderation is set up, team owners and members can have moderator capabilities for a channel. Moderators can start new posts in the channel and control whether team members can reply to existing channel messages. Team owners can assign moderators within a channel. (Team owners have moderator capabilities by default.) Moderators within a channel can add or remove other moderators within that channel. For more information, see Set up and manage channel moderation in Microsoft Teams.

Team settings

Team owners can manage team-wide settings directly in Microsoft Teams. Settings include the ability to add a team picture, set permissions across team members for creating standard and private channels, adding tabs and connectors, @mentioning the entire team or channel, and the usage of GIFs, stickers, and memes.

Take three minutes to check out this go-to-guide video for team owners:

If you are a Microsoft Teams administrator in Microsoft 365 or Office 365, you have access to system-wide settings in the Microsoft Teams admin center. These settings can impact the options and defaults team owners see under team settings. For example, you can enable a default channel, “General”, for team-wide announcements, discussions, and resources, which will appear across all teams.

By default, all users have permissions to create a team within Microsoft Teams (to modify this, see Assign roles and permissions in Teams. Users of an existing Microsoft 365 group can also enhance their permissions with Teams functionality.

One key early planning activity to engage users with Microsoft Teams is to help people think and understand how Teams can enhance collaboration in their day to day lives. Talk with people and help them select business scenarios where they are currently collaborating in fragmented ways. Bring them together in a channel with the relevant tabs that will help them get their work done. One of the most powerful use cases of Teams is any cross-organizational process.

Example Teams

Teams Web Microsoft

Below are a few functional examples of how different types of users may approach setting up their teams, channels, and apps (tabs/connectors/bots). This may be useful to help kick off a conversation about Microsoft Teams with your user community. As you think about how to implement Microsoft Teams in your organization, remember that you can provide guidance on how to structure their teams; however, users have control of how they can self-organize. These are just examples to help get teams to start thinking through the possibilities.

Microsoft Teams is great for breaking down organizational silos and promoting cross-functional teams, so encourage your users to think about functional teams rather than organizational boundaries.

Types of TeamsPotential ChannelsApps (Tabs /Connectors /Bots )
SalesAnnual Sales Meeting
Quarterly Business Review
Monthly Sales Pipeline Review
Sales Playbook
Power BI
Trello
CRM
Summarize Bot
Public RelationsPress Releases
News and Updates
Fact Checking
RSS Feed
Twitter
Event PlanningMarketing
Logistics and Scheduling
Venue
Budget
Twitter
Facebook
Planner
PDF
Marketing/Go to MarketMarket Research
Messaging Pillars
Communications Plan
Marketing Bill of Materials
YouTube
Microsoft Stream
Twitter
MailChimp
Technical OperationsIncident Management
Sprint Planning
Work Items
Infrastructure and Operations
Team Services
Jira
AzureBot
Product TeamStrategy
Marketing
Sales
Operations
Insights
Services & Support
Power BI
Team Services
FinanceCurrent Fiscal
FY Planning
Forecasting
Accounts Receivable
Accounts Payable
Power BI
Google Analytics
LogisticsWarehouse Operations
Vehicle Maintenance
Driver Rosters
Weather Service
Travel / Road Disruptions
Planner
Tubot
UPS Bot
HRTalent Management
Recruiting
Performance Review Planning
Morale
HR Tools
External Job Posting Sites
Growbot
Cross-organizational
Virtual Team
Strategy
Workforce Development
Compete & Research
Power BI
Microsoft Stream

It's possible to create Teams that align with the organizational structure. This is best used for leaders who want to drive morale, have team-specific reviews, clarify employee onboarding processes, discuss workforce plans, and increase visibility across a diverse workforce.

Org-wide teams

If your organization has no more than 5,000 users, you can create an org-wide team. Org-wide teams provide an automatic way for everyone in an organization to be a part of a single team for collaboration. For more information, including best practices for creating and managing an org-wide team, see Create an org-wide team in Microsoft Teams.

-->

You can make web apps suitable with Teams' social and collaborative features, by properly integrating them with Teams.

The different types of apps which you can integrate with Teams are as follows:

  • Standalone apps: A stand alone app is a single-page or large, and complex app. The user can use some aspects of it in Teams.
  • Collaboration apps: An app already built for the social and collaborative features inherent to Teams.
  • SharePoint: A SharePoint page you want to surface in Teams.

You can map and follow the appropriate guideline applicable to your integration scenario.This document gives an overview of Teams capabilities, share-point requirements for file and data storage, API requirements, authentication and deep-linking of your app with Teams.

Get to know Teams platform capabilities

Integration scenarios: Standalone apps, collaboration apps, SharePoint

Your Teams app must include required and expected collaborative features. To work with app integration, it is important to familiarize with Teams development terminology.

Common app featuresTeams platform capabilities
Embedded webpage, homepage, or webviewTabs
Share shortcuts and extensionsMessaging extensions
Action shortcuts and extensionsMessaging extensions
ChatbotsBots
Channel notificationsBots
Incoming webhooks
Office 365 Connectors
Message external servicesBots
Outgoing webhooks
ModalsTask modules
Content-rich cardsAdaptive Cards

Determine a subset of functionality

Integration scenarios: Standalone apps

Integrating all features of an existing application into Teams often leads to a forced or unnatural user experience, particularly in larger apps. Start with the most impactful features and those that integrates more naturally with Teams. You can allow users to launch the main app and access its full set of features.

Prerequisites to integrate your app with TeamsFollowing are the prerequisites to integrate your app with Teams.

  1. Map your app's use cases to Teams platform capabilities.
  2. Determine your app's entry points. Is it for personal use, collaboration, or both?

Understand SharePoint requirements and options

Integration scenarios: SharePoint

To integrate an existing SharePoint page as a Teams tab, you must consider the following:

  • It must be a modern SharePoint online page.
  • Only personal tabs are supported. You cannot integrate your page as a channel tab.

Alternatively, you can build a Teams tab using the SharePoint Framework.

Aim towards multi-tenancy

Integration scenarios: Standalone apps, collaboration apps, SharePoint

If your app is used by multiple organizations, consider multi-tenant hosting that makes your product scalable and greatly simplify the distribution.

Review your APIs

Integration scenarios: Standalone apps, collaboration apps

Register for teams meeting

You must make your app's existing APIs and data structures support the app when integrating with Teams. To extend the support, you must augment the APIs and data structures with contextual information about Teams for identity mapping, deep-link support, and incorporating Microsoft Graph.

Learn more about getting context for your Teams tab or bot.

Understand authentication options

Integration scenarios: Standalone apps, collaboration apps, SharePoint

Azure Active Directory (AD) is the identity provider for Teams. If your app uses a different identity provider, you must either do an identity mapping exercise or combine with Azure AD.

Teams has single sign-on (SSO) mechanisms with Azure AD for third-party apps. It also provides the guidance for authentication flows to other identity providers using standards such as OAuth and Open ID Connect, known as OIDC.

For SharePoint pages, you can only use SSO and cannot add another Azure AD ID if you want SSO to work for another app as the ID is the SharePoint app.

Learn more about authentication in Teams.

Follow Teams design guidelines

Integration scenarios: Standalone apps, collaboration apps

Web browser microsoft teams

Ensure to follow Teams design guidelines to make your app native to Teams. You cannot migrate an existing app content to a Teams tab. For more information on app design, see Fluent Design System.

Maximize deep linking

Integration scenarios: Standalone apps, collaboration apps, SharePoint

Start Microsoft Teams Web App

You can create links to information and features within Teams. Use deep links to link your app with Teams as they tie together multiple pieces of an app for a more native Teams experience.

Be smart when messaging users

Integration scenarios: Standalone apps, collaboration apps, SharePoint

Chrome Microsoft Teams Web

Use a bot in your Teams app for multi-threaded conversation, as it offers more flexibility than a webhook.

Bots also allow you to send proactive messages to individual users or channels. The proactive messages are unprompted messages triggered by an outside event and not a message sent to a bot. For example, your bot sends a welcome message when it is installed or a new user joins a channel.

Microsoft Teams Web Version Login

Teams

Sending proactive messages requires Teams-specific identifiers. You can capture the information by fetching roster or user profile data, subscribing to conversation events, or using Microsoft Graph.

Do not spam users with excessive messages. If the Teams capability supports it, the users can configure notification settings for your app.
Following is an example of a notification message:Don't send me unprompted messages.

Use SharePoint for file and data storage

Integration scenarios: Standalone apps, collaboration apps, SharePoint pages

Microsoft Teams Web Sign In

When a team is created, a SharePoint site collection is also provisioned to support file and data storage for that team. Your app must leverage this feature if it interacts with files. Use the site collection to store raw data in SharePoint Lists and Excel.

Register For Teams Meeting

See also