Notifications

​

Introduction

Long replies and generations can take a while. Aikeedo tells users when one is done, so they can leave the page and come back when it’s ready. Users are notified when:

• A chat response is ready, fails, or needs their input, such as an approval for a connector tool.
• An image, video, speech, transcription or isolated voice is ready, or its generation fails.
• A scheduled task finishes a run, or a run fails.

Users are not notified about items they are already looking at, items created in private mode, or generations that stalled for more than a day. Opening an item, running it again or answering it marks its notifications as read. Notifications work without any setup. Browser alerts can be turned off and retention changed under Settings → Notifications.

​

The bell

Every notification appears under the bell in the sidebar, and in the header on mobile. A dot on the bell means there are unread notifications. The list shows the newest first and loads more as the user scrolls. Clicking a notification opens the item. Mark all as read clears the dot. Users can also open the list with Ctrl + Shift + B (⌘ + Shift + B on Mac). See Keyboard Shortcuts.

​

Browser alerts

Browser alerts reach users outside the app, even when every tab is closed. Each user allows them for their own browser. They can do this in several places:

• Settings → General → Notifications → Browser alerts → Allow in the app.
• Notify me, offered while a reply or generation is running, with You can leave this page.
• Enable on the banner at the top of the bell’s list.
• Turning on any of the notification switches in their settings.

The browser then asks the user to allow notifications for your site. To stop alerts later, users revoke the permission in the browser’s site settings. Signing out also stops alerts on that browser. Clicking an alert opens the item. Alerts show the app icon from the PWA settings, or the favicon if it isn’t an SVG.

​

Requirements

• HTTPS. Browsers only allow alerts on secure sites.
• A supporting browser. Current desktop browsers support them. On iPhone and iPad, alerts work only once the app is added to the Home Screen as a PWA. Where alerts aren’t supported, users still get notifications under the bell.
• Cron or a background worker. Alerts are sent as background jobs, so they arrive within a minute with cron alone, or at once with a worker.

There is nothing else to set up. The keys browsers need to accept alerts from your site are created the first time a user allows alerts, and stored in your database.

​

User settings

Each user chooses what they are notified about under Settings → General → Notifications in the app. All of these are on by default: The Browser alerts row shows whether alerts are allowed in this browser, with Allow if they aren’t yet.

​

Admin settings

Go to Settings → Notifications.

​

Browser alerts

Status turns browser alerts on or off for the whole site. It is on by default. When it is off, the app never asks for the browser’s permission and sends no alerts. Notifications still appear under the bell.

​

Retention

Old notifications are deleted once a day by the Delete old notifications system task, which runs from cron.

​

OneSignal

Browser alerts are built in and don’t need OneSignal. If you already use OneSignal, it keeps working alongside them.

​

Troubleshooting

​

Need Help?

If you need assistance with Aikeedo: