Conditions for Notification Messages

Notification messages require the following conditions.

Note: This section presents an overview of requirements. Following sections explain the how to set up each requirement.

Notifications must be turned on in Workarea > Settings > Community Management > Notifications > Settings.

A message for the activity must be enabled in Workarea > Settings > Community Management > Notifications > Messages. (By default, a message is enabled for each activity.)

A user who wants to receive Notifications must enable each type of Notification for each agent in his profile’s Activities tab.

Note: A user's profile Activities tab has a Community Groups subtab, which lets the user set notification preferences for all community groups. To refine preferences further, a user can access the profile of any community group and click Edit Group Notification Preferences to set preferences for that particular group.

The user performing the action must allow the Notification to be generated by enabling it on his profile’s Activities tab.

To receive Notifications for

- another user’s activities, you must be his colleague

- a community group’s activities, you must be a group member

Note: The above points regarding message recipients are general. For specific details about which recipients receive notification messages, see Notification Message Recipients

The Notification system respects Ektron CMS400.NET’s content permissions. As a result, content-related Notifications are only sent to users with at least read-only permission for the content. See Also: Folder Permissions

For example, Julia adds content to an Ektron CMS400.NET folder for which her colleague, Tyler, does not have permission. Tyler is not notified when content is added, even though he signed up to be notified about colleagues’ activities.

However Kristin, another colleague who has permission to edit the folder’s content and who signed up to be notified about colleagues’ activities, does receive Notification of that event.

Similarly, private content is only viewable by authorized CMS users or membership users with at least Read-Only permissions for its folder.