Posted by mikey_p on February 10, 2007 at 9:21pm
What roles are you using on your church websites? OR what roles do you think are needed? I'm planning on sitting down and hacking some more on drupal for churches and want to get some place to start here, and I'll update my svn when I get to a critical point.
Basically I want to know what roles you need, and what other access control methods you are using? Are you using what built into views? Field level permissions with CCK? Taxonomy Access? Organic Groups? What are the basic roles and examples of the user permissions for those roles? And what is a typical user for each of those roles?
Thanks!
-Mike
Comments
As few as possible
I've tried to setup as few roles as possible and I've based them upon what those individuals need to do to the site. I've got the following:
At some point, I may decide to role maintainers and staff or staff and leaders together and might also add a role for members just so we can show them a slightly different front page, but otherwise, I like it as is.
We've got loads of roles
One of the big benefits of using CMS for a church website I think is that it allows you to let lots of different people keep the site up to date - no technical knowledge required. Our site is set up in different sections which reflect the different activities etc that go on. So there is a bit for youth, students, what's on, sermon downloads and so on. Each bit is maintained by different people. So we use TAC to make sure that no accidents happen and the wrong bit gets changed. This allows lots of volunteers to keep different bits up to dates, as well as people that are paid to organise their stuff as a job (e.g. the youth worker).
So I have an "author" role that controls what most users that contribute will need (tinymce, create storys etc) and then lots of roles such as "youth", "student", "downloads", "office" which give users access via TAC to edit the appropriate sections. Does that make sense?
Chris
Exactly what we're planning
Although our Drupal site is still pre-release, this is exactly the structure we're planning. We already have a general role for "content administrator" who is a person with privileges to edit anything else that is posted, but with no other administrative privileges. In our organization, this role is assigned to a volunteer with PR background who can go in and edit page content for clarity, style consistency, etc.
We have a taxonomy that pretty much parallels the structure of the various ministries, and we'll create a role with privileges to edit and moderate each of these sections. Then, we'll assign to each of these roles the relevant staff person, as well as any volunteers (like committee chairs) who are involved in organizational governance in that area.