# Multi\_site restrict access to radiant

**URL:** <https://www.ruby-forum.com/t/multi-site-restrict-access-to-radiant/144987>\
**Category:** Radiant CMS\
**Created:** [August 4, 2008, 11:56pm UTC](https://www.ruby-forum.com/t/multi-site-restrict-access-to-radiant/144987 "2008-08-04T23:56:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c57346/32.png) [@marc\_a](https://www.ruby-forum.com/u/marc_a)\
**Post date:** [August 4, 2008, 11:56pm UTC](https://www.ruby-forum.com/t/multi-site-restrict-access-to-radiant/144987/1 "2008-08-04T23:56:04Z")

</div>

Hello everybody!

I’ve recently discover the multi\_site extension which appears to be  
really interesting.  
But there is some things that I still don’t know if it is possible and  
how to do them.

1-Imagine I have a radiant site called [marc.com](http://marc.com). I install the  
multi-site and then I create [site1.marc.com](http://site1.marc.com) and [site2.marc.com](http://site2.marc.com). Now I  
can manage the pages for the two “child” site1 and site2, but I can’t  
manage anymore the page from [marc.com](http://marc.com).

2-Is it possible to create administrator for each site? For example if I  
log in to radiant as an admin, I’ll see all my site. However I want to  
create site-administrator for each site so that they can log in to  
radiant and manage the pages of their own site without seeing all the  
other site.

Cheers  
Marc.

---

<div class="post-metadata">

**Author:** ![marc\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c57346/32.png) [@marc\_a](https://www.ruby-forum.com/u/marc_a)\
**Post date:** [August 6, 2008, 10:27am UTC](https://www.ruby-forum.com/t/multi-site-restrict-access-to-radiant/144987/2 "2008-08-06T10:27:33Z")

</div>

Hi Marc,

The multi\_site extension has those limitations you mention. I  
especially think #2 is a show stopper in many cases - all users sees  
all sites. It would take some work to tie logins to a specific site,  
but it would greatly enhance the value of the extension.

Cheers,  
Casper

---

<div class="post-metadata">

**Author:** ![marc\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c57346/32.png) [@marc\_a](https://www.ruby-forum.com/u/marc_a)\
**Post date:** [August 6, 2008, 10:32am UTC](https://www.ruby-forum.com/t/multi-site-restrict-access-to-radiant/144987/3 "2008-08-06T10:32:50Z")

</div>

There is a branch that starts down this road. You can tie specific  
users to each site, though Admins and Devs see all sites, normal usere  
do not.

Layouts can also be limited. It is not perfect, but a huge step in the  
right direction.

> **[GitHub - zapnap/radiant-multi-site-extension: An extension for Radiant CMS that...](https://github.com/zapnap/radiant-multi-site-extension/tree/master)**
>
> master

and the related blog post:

[http://blog.zerosum.org/2008/6/24/radiant-scoped-multi-update](http://blog.zerosum.org/2008/6/24/radiant-scoped-multi-update)

Keith

---

<div class="post-metadata">

**Author:** ![marc\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c57346/32.png) [@marc\_a](https://www.ruby-forum.com/u/marc_a)\
**Post date:** [August 6, 2008, 10:47am UTC](https://www.ruby-forum.com/t/multi-site-restrict-access-to-radiant/144987/4 "2008-08-06T10:47:15Z")

</div>

Hi

Thanks for your answers.  
It would be definitely great if we can assign user to a group.  
For now I’m using multi\_site and page\_group extension together to  
restrict the access.

Marc