I'm looking for some opinions if anyone would like to share...
I'm building a (D7) site for a non-profit advocacy organization. They want to have supporters register with the site and provide some specific information about themselves that will help the organization to "rally the troops" for specific initiatives. They want to have information like:
- where they are located so they can be directed to contact specific legislators
- what their skills are to help with specific projects
- what their motivating interests are to direct them to targeted trainings and events
There will be a Supporter role, and a couple of different roles created for the organizations staff. Some of those (staff) roles should be able to access/edit the Supporter profile data.
I'd also like to have some--but not all--of the user profile data to be viewable by other users in the Supporter role.
I was looking at the Profile2 as part of the solution, but the access control for certain fields is too restrictive... Either allowing full access to view fields, or only access for profile owners and Administrators. I need the access to be granted to a few specific staff roles--other than just administrators.
So I'm back to using the D7 core fields management, and then maybe something like the Content Access module to grant/restrict access to the data--assuming that that module works with User Profiles as "content" also.
Anyway... Just wondering how others have managed something like this, and hoping for suggestions/recommendations.
Hope you're all having a good summer.
Cheers
Comments
Flag, Flag Friend, Flag Friend Access
http://drupal.org/project/flag and http://drupal.org/project/flag_friend might work, the latter has an access module included though I don't know if it it works at the field level or the node level (which obviously wouldn't work).
I may be looking for too much
It seems that, if I just drop the ability for other members to view some of the user data, that the whole job gets simpler. Then I'd just set permissions to only allow the appropriate staff roles to View User Profiles so that they could view and collect the data they need.
The site isn't intended to be a social network, so the "need" for members to view other Supporters information isn't critical, and with the kind of data the site needs to gather (some of it sensitive), seeing all of it wouldn't be appropriate. I was wondering if there was a simple way to expose different bits of information depending on the role (basic for Supporters, and more for Staff).
Roger
_________________
Art has gone to the dogs
GoodeGallery.com