# Access control to the admin interface

**URL:** <https://www.ruby-forum.com/t/access-control-to-the-admin-interface/63089>\
**Category:** Radiant CMS\
**Created:** [June 11, 2006, 11:06pm UTC](https://www.ruby-forum.com/t/access-control-to-the-admin-interface/63089 "2006-06-11T23:06:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\
**Post date:** [June 11, 2006, 11:06pm UTC](https://www.ruby-forum.com/t/access-control-to-the-admin-interface/63089/1 "2006-06-11T23:06:22Z")

</div>

Hello. At this time there are in radiant two access roles:  
administrator and developer. For the site I’m going to develop I’d  
need at least a third role which is similar to the developer one but  
whose editing capabilities are limited to a branch of the site. For  
example, a Greek author or a German one should only be able to edit  
(remove, add, change) their language branch rather than the whole  
site. They should also be forbidden to remove snippets, layouts and so  
on. Is there a “simple” way I can reach such level of access control  
at the current stage of development of radiant? Many thanks.  
–Maurizio

---

<div class="post-metadata">

**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\
**Post date:** [June 12, 2006, 6:52pm UTC](https://www.ruby-forum.com/t/access-control-to-the-admin-interface/63089/2 "2006-06-12T18:52:22Z")

</div>

Maurizio B. wrote:

> Hello. At this time there are in radiant two access roles:  
> administrator and developer. For the site I’m going to develop I’d  
> need at least a third role which is similar to the developer one but  
> whose editing capabilities are limited to a branch of the site. For  
> example, a Greek author or a German one should only be able to edit  
> (remove, add, change) their language branch rather than the whole  
> site. They should also be forbidden to remove snippets, layouts and so  
> on. Is there a “simple” way I can reach such level of access control  
> at the current stage of development of radiant? Many thanks.

There is not really an easy way to do this right now. I’m considering  
adding the ability to do this with the rest of the full administration  
system, but haven’t made any decisions.

You might consider running multiple Radiant installs if you need to  
prevent English users from accessing the German content.

–  
John L.  
[http://wiseheartdesign.com](http://wiseheartdesign.com)

---

<div class="post-metadata">

**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\
**Post date:** [June 12, 2006, 7:21pm UTC](https://www.ruby-forum.com/t/access-control-to-the-admin-interface/63089/3 "2006-06-12T19:21:13Z")

</div>

John W. Long wrote:

> You might consider running multiple Radiant installs if you need to  
> prevent English users from accessing the German content.

s/English/Greek/

–  
John L.  
[http://wiseheartdesign.com](http://wiseheartdesign.com)

---

<div class="post-metadata">

**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\
**Post date:** [June 12, 2006, 7:35pm UTC](https://www.ruby-forum.com/t/access-control-to-the-admin-interface/63089/4 "2006-06-12T19:35:04Z")

</div>

John, thank you for your suggestion. I’ll likely go with it. I’m  
looking forward to the upcoming administrative access facility and  
also to protected access to part of the web site by the end users. --M