Moderating Teams Channels

-

Working with Moderated Channels in Teams:

Beside of the upcoming Private Channels, in Teams you can control channel and messaging/ collaboration in multiple ways.

The optimal control what a channel shall be for, is found under Managing Channel. You want to be able in the sense of Teams Adoption controlling (other words: optimizing) collaboration. 

A channel can have multiple functions:
  •  Information Channel
  •  Information Channel with dedicated feedback
  •  Moderated Channel
  •  Controlling behavior of Guest
  •  BOT or CONNECTOR controlled
Those options provide us with a greater flexibility in optimization of Teams Usage.
It will drive best user experience and archive an optimal approach for Business Processes and Information Flow within a Collaboration Platform.

First you have to create a channel within the Team:



After its creation, select the Manage channel option.


The configuration windows start with controlling Guest behavior. You can restrict Guest from starting proactively a conversation.


Next, if you turn "Channel Moderation" ON:
  •  Teams Owner are activated posting in this channel, while members can reply and  bot/ connector can submit messages.
If you turn of Team member permission:
  •  Team members are only observer (information channel)
  •  control BOTs and Connector if messaging is possible/ or not


If you hover of the "Teams owners" a popup shows you who are the automatically added Teams owner.


Managing Moderator is limited on the list of Teams members/ owner:


It is possible nominating Guest as moderator too. 

Example:

If a you have a Project Management Team, where the PM is external (Guest), this is one option where it makes sense.


If a user isn't part of the members of a team, search will not bring up any results and the user can't be added. You would have first making this user part of the members.



Advice for User Adoption:

In the following examples, will hopefully give you ideas on how to use moderated channels and help you driving optimized collaboration, reducing other "outside" Teams workloads, like SharePoint, or Yammer.

Information Channel:

At channel level, where you like to publish information only, you should define a moderator and restrict postings. You can enable Replys on those messages, depending on who and what those information are for.

Functional Channel: (e.g. TABs)

You might have written BOTs, specialized TABs or other functional events. In this case the might be no collaboration based on messaging necessary. At those circumstances, you can leave the chat section "closed", focusing on the other features you have deployed within the channel.

Moderated Channel: (Compliance Control)

If you, e.g. have a management board channel, you want to control this channel and ensure compliance or behavioral policies. In those cases a moderated channel might help.

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, uniqu...
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more