The taxonomy access control are too wide. Add module specific access control, affecting only the 'files' vocabulary.

Comments

dikini’s picture

dikini commented

Ok, a question of my own. Should there be a single "modify directories" permission, or add/delete/create?

Simplicity over being thorough. At the moment I'm inclined to favour simplicity, unless you persuade me otherwise. I really hate the permissions UI.

View is a possibility, but I'm not sure I actually want to implement it. It will probably require modification to core, which I don't want. If core supports this, we will. I know that empty directories are a nuisance but hooking into every kind of taxonomy view can be a bigger one from so many angles.