There are three settings for managing membership:
1. This place allows public access, and anyone can join2. This place allows public access
3. This place does not allow public access
In many cases the place owner does not want to manage individual memberships but they still want to know who is a member and they those members included in email and name picklist dialogs. The solution for this is to use “allow public access, and anyone can join”.
If the place owner also wants to prevent the non-members from seeing the content of the place then the default behavior is not going to be adequate. The following outline will walk through the steps to secure the place and still provide self-join.
1.Open your place in the browser
2. Create a new role by going into Place Actions -> Manage Roles
3. Then click the “New Role” button
4. You will be presented with a dialog box allowing you to name and describe the role. For this walk through the role will be called “custom public access role”:
5. Click OK and the role will be created. The system will automatically take you to back to the Manage Roles screen and the new role will be expanded. Allow this role to read the initial page but prevent them from reading any other pages.
6. Click Save to save the new role
7. Now this role needs to be assigned to the public user. To do this select Place Actions -> Edit place
8. You can now configure the Public Role to use this new role
9. Click Save.
The public user can now only see the welcome page.
If you need a different welcome page:
This approach can be extended one step further by creating a different Welcome page for members and non-members. To achieve this:
1. Add a new page for the public members (In the screenshot below it is called "Public Welcome Page". The rich text portlet is a good choice for content for this page
2. In the step above where we assigned role privileges assign the custom role to the “Public Welcome Page” and to no other pages.
3. For every other role the role security needs to be adjusted to hide the Public Welcome Page with a result as follows:
Following the approaches above will allow for self join and still restrict visibility of your content. One caveat is that if new components are added then they should also be configured in the manage roles area in order to ensure that they are also restricted.
For template use, the default public role configuration will persist so newly generated places will work as expected.