Thanks, Rob! I was messing about in there, but did not hit the magic recipe.
Thanks to your inputs, I have been able to make it work for me. There are a few
changes / differences, but it works nicely now. Here's what I did:
First, the goal is for a non-manager to be able to review and approve new
member requests using the member approval workflow that installs with remember.
There is no need to permit modification after that. I also didn't want to
interfere with other portal roles.
1. Create a new site role called "portalist" and give that role "membrane: Edit
member ID" and "membrane: Register member" rights in the portal root/security
tab.
2. Minor change in the workflow transitions for register_private and
register_public: The permissions guard in the default install calls out
"Remember: Register member" I changed that to "membrane: Register member" ( I
could find no Register member for remember, so maybe this is a bug?)
3. To allow the Portalist role to be notified via portlet of new member
requests, I edited the "pending" state security to give the "portalist" role
rights to "mail forgotten password" "view", "membrane: Edit member ID" and
"membrane: Register member"
Works great! Now I won't be bothered with people complaining that they tried
to join and never got a response!
Thanks!
Gray McCord
"Adapt, Mutate, Migrate, or Die"
-C. Darwin
-----Original Message-----
From: Rob Miller [mailto:[email protected]]
Sent: Wednesday, February 11, 2009 5:47 PM
To: [email protected]
Subject: Re: [Remember Mailing List] Allow non-manager to approve new
memberships.
Gray McCord wrote:
> I’m using remember on a plone 3.17 installation with the approval
> workflow. What I would like to do is have someone with a reviewer role
> be able to approve new members when they apply ffrom the registration
> form. I thought this would be a simple matter of adding “reviewer” to
> the various workflow state permissions, but all I can get it to do is
> give me the approval form with only “disable member” as an option. I’m
> obviously missing something. Any advice?
you were barking up the wrong tree w/ adding "reviewer" to the workflow state
permissions. that might give reviewer folks permission to view or edit or
otherwise tweak a member object that is in a given state, but it doesn't
relate at all to whether or not someone is able to CHANGE the workflow state
of that object, which is what you want to do.
to do that, you want to look at the workflow transitions. there are two that
you care about, register_private and register_public. each of them is guarded
by here/isValid (i.e. the member object in question has passed validation) and
by the "remember: Register member" permission.
so.... you should just be able to make sure that the reviewer role (or
whatever role you want to use) has the register member permission and it will
start working. i'd recommend going in and re-setting the workflow state
permissions to their original settings, unless there are other privileges that
you explicitly want reviewer type folks to have.
-r
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2009/02/1234396038031
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact
[email protected] for questions.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2009/02/1234459470512
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact
[email protected] for questions.
