Skip to main content
Socializioz uses in-app notifications to surface important workspace events. Notification preferences are available in Settings → Notifications and are loaded and saved through the authenticated user-preferences flow.

​
Notification center

Use the bell in the workspace header to review current notifications. The notification center can show platform-aware or system events with a title, message, time, read state, and an action when the event has a supported destination. Supported notification records can include events related to:
  • Successful publishing.
  • Publishing failures.
  • Approval needs.
  • Connected-account issues.
  • Campaign changes.
  • Billing or subscription state changes.
  • Integration connection events.
  • Other operational events produced by the current Socializioz backend.
The exact list depends on which producers are active in the current product and on your saved notification preferences.

​
Read state

Unread notifications contribute to the bell’s unread state. You can mark an individual notification as read or use the available Mark all as read action. The application refreshes the notification list periodically while the app is active and also refreshes when you return to the window. The current polling interval is approximately 90 seconds; provider events themselves can arrive on different schedules.
Notification polling is not the same thing as real-time provider delivery. A social platform can report an event later than the action that caused it.

​
Notification sound

When in-app notifications are enabled and the unread count increases, Socializioz can play a short browser-generated chime. Browser autoplay rules, a muted tab, device volume, or unsupported Web Audio behavior can prevent the sound from playing. The sound is secondary to the persisted notification state.

​
Preferences

Open Settings → Notifications to change the controls that are currently exposed.

​
Master control

Enable notifications turns the saved notification preference set on or off. When it is off, the event-specific and channel controls are not used for visible notification delivery.

​
Delivery controls currently exposed

The current settings UI intentionally does not expose browser push or email-digest controls because those delivery pipelines are not currently implemented as complete user-facing features.
Do not rely on old screenshots or earlier documentation that shows browser push, daily/weekly digest selectors, or engagement-milestone switches. Those controls are not part of the current Notification Settings interface.

​
Event preferences

When notifications are enabled, the current settings screen exposes these event categories:
  • Post published.
  • Post failed.
  • Approval needed.
  • Account issues.
  • Campaign updates.
The saved preference is used to filter applicable user-visible notifications.

​
Engagement milestones

The preferences schema still has room for an engagement-milestone preference, but the current settings UI deliberately does not expose that switch because no production notification producer currently creates engagement-milestone events. Use Analytics for performance review instead of expecting milestone alerts.

​
Quiet hours

Quiet hours are available in Notification Settings. The current control is specifically described in the product as pausing notification emails during the selected time window. It should not be documented as a universal suppression switch for every in-app event or sound. To configure it:
  1. Turn on Quiet hours.
  2. Set the start and end times.
  3. Save the changes.
Quiet hours use the saved user timezone. The timezone itself has one canonical home under Profile rather than a second editable timezone field inside Notification Settings.

​
Saving changes

Notification settings are not treated as saved merely because a switch was changed locally. When you modify a preference, use Save changes. If the authoritative preferences cannot be loaded, Socializioz does not expose an editable default form that could overwrite an unknown server state. This fail-closed behavior protects existing preferences during a temporary settings-read failure.

​
Push notifications

Browser/OS push notification delivery is not currently exposed as a working Socializioz notification channel in the current settings UI. There is no active user-facing push-subscription setup to document today. When push delivery is implemented and exposed, this page should be updated from the shipped product rather than from the dormant preference-schema field.

​
Email digests

Daily/weekly email digests are likewise not currently exposed in Notification Settings. The stored schema can preserve fields for future functionality without making that functionality public.

​
Troubleshooting

Last modified on August 16, 2026