Petition: Call to improve security / access / privacy model

Most people who've worked with Dolphin have probably reached the point where I am (and have been several times in the few short months I've been working with Dolphin):

Pulling my hair out due to incomprehensible security settings

Though Dolphin is very powerful, and has a lot to be thankful for, there are many access control / security / privacy settings scattered throughout Dolphin and how they affect one another is, to a large extent, a great mystery.

Without going into too much detail, some of these settings include (see attached images for each):

  • Admin Privacy Settings
  • User Privacy Settings
  • Profile Privacy Settings
  • Module Privacy Settings
  • Membership levels & their associated actions
  • Default in several contexts including these

It's time for these to either be documented or simplified so they can be figured out. Granted this is not an easy endeavor, but it needs to start, since there is a large amount of time spent trying to figure this out.

If addressing this issue is high importance to you and the success of Dolphin, please respond to this post.

privacy_settings_admin.JPG · 90.5K · 95 views
privacy_settings.JPG · 53.5K · 93 views
profile_lock_popup.JPG · 31.5K · 83 views
membership_levels_highlight.JPG · 84.9K · 79 views
privacy_settings_default.JPG · 57.2K · 59 views
Quote · 1 Feb 2011
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.