Box Status

Non-obvious effects of enabling "Restrict content creation"?

Answered
Follow
New post
BD

Hi all,

I would like to better understand the effects of enabling the "Restrict content creation" setting in Enterprise Settings, as explained in the "Closed Folder Taxonomy" section of https://support.box.com/hc/en-us/articles/360043695494-Plan-Your-Folder-Structure  Currently, "Restrict content creation" is disabled, and we are operating using an Open Folder Taxonomy.

We have non-admin users who currently have folders/files in their root level. Some examples of these folders/files are:

  • "My Box Notes" folder automatically(?) created by Box.
  • "Getting Started with Box.pdf" automatically saved by Box during onboarding.
  • Folders automatically created as a result of third-party integrations, such as "Microsoft Teams Chat Files".

If we enable "Restrict content creation",
  1) Will existing folders/files in non-admins' roots be deleted, moved, or remain where they are?
  2) Will non-admins be able to rename or delete existing folders/files in their root?
  3) Will non-admins continue to be able to save data within the existing root folders? For example, a non-admin with a "Microsoft Teams Chat Files" folder will continue to be able to use that folder integration with Microsoft Teams, which automatically saves chat files into that folder.

Thanks.

0

Comments

2 comments

Date Votes
  • BD

    Bump.

    We would really appreciate an official response on this topic.

    0
    Comment actions Permalink
  • Rona
    • Edited

    Hi there, 

    Welcome to Box Community and glad to help! 

    Here's to answer your questions regarding your managed user's access to first-level folders once 'Closed Folder Taxonomy' is implemented.

      1) Will existing folders/files in non-admins' roots be deleted, moved, or remain where they are? Your managed user's own first-level folder will remain accessible even after you've enabled 'Restrict Content Creation.'
      2) Will non-admins be able to rename or delete existing folders/files in their root? Renaming folders will vary according to the user's permission to the folder. However, they can no longer delete first-level folders. Your managed users will have to contact their Box Administrators. 
      3) Will non-admins continue to be able to save data within the existing root folders? For example, a non-admin with a "Microsoft Teams Chat Files" folder will continue to be able to use that folder integration with Microsoft Teams, which automatically saves chat files into that folder.

    As long as they are involved in the folder as collaborator and given the right permission. Your managed user will be able to upload or save files in the folder. 

    Hope it helps! 

    0
    Comment actions Permalink

Please sign in to leave a comment.