Alex - The more I have utilized aMember, the more something becomes apparent. For the sake of clarity, there needs to be a logical distinction between access rights and subscriptions. Defining 'Administrative Privs' as a subscription just doesn't make sense. There needs to be a logical division. Products are initially seperate from access groups. One should specify the default user group for a system, and then speficy alternative user levels for each individual product. The user group will define further actions (upgrading forum access via plug-in, etc). The user should check for the appropriate user group on each protected page, not an individual product. This generalized model betters suits both those who just run membership sites, and those who sell subscriptions. And this model closely resembles standard models utilized mainly in OS administrative systems and forum software. Thoughts anyone?