|
Thursday 04 May 2006 4:58:47 am
Multiple websites can be installed and share the same database. The most common reason for doing this that I know of is to use a different design templates for the same data. We use this feature when installing redesigns that use new templates. Any editor can be given edit priviliges with a subtree limitation. This means that you create a role (teacher) that has edit priviliges, and assign those priviliges with a limitation based on the parent folder/object. So, assign that role to a user/group, and pick the starting page from which they can edit. They will only be able to edit content under that page in the tree. Your role can limit the viewing of pages in the same way, so you can restrict what users can see in either the admin or the public site. We stopped using sections for assigning roles a while ago, but it does work fine. It seems to add an extra step for this purpose (creating and assigning a section) when the subtree limitation works better. Sections are great for using unique designs for different parts of the site, though, and if you have already implemented it, then using it for permissions is not an extra step. Similarly, you should be able to allow teachers to create a subgroup of users, and add users to it (just an extension of the roles and permissions). In my experience though, this may be beyond the skill set of an average CMS user. I would expect that some manual configuration at the start of each semester may be necessary. Also, you may be able to pre-make the groups, and for teachers to add users would be easy. As long as the roles are assigned, it should be fine.
http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions
|