---
name: bijection-notifications-vllnt
description: "Evaluate and integrate the Notifications Vllnt component with Bijection."
---

# Notifications Vllnt

Per-subject directed inbox — deliver notifications with read/unread state and fan-out as a Bijection component

- Package: @bijectionhq/notifications-vllnt
- Category: Messaging
- Status: Reference
- License: MIT
- Bijection source (repository access required): https://github.com/bijectionhq/notifications-vllnt/tree/30678273bded3b391b72610c93eac590861b5a2e
- Upstream: https://github.com/vllnt/convex-notifications/tree/574a29f2bda9d07a0f016c1edb38154b2a3e38e0
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/notifications-vllnt

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/notifications-vllnt.git
cd notifications-vllnt
git checkout 30678273bded3b391b72610c93eac590861b5a2e
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.

## Original upstream skill

The following guidance describes @vllnt/convex-notifications. Its installation commands and APIs refer to the upstream package. Evaluate compatibility with the Bijection source separately.


> Agents: read this skill fully before writing code that uses Notifications Inbox. Follow the installation and configuration steps exactly.

# Notifications Inbox

## Instructions

@vllnt/convex-notifications stores a notification inbox for each opaque subject reference. The application defines notification types and a typed payload, so the same component can serve different product surfaces.

deliver writes one notification per recipient, including fan-out to several recipients. list and unreadCount support inbox screens and badges through host queries. markRead and bounded markAllRead clear unread state. Retention cleanup removes eligible read notifications.

The host authenticates recipients, gates access, and chooses which events create notifications. This is an in-app data store; it does not send APNs/FCM push notifications, SMS, or email. Device delivery and channel preferences belong in your integration.

Maintained by [bntvllnt](https://bntvllnt.com) at [VLLNT](https://vllnt.com). Find the author on [GitHub](https://github.com/bntvllnt) and [X](https://x.com/bntvllnt).

### Installation

```bash
npm install @vllnt/convex-notifications
```

Current npm version: `@vllnt/convex-notifications@0.1.0`

## Use cases

- Team tools: notify people about mentions, assignments, or shared-resource updates.
- Mobile apps: retain account and product notices in an in-app inbox.
- Learning platforms: display lesson, feedback, or course activity notices.
- Games and communities: surface invitations, replies, or host-defined milestones.

## How it works

deliver writes one notification per recipient, including fan-out to several recipients. list and unreadCount support inbox screens and badges through host queries. markRead and bounded markAllRead clear unread state. Retention cleanup removes eligible read notifications.

The host authenticates recipients, gates access, and chooses which events create notifications. This is an in-app data store; it does not send APNs/FCM push notifications, SMS, or email. Device delivery and channel preferences belong in your integration.

## When NOT to use

- When a simpler built-in solution exists for your specific use case
- If you are not using Convex as your backend
- When the functionality provided by Notifications Inbox is not needed

## Resources

- [npm package](https://www.npmjs.com/package/%40vllnt%2Fconvex-notifications)
- [GitHub repository](https://github.com/vllnt/convex-notifications)
- [Live demo](https://vllnt.com/)
- [Convex Components Directory](https://www.convex.dev/components/vllnt/convex-notifications)
- [Convex documentation](https://docs.convex.dev)