Thread

So far, the sites I run off EE have been entirely managed by myself and my partners. I have not even made it possible to register accounts for different levels of access, because it hasn’t been needed.

Now, I am looking at adding account registration, but since I have not built the site at all with this in mind, how much would I need to change to ensure that members can only access what I want them to access?

Specifically, I am looking at giving them access to one out of several wikis and possibly one out of several blogs. What’s the most effective way to go about this? Do I have to add checks to all templates for the other wikis and blogs, to keep them out, or can I set it up so that the default is that they can’t edit and then make it possible only on the selected wiki and blog?

Any suggestions? 😊 For example, I have two existing wikis. If I add a third, which the members I’d be adding should have access to, how do I keep them out from the other two wikis? Or is it a matter of granting them access to the third rather than removing access from the other two?

Wikis have member permissions (assigning to Users in the Wiki control panel), and/or you can control access to templates with the Access link in the Template Manager.  If you need more discrete control, you would use conditionals in your template based on logged_in_member_group.  Let us know if you need additional details for a specific access control method!

So when a new member is created (and assigned to the default member group), they don’t automatically have access to my existing wikis and blogs? I am sort of trying to wrap my head around if what I need to do is go in and secure everything currently existing (there’s currently nothing in my templates that checks for whether someone is a member or not) or if what I do is open up the things I want to give access to.

Oh, okay, I see that wikis aren’t an issue. They could just each have their own group rather than the default. That’s easy enough. 😊

And you can always change which group is the default group for new registrants, allowing you to screen them as they register to place them into the appropriate group.

Yeah, I would probably go with that approach, so there’s nothing they automatically access in case I have some standard checks for the regular Member group that I have forgotten about.