[support] Log in according to user responsibility

[Carl Wiedemann]

You might investigate using the rules module to do this
http://drupal.org/project/rules, which can respond to user roles.

On Thu, Oct 28, 2010 at 5:31 PM, Roger <arelem at bigpond.com> wrote:

> Using Drupal 6.19
>
> We have a generic member's login for group members with password and
> user based on a current newsletter publication but this does not
> facilitate different pages depending on user.
>
> In our system certain users each have a role/responsibility.
>
> 6 coordinators who input calendar events for their particular State or
> Region.
> 6 coordinators update page displays for their State or Territory
> 12 reviewers who each review one of the above and approve or not, but do
> not have editing permissions.
> None of the above have admin permission.
> Permissions are tight and only for the explicit role.
>
> It is intended that the menus for each will provide only: Create
> content, edit, review, approve, send back, unpublish as appropriate for
> the role.
>
> The coordinator can see the page he/she is working on, but must be able
> to see the 'as if live' page before submitting it.
> Primarily because the cck editor does not present good representation of
> a live preview.
> The reviewer receives notification, views the completed page 'as if' it
> were live and approves/publishes or sends back for editing.
>
> Each of the above has their own user name and password. A reviewer for a
> particular region would use for example, 'reviewer-victoria' as the user
> name
> 'some_password' as the password
>
> Question: How can I set up a log in for each role so that it presents
> the appropriate log in page and menu, specific to that user login?
> The menu system I think I can do ok but I cannot find how to present the
> correct login page per user.
>
> Thanks in advance
> Roger
>
>
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20101028/3f6ad476/attachment.html