@jeffteper@Workday@MicrosoftTeams Hi Jeff, please check this https://t.co/OfBavhmcgW
Shared channel loses its potential in terms of productivity and collaboration if can't be shared with any organization, having or not a MS Org
@MicrosoftTeams Hi, not everyone is allowed. Shared channels are more restrictive than private channels, external sharing is only allowed to MS Orgs after B2B connect setup. This is a huge step back. Please review this
https://t.co/sxbqXc49eJ
https://t.co/4jT0fCugxp
https://t.co/lbERnmC7nj
@MicrosoftTeams Hi, not everyone is allowed. Shared channels are more restrictive than private channels, external sharing is only allowed to MS Orgs after B2B connect setup. This is a huge step back. Please review this
https://t.co/sxbqXc49eJ
https://t.co/4jT0fCugxp
https://t.co/lbERnmC7nj
@MicrosoftTeams Tried this https://t.co/t3IdYnUDz2 in a private channel but does not work 😭😭😭 Why it's not possible? Is on private channels where most of the job gets done😞
@MSPowerApps Already exists https://t.co/VzP9jcSpf4 It seem easy, The app just should run under a kind of service account with permissions over the list or any connector
@MSPowerApps Allow user impersonation. List security, or hide it, are not enough for serious app requeriments. If user share the app url pointing to an item, eventually unwanted access could happen....