Pleas re consider

Would like to have this feature available.

Hi, this is a great question. @Box, please look into it.

Please bring this up for review, Dropbox for Business has had this feature for years, Box should be able to do it as well.

Can you try to reconsider this problem now, after 4 years? We are having serious issues with users repeatedly renaming our root folders, there are at least two threads with this problem, the second one is here https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/37403950-block-root-shared-folder-renaming

Everywhere in the IT world, the most typical scenario for sharing is folders created by some admin/HQ/IT dpt and those shared to users with various permissions, with one thing common - you never want the user to tamper with the name of the share itself - no matter if it is smb, sharepoint, NAS etc. This is definitely a Co-Owner/Owner permission, not editor - now there is no full r/w role without tampering with the root folder itself, it would make much more sense to leave this only for Owners/Co-Owners, or to give us the possibility to force this in enterprise settings (something like Only Owners/Co-Owners can rename the root folders"). Thank you

Today, only API can do this:
https://developer.box.com/reference/post-folder-locks/

Would be extremely valuable to offer this in the native user interface in order to avoid team members accidentally moving mission critical folders to incorrect places.

This should be merged with this request: https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/35984521--lock-a-folder-taxonomy

We already have folder locks for delete etc. And adding renaming to the folder lock abilities in the API would go a long way to addressing the folder taxonomy issues.

We would like this use case as well. We've created a Box folder structure with subfolders that serve as a "template" for a project which other users can copy and then modify/rename for use with their project. Unfortunately, users have accidentally moved the template folder.

We'd like the ability to lock the folder to disallow the following operations on the main folder and it subfolders:
- Moving
- Renaming
- Deleting

If we could lock main folders in place so they can't be moved but files within them can that would be great. Our staff accidentally edits or moves folders. Not all staff is extremely tech-savvy and this would help make BOX more user friendly for all skill levels.

Our staff accidentally edits or moves folders. Not all staff is extremely tech saavy and this would help make BOX more user friendly for all skill levels.

We have systems integrating with folders on Box.com. These functions either provide workflow timestamps, or move files from folder to folder. In order for these integrations to work seamlessly, folders cannot be accidentally or purposely renamed.

I would like to have a Folder properties setting to disable Folder Rename (even for Editors).

I was testing setting up departmental folders to replicate our group file server. I want all members of the department to be able to add/remove/delete files in their folder. I was able to do that by assigning them the editor role, but that allows them to change the root level folder name. Is there a way to prevent that?

For instance, I create folders for accounting, finance, etc. I want those folders to keep the names I set and I do not want the users to be able to change them. Anything they do inside is fine with me.

We have already enabled the restriction on users to create root level folders.

We leverage a template folder structure being replicated for each of our clients (new client gets same template folder structure as pre-existing clients)