If you try to click the "Sign the guestbook" button at this point, you'll probably meet a rude page that resembles the following screenshot.

That's right buddy, the object is unavailable! This phenomenon is perfectly normal; and the explanation is fairly simple. When clicked, the "Sign the guestbook" button that we just put in initiates an action within the content management system. eZ publish will attempt to create a new object using the current user, which in this case (since nobody is logged in) is the built-in "Anonymous" user. Not surprisingly, the default security settings do not allow anonymous users to mess around with content. In order to make the button work, we'll simply have to let anonymous users to be able to do two things:

• Create guestbook entries within the guestbook section
• Edit the contents of guestbook entries

The following step-by-step guide explains how to enable this functionality.

1. Make sure that you're logged into the administration interface.
2. Click on the "User accounts" tab.
   A list of users/groups will appear.
3. Click on "Roles and policies" (from within the menu on the left hand side).
   A list of roles will appear.
4. Click on the "Anonymous" user.
   The properties of the Anonymous user will appear.
5. Click on the "Edit" button.
6. Click the "New policy" button.
7. Select "Content" from the "Module" dropdown box.
8. Click the "Grant access to one function" button.
9. Select "Create" from the "Function" dropdown box.
10. Click the "Grant limited access" button.
11. Set the class to "Guestbook", the section to "Guestbook section" and the ParentClass to "Any".
12. Click the "OK" button.

At this point, the list of role policies for the anonymous user should look something like this:

The previous list of steps took care of adding "Create" privileges to the anonymous role. In addition, we'll also have to add "edit" privileges to this role. Repeat the previous steps, but this time make sure that you select the "Edit" function (at step two) and that you select "Self" from within the owner list (at step three). The rest of the selections should be the same as in the list of steps presented above.

At this point, the list of role policies for the anonymous user should look something like this: