Is there any way to prevent a certain group from creating folders, but keeping the ability for that group to create documents?
Solved! Go to Solution.
This is unfortunately not possible with default / low-level permissions only as there is no distinction about which type of node is about to be created. Using a custom permission model, a customisation of Repository-tier web scripts, and some customisation of the Share document library "create content" menu, it would be possible to achieve something like this for Alfresco Share, but it would still be possible for members of that group to create folders via e.g. CMIS / WebDAV (mapped network drive). A solution to that would be to implement Java-based behaviours which throw exceptions as a kind of "veto" when members of the group create folders, but that would potentially generate errors in CMIS / WebDAV clients which had checked permissions before to determine they could create folders to later then be thwarted with an unexpected error.
So you see: It is possible with some trickery and limitations, but it would always take quite some hacks for a rather incomplete overall solution.
This is unfortunately not possible with default / low-level permissions only as there is no distinction about which type of node is about to be created. Using a custom permission model, a customisation of Repository-tier web scripts, and some customisation of the Share document library "create content" menu, it would be possible to achieve something like this for Alfresco Share, but it would still be possible for members of that group to create folders via e.g. CMIS / WebDAV (mapped network drive). A solution to that would be to implement Java-based behaviours which throw exceptions as a kind of "veto" when members of the group create folders, but that would potentially generate errors in CMIS / WebDAV clients which had checked permissions before to determine they could create folders to later then be thwarted with an unexpected error.
So you see: It is possible with some trickery and limitations, but it would always take quite some hacks for a rather incomplete overall solution.
Since in this specific project CMIS/WebDav won't be used (at least it shouldn't), the UI path could be a solution. Thanks for the info.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.