For the site I'm setting up there are a few areas that I'd like to control access to. One, which is easy with amember, is to control access to on-line content which is paid-for access. The user signs up for this "product" and gets access. It's a single directory, i.e. pub_content, that is protected as such thru amember. What I'd also like to do is use amember to manage accounts for the authors and admins of this content (which is another area of the site entirely, i.e. priv_area). The authors can create content and the admins can publish this content. All that really means is that they can write to the database and modify the records indicating yes to publish, or no not to publish. All of the author/admin db access pages are stored in priv_area so I want to limit access to that directory to just those users. Since the author/admin area is not really a product, but it is a seperate directory, is there a way that I can use amember to control access to this yet make sure that non authors/admins don't gain access and/or sign-up for this thru amember? Thanks, Todd
Todd, why don't create a special product for that? You may hide it from customers by settings Scope = disabled, but you still be able to assign it from aMember CP.