Skip to main content
The Notifications inbox is your single feed for everything happening across Vibely — product updates, invitations from other workspaces or projects, build/deploy outcomes, connector reauth prompts, and anything else worth your attention. Open the bell icon in the top bar to see it.

​
What lands in the inbox

  • What’s new in Vibely — feature launches, model upgrades, and important platform changes (the same updates published in the Changelog, surfaced in-app as they ship).
  • Workspace invitations — when someone invites you to their workspace, accept or decline from the inbox without leaving your current project.
  • Project invitations — collaborators adding you to a specific project show up here too, so you don’t miss a hand-off.
  • Build & deploy events — completions, failures, and publish results across your projects.
  • Connector reauth prompts — Slack, Stripe, GitHub, and other connectors expiring or needing re-consent.
  • Billing & credit alerts — thresholds crossed, top-up confirmations, plan changes.
  • Security & account events — sign-ins from new devices, 2FA changes, password resets.
Each item is actionable — click to jump to the project, accept/decline an invite, or reauth a connector inline.

​
Channels

Vibely has three notification channels. Each event can be routed to any combination of them — including none.
ChannelWhere it shows upDefault
EmailYour notification email (set in Account)On
PushBrowser push (desktop & mobile, when granted)Off
In-chatA bell badge inside the Vibely appOn
Change them in Settings → Notifications.

​
What can fire

The full set of events Vibely will notify on:
EventFires whenRecommended channel
Product updateA new feature or major improvement ships on VibelyIn-chat
Build completedA long-running build / generation finishesPush
Build failedA build errored outEmail + In-chat
Deploy completedPublish to preview or production succeededIn-chat
Deploy failedPublish errored outEmail + In-chat
Connector auth expiredA connector (Slack, Stripe, GitHub) needs reauthEmail + In-chat
Workspace invite receivedSomeone invited you to their workspaceEmail + In-chat
Project invite receivedSomeone added you as a collaborator on a projectEmail + In-chat
Workspace invite acceptedSomeone you invited joinedIn-chat
Billing threshold hitYou crossed 50% / 80% / 100% of your monthly creditsEmail
Security alertNew-device sign-in, 2FA change, or password resetEmail + In-chat
Weekly digestSummary of last week’s builds and credit usageEmail
Each row is independently toggleable. Turning off “Build completed” doesn’t touch “Build failed” — most people keep failures noisy and successes quiet.

​
Sensible defaults for common roles

If you don’t want to think about it, copy one of these: Heads-down builder — only failures and connector reauth: 
Build completed     → off
Build failed        → Email + In-chat
Deploy completed    → off
Deploy failed       → Email + In-chat
Connector expired   → Email + In-chat
Invites             → In-chat
Billing             → Email (only the 80% and 100% rows)
Weekly digest       → off
On a team, watching builds — push on all completions, mute the digest: 
Build completed     → Push
Build failed        → Push + In-chat
Deploy completed    → Push
Deploy failed       → Push + In-chat
Connector expired   → Email
Invites             → In-chat
Billing             → Email
Weekly digest       → off
Trying Vibely casually — only the things that block you: 
Build failed        → In-chat
Deploy failed       → In-chat
Connector expired   → In-chat
Billing             → Email
Everything else     → off

​
Push notifications

Push requires browser permission. The first time you toggle any push row on, Vibely asks for permission. Deny once and most browsers will silently block future asks — re-enable via your browser’s site settings for vibely.sh. Push works on:
  • Desktop Chrome, Edge, Brave, Firefox
  • Mobile Chrome on Android
  • Mobile Safari (iOS 16.4+) only when Vibely is installed as a PWA (“Add to Home Screen”)
Mobile Safari without PWA install can’t receive web push at all — that’s an Apple constraint, not a Vibely one.

​
Email — primary vs notification

Two email addresses live on your account:
  • Primary email — sign-in, billing receipts, security alerts. Always-on, can’t be muted.
  • Notification email — everything in the table above. Defaults to your primary; change it if you want notifications routed to a personal address while billing stays on a corporate one.
Set both in Settings → Account.

​
Quiet hours

Not yet supported — every event fires immediately on whichever channels you’ve enabled. If you need a digest-only mode for a particular event, switching to the Weekly digest row catches most cases.

​
Unsubscribing entirely

Every Vibely email has an unsubscribe footer that mutes that event type globally. Use it instead of marking emails as spam — once enough recipients spam-mark, deliverability for legitimate emails (verification, billing) suffers for everyone on the platform.