Permissions

If you find that the Admin can add/edit events however your users can’t, then check that your PostCalendar permission should be above your default user permission like so:

• Users PostCalendar:: .* Comment
• Users .* .* Comment

Below you will find a description of what each PostNuke access level will do inside PostCalendar.

• NONE

This setting will deny access to all PostCalendar Pages

• OVERVIEW

This setting will allow users to see the calendar but not view event details

• READ

This setting will allow users to see the calendar and view event details

• COMMENT since PostCalendar 4.0.1

This setting will allow users to see the calendar, view event details and add/edit their own events. (Since PostCalendar 4.0.1)

• MODERATE

not currently used

• EDIT

not currently used

• ADD

not currently used PostCalendar 4.0.0 and below used this to allow users to ADD events, this is deprecated, please use the COMMENT permission instead.

• DELETE

not currently used

• ADMIN

This setting will give a user Admin Permission for PostCalendar

There are currently five types of Permission settings for PostCalendar. Each one is described below.

This permission will restrict certain events based on the event information. It is used as such:

Format:

Note that in the above example Event Title would be the complete text title of the event you wish to hide. If you know the Event ID then you could use it instead.

Examples:

In the first permission setting, the Group or User the permission is applied to will not be able to view the Event entitled My Birthday. The second example denies access to the event with an ID of 7.

This permission will restrict certain events based on the Category the belong to. It is used as such:

Format:

Note that in the above example Category Name would be the complete category name of the category you wish to hide. If you know the Category ID then you could use it instead.

Examples:

In the first permission setting, the Group or User the permission is applied to will not be able to view events in the Birthdays category. The second example denies access to events that belong to the category associated with ID 7.

This permission will restrict certain events based on the User it belongs to. It is used as such:

Format:

Note that in the above example User Name would be the name of the user whos events you wish to hide. If you know the User ID then you could use it instead.

Examples:

In the first permission setting, the Group or User the permission is applied to will not be able to view events submitted by iansym. The second example denies access to events that belong to the user associated with ID 7.

This permission will restrict certain events based on the Topic it belongs to. It is used as such:

Format:

Note that in the above example Group/Username would be the User or Group who you wish to control events for.

Examples:

In the first permission setting, the Group or User the permission is applied to will not be able to view events submitted in the topic !PostCalendar. The second example denies access to events that belong to the topic associated with ID 7.

This is a much more general permission setting and is used to control such things as overall access to the calendar and admin rights. It is used like the above settings, just with less granularity.

Format:

Examples:

The first example gives ADMIN access to the user iansym. The second example allows Anonymous user’s to view the calendar but not see event details.