Allow 'Guests' to have the same amount of functionality as a regular Member.
Allow 'Guests' to have the same amount of functionality as a regular Member. Or as much as possible while still keeping things secure.
When a Guest is added to the Team, often times they are at the same level of team membership / importance / contributor as actually internal Members and it makes no sense business wise to limit their functionality - arbitrarily - just because they are not part of our tenant.
Lee Kowalinski
shared this idea
8 comments
-
Hannah-Jane
commented
There should be some flexibility to define what a Guest can or cannot do, for example:
- Be made a Team "Owner"
- View Meeting Notes (this one drives me mad) -
Kate Hardy
commented
I would like to have controllable options that allow Guest access - "Guest can start chats with others in the Team", "Guest can collaborate on docs", etc. Would be ideal to have users start with a low level of access and allow either Team owner or admin to dial up the access.
-
Anonymous
commented
I wholeheartedly share this sentiment and desire for change - is Microsoft working on this???
While the Guest account may be a useful feature, the Team owner should be able to decide who is a Guest and who is a full Member: it should not be enforced with the tenancy. Surely the whole point of Teams is to allow distributed Teams to work together? I don't even know what my Guests can and can't do and it is very frustrating when something works for me and my colleagues in the same organisation, but there is no way to know if it will work for Guests, who are just as much "full" Members.
-
Anonymous
commented
I can understand there may be security issue, but, working in a university setting, I often have partners from other institutions whom I fully trust, and it is frustrating that they have to feel like 'second-tier' users because I cannot make external accounts 'full members' on my team. They cannot start tabs, cannot start private channels etc., and it's unfair when in a university setting we put so much emphasis on inclusivity.
-
Jacqueline Edge
commented
While the Guest account may be a useful feature, the Team owner should be able to decide who is a Guest and who is a full Member: it should not be enforced with the tenancy. Surely the whole point of Teams is to allow distributed Teams to work together? I don't even know what my Guests can and can't do and it is very frustrating when something works for me and my colleagues in the same organisation, but there is no way to know if it will work for Guests, who are just as much "full" Members.
-
Nadia Pelham-Lacey
commented
Allowing the option to enable / limit guest capabilities would be nice including allow guests to edit / open PPT/Docs the same way a normal use can. I work closely with partners we're constantly running into issues where guests cannot edit PPTs via the desktop application and don't prefer to use the online version. We then run into issues collaborating in real-time using this platform as it becomes more of a repository rather than a collaboration space.
-
Ian Caldwell
commented
Or, at least some very clear explanations of why - so that our company users can understand the security, control, management or cost issues behind why some basic features - like adding tabs to a channel - are not available to guests
-
Clive Hornsby
commented
I am having the same issue.
As a Global Admin in 6 different organisations. I am restricted when added as a Guest from another Tenant using my primary login.