CiviCRM Community Forums (archive)

I've been looking around to see if this question has ever been posted before, but is it possible to use a different CiviCRM profile for Drupal account create/edit and profile depending on Drupal user role?

The way I have my site set up now, people complete a CiviContribute page and pay membership dues.  In this page, they fill out a CiviCRM profile called "Member Information" which automatically adds them to the Members contact group and records their membership in the General Membership membership type in CiviCRM.  This is the same CiviCRM profile members see in the Drupal user accounts, which they can edit.  This is also the same searchable data used in the Member Directory.  All of this is working beautifully.

What I would like to do, though, is to allow two types of registrations, one Member registration using the process described above and one more limited Supporter registration.   Right now, Supporters complete a CiviContribute page, pay a smaller amount of money, but I haven't enabled Drupal sign up because I don't want them to fill out the CiviCRM Member Information profile used in Drupal user accounts.

I would like Supporters to be able to log in and have only limited access to the members' features.  The problem is that Supporters still have the Member Information profile tied to their user accounts in Drupal, which they will see and edit and etc., adding themselves wrongfully to the Members contact group and making their info searchable in the Member Directory, which is a feature they should not have access to.

So my question is, is there a way to use a Supporter Information profile in Supporter user accounts (those who have the Supporter Drupal role)  and only have the Member Information profile visible/editable in the Member user accounts (those who have the Member Drupal role)?  when I tried to set up the Supporter Information profile to be used in Drupal user accounts, that just linked both profiles to all the user accounts.

The best solution I found so far was to remove the Drupal member profile link from the Supporter menu so they can't edit their user information at all, but that will also not allow them to edit their password, and since the automatically generated Drupal passwords are random and unmemorable, they should be able to choose their own. 

So can different Drupal account CiviCRM profiles be used according to Drupal role (or CiviCRM ACL)?

Thank you!  (I hope what I wrote made sense...)