>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 12/29/00, 4:00:03 AM, Daniel Reichenbach <[EMAIL PROTECTED]> wrote 
regarding [midgard-user] Getting started with 1.4:

> after playing a while with 1.4, i'm feeling a bit dumb :) What I
> understood so far, Sitegroups help me to create a fine grained
> access control, like having seperate groups for page development,
> layout development and content development. Correct me, if I got this
> wrong :)

No. Sitegroups help you to completely separate the contents for customer 
A from student-group B. Sitegroups is a way to virtually have two 
databases (or more), when there is actually only one. The only thing 
persons from different sitegroups can see both are the resources in 
special sitegroup SG0. This is used to provide every sitegroup with the 
same administration interface.

> Reading through the new 1.4 manual, i didn't get the point, where I
> can start building my sites. So let me describe, what I want to do.
> Hopefully someone can give me a starting point.

I'll give it a shot.

> 1.) Create a new sitegroup with three sub-groups, one for page
>     administration, one for layout administration and one for content
>     administration.

> 2.) Create a host record for this sitegroup.

A sitegroup must have a sitegroup admin, they can do anything within the 
sitegroup except creating/deleting host records, or changing port/URL for 
the host records. 

So:

1.) as root, create your sitegroup, and assign an admin group to it.
2.) relog as root*<sitegroupname>
3.) create a new person (<admin>, for example)
4.) add login credential for this person.
5.) make this person member of the admin group of this sitegroup.
6.) create a host record for this sitegroup.
6.) relog as <admin>+<sitegroupname>

Now, the admin will do the next steps:

a.) create groups <page>,<layout> and <content>
b.) create persons
c.) assign login information to these persons
d.) make these persons member of these groups.
e.) make the rootpage of the site owned by 
    group <page>, the rootstyle owned by group
    <layout> and create a toplevel topic and
    make it owned by group <content>

Now persons that are member of group <page> can modify all pages, members of 
<layout> can modify all styles, etc.
the admin user can modify everything save the exceptions mentioned 
earlier. 

Hope this will help you further, if not, holler.

Armand.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to