26
Newly created teams should not have access to All spaces
planned
Marco Porracin Dieguez
When adding a new team there should be an more simple way to select which spaces you want to apply that team to. Or at least let me chose "None" or "All" cause its a pain if you have X spaces and want to apply the new team to only 1 space you would need to go to the config of every other space and remove the new team from it.
Activity
Newest
Oldest
Maria Isabel Restrepo
Can we please get un update from Gitbook team. This was planned 2 years ago. It seems like bug fix more than a feature and given that it has security implications it would be nice if it is given higher priority. Thank you for all your amazing work
M
Michael Ferullo
This is HUGE. I'm actually astonished this is the default action. I created a new team not realizing this is what happened. I added a user to the team and after he sent me a screenshot of EVERY SINGLE SPACE that he had access to (including spaces with confidential information), I realized that I had go to through every single space and remove access.
Maria Isabel Restrepo
Hi. I am wondering the status of this plan. This issue is a high security concern for our team, any updates are greatly appreciated. Thanks!
Nicolas
planned
Yes, this behavior is not what people would expect, and it is painful to deal with for large organizations. We are planning to simplify the management of team and permissions.
Santa
@Nicolas: Hi Nicolas. Any news regarding this behavior? As we use many teams with external people, the actual standard is really annoying and also very dangerous. Do you have any date, when it will be "fixed"? Thank you!
Sumit Chachra
@Santa: agreed. this is a serious security issue infact for us as well :-(
'Mash
I totally agree, I have only just discovered this and it's a horror to deal with. I have multiple spaces and now have to go through everything to remove them all.