Learn how to receive instant notifications for events happening in your cloud ebook, either triggered by your team members or by your readers.

Notifications help you monitor events happening in your cloud ebook at any minute. If you have your ebook shared with team members, you may receive notifications once certain actions are made by them, such as editing a setting. Other notifications involve the reader using the ebook, such as logging into the library.

Kotobee supports 3 different types of notifications.

System Notifications

These notifications are similar to Facebook's notification toolbar at the header. You may access these notifications inside Kotobee Author from the bell icon located next to your name or email. Clicking on the icon will show you a listing of new and old notifications.

Push Notifications

While having Kotobee Author open, a notification will appear in a small popup window informing you of an event. The popup will display for a few seconds then hide. It is useful in case you have a different software open, and you'd still like to be informed by Kotobee Author of events.

Email Notifications

These types of notifications get sent to your email address.

Notification Settings

To select the type of notifications you would like to enable for your library, go to your cloud ebook settings, and select the Notification settings tab.

You will see a listing of all notifications supported by your cloud ebook, along with each notification's respective settings. For each notification, you may set how you would like to receive this notification by enabling checkboxes under System, Push, or Email.

Note that team members with appropriate privileges will also receive notifications. However, any member can choose to disable certain types of notifications from their Account Settings, under their user menu.

Setting a Callback URL

If you are doing tight integration with an external system, you can direct notifications to any callback URL of your choice. When any of the events occur, the Kotobee servers will send a request directly to the callback URL, passing many parameters describing the event, such as the name of the event, the user's name, email, id, etc.