Hi All, After rewatching the video myself, I know there's even more to talk about permissions. Best practices and more, I'll be sure to make a part 2! Feel free to leave any questions that you want addressed in part 2! Thanks for watching!
One aspect of this that I've seen cause a LOT of problems is that Microsoft Teams expects "members" of the team to have Edit access to the site and the Documents library within it. If you change that, then some features and functions in the MS Teams app will break. For example, if you change the permission from Edit to Read, they will get an error message when trying to attach files to posts in a channel (because they don't have access to upload files to the Documents library). Even if you change it to Contribute, they won't be able to do things like add Lists to Teams (at least, not new lists) because being able to create a list in the site requires Edit permission. In my Teams (and SharePoint) workshops, I pretty much just tell people to NOT mess with the default permissions in a team-connected site without first consulting with the SharePoint support team in our organization.
This is so true, thanks for explaining this Chad. In a Group or Teams site, don't touch. Without that it would be Ok. Thanks for explaining I hope others are able to read your comment too, this is such a big tip!
Thanks John! Way too kind, I was already judging myself where I could of worded things better 😆 but it's really hard without making an hour long video! Thanks though hopefully the video helps a few, and I think it took me 3 years and couple clicks. Hahahah
This just made things more confusing, because: 1) You created a SharePoint site using admin-level access which most of us don't have, so why put that in?; and 2), you were switching between sites, (and Teams) so fast that it was difficult to be clear which site we were looking at. That made it necessary to watch several times.
In all of the companies I have worked for we do not allow users to create SharePoint sites, only admin. I guess I should recommend that. It's very difficult to govern sites if they are created in the wild west and you end up with no site naming structure, sites inside sites, a big mess and no governance at all. My bad for going too fast I'm working on slowing it down. Thanks for watching.
@@andrewhess123 That's really interesting to know. Where I work (a public institution of higher education with some 7000 employees) we create our own sites. And, yes, there is no naming structure, and that can be confusing, and people are making all kinds of mistakes with permissions. So thanks for all the videos--I'm using them to help out our situation, (though I'm not part of IT--just faculty).
Hi All, After rewatching the video myself, I know there's even more to talk about permissions. Best practices and more, I'll be sure to make a part 2! Feel free to leave any questions that you want addressed in part 2! Thanks for watching!
One aspect of this that I've seen cause a LOT of problems is that Microsoft Teams expects "members" of the team to have Edit access to the site and the Documents library within it. If you change that, then some features and functions in the MS Teams app will break. For example, if you change the permission from Edit to Read, they will get an error message when trying to attach files to posts in a channel (because they don't have access to upload files to the Documents library). Even if you change it to Contribute, they won't be able to do things like add Lists to Teams (at least, not new lists) because being able to create a list in the site requires Edit permission. In my Teams (and SharePoint) workshops, I pretty much just tell people to NOT mess with the default permissions in a team-connected site without first consulting with the SharePoint support team in our organization.
This is so true, thanks for explaining this Chad. In a Group or Teams site, don't touch. Without that it would be Ok. Thanks for explaining I hope others are able to read your comment too, this is such a big tip!
Thanks for watching and your support and insight as always!
Thank you, I have seen many videos where they don’t even cover the permissions regarding that Microsoft Teams connection. Great explanation.
Thanks Squaregg!!
Great video Andrew best explaination out there so far, unfortunately took me about 2 years for that click moment , it’s all very confusing
Thanks John! Way too kind, I was already judging myself where I could of worded things better 😆 but it's really hard without making an hour long video! Thanks though hopefully the video helps a few, and I think it took me 3 years and couple clicks. Hahahah
thank you so much, this was so helpful, please upload more videos about the sharepoint.
Thanks Fatma, there's so much more this was very basic. Glad it was helpful!
Keep it up!!
Thanks for the support Stephen!
This just made things more confusing, because: 1) You created a SharePoint site using admin-level access which most of us don't have, so why put that in?; and 2), you were switching between sites, (and Teams) so fast that it was difficult to be clear which site we were looking at. That made it necessary to watch several times.
In all of the companies I have worked for we do not allow users to create SharePoint sites, only admin. I guess I should recommend that. It's very difficult to govern sites if they are created in the wild west and you end up with no site naming structure, sites inside sites, a big mess and no governance at all. My bad for going too fast I'm working on slowing it down. Thanks for watching.
@@andrewhess123 That's really interesting to know. Where I work (a public institution of higher education with some 7000 employees) we create our own sites. And, yes, there is no naming structure, and that can be confusing, and people are making all kinds of mistakes with permissions. So thanks for all the videos--I'm using them to help out our situation, (though I'm not part of IT--just faculty).
@@guizot2010 I need to remake a permissions one 🤣 I know I could do a better video on it.