tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/351-folder-access-and-system-nameCascade CMS: Discussion 2011-10-11T19:13:14Ztag:help-archives.hannonhill.com,2010-02-09:Comment/55813452011-02-25T22:05:47Z2011-02-25T22:05:47ZFolder Access and System Name<div><p>Kris,</p>
<p>In recent versions the ability to move or rename a folder is now
its own permission, so you can restrict that. I think that covers
most of what I care about when it comes to giving write
permissions.</p>
<p>I don't know about metadata though. If no one needs to edit the
metadata regularly you can set the metadata, then hide it in the
metadata set options.</p></div>Lee Roberson (Function Digital LLC)tag:help-archives.hannonhill.com,2010-02-09:Comment/55813452011-02-25T22:25:01Z2011-02-25T22:25:01ZFolder Access and System Name<div><p>Unfortunately using that role based permission setting doesn't
work in this case. I need to limit the moving or renaming of the
top level folder, but the user needs to be able to create, edit,
move, rename or delete any asset under that folder.</p></div>Kristag:help-archives.hannonhill.com,2010-02-09:Comment/55813452011-03-02T18:33:42Z2011-03-02T18:33:42ZFolder Access and System Name<div><p>Any other suggestions out there?</p></div>Kristag:help-archives.hannonhill.com,2010-02-09:Comment/55813452011-10-11T19:13:13Z2011-10-11T19:13:13ZFolder Access and System Name<div><p>Hi Kris,</p>
<p>I noticed this discussion as I was looking through old
unresolved posts. The only thing that comes to mind for me is what
Lee mentioned regarding the configuration of your Metadata Sets to
use hidden fields.</p>
<p>If you can think of any improvements that you would like to see,
please be sure to file them here: <a href=
"http://ideas.hannonhill.com">http://ideas.hannonhill.com</a></p>
<p>Thanks!</p></div>Tim