# My admin tool hack for page editor

**URL:** <https://www.ruby-forum.com/t/my-admin-tool-hack-for-page-editor/71268>\
**Category:** Radiant CMS\
**Created:** [October 6, 2006, 3:41pm UTC](https://www.ruby-forum.com/t/my-admin-tool-hack-for-page-editor/71268 "2006-10-06T15:41:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![orff](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/b38774/32.png) [@orff](https://www.ruby-forum.com/u/orff)\
**Post date:** [October 6, 2006, 3:41pm UTC](https://www.ruby-forum.com/t/my-admin-tool-hack-for-page-editor/71268/1 "2006-10-06T15:41:58Z")

</div>

I added in details for a hack into the admin tools for letting the admin  
specifiy a top-level page for a user to view:

[http://dev.radiantcms.org/radiant/wiki/HowToSetATopLevelPageForUser](http://dev.radiantcms.org/radiant/wiki/HowToSetATopLevelPageForUser)

We needed a way to have specific users only be able to edit certain  
parts of  
the site (like MSCMS ‘channels’). I saw in the mailing list other  
people  
were asking for similar functionality – a way to have specific users  
for  
multiple site, etc.

It seems to work okay, but definitely needs some more improved security.  
Maybe a new method in the page controller called before edit to see if  
that  
user isnt going out of bounds of their page setting?

Let me know what you guys think. I love this project and am a decent  
rails  
programmer. If the core devs have some suggestions and want me to build  
on  
this code I have no problem finishing this up and submitting code via  
subversion.

-mike