CiviCRM Community Forums (archive)

Hi, I'm new here... so apologies if this question has been raised before. Browsing through the forum, I couldn't find any adequate answers.

My problem is quite simple really. We are trying to construct an online database so people can sign up to our newsletter and upcoming events. They should be able to register themselves and update their profiles in the future. We are currently using a Drupal page that displays CiviCRM profiles as the frontend. CiviCRM is our "backend" and should only be accessible to site administrators.

Unfortunately, this is currently not the case as people can access CiviCRM by clicking on their first or last name in the profile view, for example. This takes them to a CiviCRM search result. From there, users can perform other searches and access data that they shouldn't be able to see. Also, the unsubscribe option in a CiviMail message links to a CiviCRM page from where people can access other information.

Hence my questions:

• how can we effectively separate the drupal (frontend) and CiviCRM (backend)?
• should CiviCRM acutally be used as a (restricted) backend? how could we use it as a frontend with the same user restrictions?
• how can we remove the unwanted links in the drupal profile view?

I hope I made my problem clear. Thanks for any advice!

Denis

Thanks; this was a good hint. Without the "Profile" option selected in CiviCRM, you now get an error message when you click on your name in the Drupal profile.

I assume you cannot avoid that certain elements in the profile are clickable? Needless to say, this would be the more elegant solution.

Thanks again,
Denis