Community notification setup
Community supports in-app notifications and Bark mobile pushes. Each user opts in and supplies their own Bark URL. This personal setting applies across the groups and channels you participate in.
Open personal settings
In a community channel, click the Community personal settings gear beside search and pinned messages above the message area.
The panel has Notifications and Private message privacy tabs. Privacy controls who can send you a private message request.
Set up Bark
- Install Bark on your iPhone and allow notifications.
- Copy your device push URL from Bark, for example
https://api.day.app/your-device-key. This is a Bark URL, not an Nbility API key. - Open Community personal settings → Notifications, paste the URL, enable Push @mentions to Bark, and click Save.
- Click Send test notification after saving and check your phone. Each account can send one test per minute.
Only HTTPS is supported. For a self-hosted Bark server, enter the complete public device push URL. Localhost, private networks, and addresses rejected by the outbound security policy are unsupported. Query parameters such as sound, group, and level are preserved. The default group is community.
The URL contains a usable device key. Keep it private. Nbility encrypts the saved URL and only returns whether it is configured when loading settings. Leave the field blank to keep the saved URL when changing other settings. Paste a new URL and save to replace it. To delete it, click Remove saved URL, then save.
When pushes are sent
A message from another user that explicitly includes @your-username sends a Bark push in addition to the existing in-app notification. Use the member mention action to insert the correct username. Repeated mentions of the same person in one message queue one push. A reply that also explicitly mentions you sends a push too.
Replies without a mention, self mentions, private messages, and Agent messages do not trigger this setting. Muted groups do not send pushes. Pending pushes are skipped if the account is disabled, access is revoked, the user is removed, the message is deleted, or an edit removes the mention. Messages posted before you opted in are not replayed. Sound and delivery on your phone also depend on Bark, iOS notification permissions, and Focus settings.
Pushes include the sender, group, channel, and a message excerpt of about 240 characters. This information passes through your chosen Bark server, so use a service you trust. Tapping a push can open the message when the server has the correct client origin configured through FRONTEND_BASE_URL. Login and channel access are still required.
Disable or troubleshoot
Turn off the switch and save to stop subsequent Bark pushes. In-app notifications continue to follow their existing rules. Bark failures do not affect message sending or in-app notifications. Delivery has bounded retries; a lost network acknowledgement can cause a duplicate push.
If a test fails, check the complete device URL, HTTPS, server availability, and phone notification permissions. Save form changes before testing. Tests can be sent while the push switch is off. These settings are independent of usage summaries, balance alerts, and administrator payment notifications.