Docs for content page and CRUD operations for context

content/docs/platform/inbox/configuration/inbox-with-context.mdx

@@ -0,0 +1,78 @@
+---
+pageTitle: 'Using contexts for Inbox personalization'
+title: 'Inbox with context'
+description: 'Learn how to use contexts in the Inbox component to filter and personalize notifications for your subscribers.'
+icon: 'Package'
+---
+
+_Contexts_ let you scope each <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> instance to a specific environment, tenant, or app within your product. When combined with workflow-level contexts, they ensure that each <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> displays only the notifications relevant to that specific context.
+
+<Callout type='info'>If you’re new to contexts, start from the [Contexts](/platform/workflow/contexts) section to understand how contexts are created, managed in Novu and how they used in workflows.</Callout>
+
+## How context works in `<Inbox/>`
+
+The <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> uses exact-match context filtering to determine which notifications to display. This means the context provided to the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> must match all the key-value pairs of the context used when the workflow was triggered.
+
+This creates predictable isolation and ensures notifications can't accidentally leak across boundaries. If the contexts do not match exactly, the notification will not be delivered to that Inbox session.
+
+| Workflow Context                           | Inbox Context            | Displayed? |
+| ------------------------------------------ | ------------------------ | ---------- |
+| `{ "tenant": "acme" }`                     | `{ "tenant": "acme" }`   | ✅ Yes      |
+| `{ "tenant": "acme" }`                     | `{ "tenant": "globex" }` | ❌ No       |
+| `{ "tenant": "acme", "app": "dashboard" }` | `{ "tenant": "acme" }`   | ❌ No       |
+| `{}`                                       | `{}`                     | ✅ Yes      |
+
+
+### Creating context via `<Inbox/>`
+
+If a new context is passed from the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> that doesn’t already exist, Novu will automatically create it. This means you don’t have to manually set up contexts before using them, they are created just in time.
+
+This is particularly useful for:
+
+- **Dynamic tenants or organizations**: When users join or switch organizations.
+- **Per-environment views**: Isolating notifications for staging, production, or preview.
+- **Feature-specific dashboards**: Where each section of your app has its own notification scope.
+
+You can view all automatically created contexts under the Contexts section of your Novu dashboard.
+
+## Applying context to the Inbox
+
+You can filter the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> notifications to a specific context, by passing a context prop to the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component.
+
+This prop's value defines the filter for that session, and it will only request and show notifications that match this context.
+
+```typescript
+import { Inbox } from '@novu/react';
+
+<Inbox
+  applicationIdentifier="APPLICATION_IDENTIFIER"
+  subscriber="SUBSCRIBER_ID"
+  context={{
+    tenant: {
+      id: 'acme-corp',
+      data: {
+        name: 'Acme Corporation',
+        plan: 'enterprise',
+      },
+    },
+  }}
+/>
+```
+
+When a workflow with these exact context is triggered, as seen below
+
+![Context in trigger](/images/inbox/context-trigger.png)
+
+Then, the notifications will be delivered to the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method>.
+
+![Inbox with context](/images/inbox/context.png)
+
+<Callout>To learn how to use context with the Novu SDKs, visit the <Method href="/platform/sdks/javascript">{`Context`}</Method> documentation.</Callout>
+
+## How to secure your context
+
+Because the context prop is set on the client-side, a malicious user could potentially tamper with it to view notifications from a different tenant.
+
+To prevent this, you must validate the session using HMAC encryption. This ensures that the context data comes from your server and has not been altered.
+
+<Callout>Learn how to secure your <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> with HMAC encryption, refer to the [Prepare for Production](/platform/inbox/prepare-for-production) documentation.</Callout>

content/docs/platform/inbox/configuration/meta.json

@@ -1,6 +1,6 @@
 {
   "title": "Customize and configure",
   "icon": "SlidersHorizontal",
-  "pages": ["styling", "icons", "tabs", "preferences", "data-object"],
-  "description": "Learn how to configure your inbox with styling, tabs, preferences, data objects, and snooze functionality"
+  "pages": ["styling", "tabs", "preferences", "data-object", "inbox-with-context", "icons"],
+  "description": "Learn how to configure your inbox with styling, tabs, preferences, data objects, icons and context functionality"
 }

content/docs/platform/meta.json

@@ -22,6 +22,7 @@
     "workflow/step-conditions",
     "workflow/tags",
     "workflow/translations",
+    "workflow/contexts",
     "---Channels---",
     "...integrations",
     "---Account---",

content/docs/platform/sdks/javascript/index.mdx

@@ -26,6 +26,13 @@ The Novu client provides methods to interact with notifications, preferences, an
     "description": "",
     "type": "string"
   },
+  "context": {
+    "description": "A context object to filter notifications for this session.",
+    "type": "object"
+    },
+  "contextHash": { 
+    "description": "The HMAC-SHA256 hash of the context object. Required if context is provided and HMAC is enabled.", "type": "string"
+    },
   "apiUrl": {
     "description": "",
     "type": "string"
@@ -50,7 +57,7 @@ The Novu client provides methods to interact with notifications, preferences, an
 
 ### Usage
 
-<Tabs items={['US', 'EU', 'HMAC Encryption']}>
+<Tabs items={['US', 'EU', 'Using Context', 'HMAC Encryption']}>
   <Tab value="US">
     ```typescript
     import { Novu } from "@novu/js";
@@ -73,6 +80,30 @@ The Novu client provides methods to interact with notifications, preferences, an
     });
     ```
   </Tab>
+  <Tab value="Using Context">
+  <Callout type="info"> Learn how Context is used to filter Inbox notifications in the [Inbox with Context](/platform/inbox/customization-and-configuration/inbox-with-context) guide. </Callout>
+  ```tsx
+  import { Novu } from '@novu/js';
+
+  const novu = new Novu({
+    applicationIdentifier: 'YOUR_APP_ID',
+    subscriberId: 'user-123',
+    context: {
+      tenant: { id: 'org-123', data: { name: 'Acme Corp' } },
+      team: 'team-456',
+    },
+  });
+
+  // Access the current context
+  console.log(novu.context);
+  // → { tenant: { id: 'org-123', data: { name: 'Acme Corp' } }, team: 'team-456' }
+
+  // Get a stable string key (used internally for caching/filtering)
+  console.log(novu.contextKey);
+  // → "team:team-456,tenant:org-123"
+
+  ```
+  </Tab>
   <Tab value="HMAC Encryption">
     ```typescript
     import { Novu } from "@novu/js";

content/docs/platform/sdks/react/hooks/novu-provider.mdx

@@ -24,6 +24,14 @@ Usually, it's placed somewhere in the root of your application, which makes the
       type: "string",
       description: "HMAC encryption hash for the subscriber",
     },
+    context: {
+      type: "object",
+      description: "Defines contextual attributes (for example, tenant, app, team) for filtering and personalizing notifications.",
+    },
+    contextHash: {
+      type: "string", 
+      description: "The HMAC-SHA256 hash of the context object. Required if context is provided and HMAC is enabled." 
+    },
     apiUrl: {
       type: "string",
       description: "Custom backend URL for self-hosted instances",
@@ -43,7 +51,7 @@ Usually, it's placed somewhere in the root of your application, which makes the
 
 ## Example Usage
 
-<Tabs items={['US', 'EU', 'HMAC Encryption']}>
+<Tabs items={['US', 'EU', 'Using Context', 'HMAC Encryption']}>
   <Tab value="US">
     ```tsx
     import { NovuProvider } from '@novu/react';
@@ -80,6 +88,33 @@ Usually, it's placed somewhere in the root of your application, which makes the
     ```
 
   </Tab>
+  <Tab value="Using Context">
+    <Callout type="info"> Learn how to use Context for filtering and personalization in the [Inbox withContext](/platform/inbox/configuration/inbox-with-context) guide.</Callout>
+    ```tsx
+    import { NovuProvider, useNovu } from '@novu/react';
+
+    function App() {
+      return (
+      <NovuProvider
+        applicationIdentifier="APPLICATION_IDENTIFIER"
+        subscriber="SUBSCRIBER_ID"
+        context={{
+          tenant: { id: "org-123" }
+        }}
+      >
+        <App />
+      </NovuProvider>
+      );
+    }
+
+    // In child components
+    const MyComponent = () => {
+      const novu = useNovu();
+      console.log(novu.context);
+      // Logs: { tenant: { id: "org-123" } }
+    };
+    ```
+  </Tab>
   <Tab value="HMAC Encryption">
     <Callout type="info">
       Read more about [HMAC Encryption](/platform/inbox/prepare-for-production#secure-your-inbox-with-hmac-encryption).
@@ -102,4 +137,4 @@ Usually, it's placed somewhere in the root of your application, which makes the
     ```
 
   </Tab>
-</Tabs>
+</Tabs>

content/docs/platform/workflow/contexts/contexts-in-workflows.mdx

@@ -0,0 +1,79 @@
+---
+pageTitle: 'Personalize workflows and templates in Novu using context'
+title: 'Applying context'
+description: 'Learn how to use contexts in Novu to personalize notification templates, control workflow logic, and customize the Inbox. Understand supported data formats and how to debug context usage from the activity feed.'
+---
+
+Contexts let you personalize how notifications are rendered and delivered by making contextual data available inside template editors, step conditions, and the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component.
+
+## How to use context
+
+Once a context is created either through the Novu dashboard or API, its data becomes available for use in your templates editors, step conditions, and for customizing the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component.
+
+### Using context data in the template editor
+
+Use the `{{context}}` Handlebars helper to access context data in any template editor. The context key you provide while creating the context (for example, tenant, region) becomes the accessor.
+
+
+For example, if a context with this data is created:
+
+```json
+context: {
+  tenant: {
+    id: 'acme-corp',
+    data: {
+      name: 'Acme Corporation',
+      plan: 'enterprise'
+    }
+  }
+}
+```
+
+You can access the `name` and `plan` in your in-app, email, SMS, or push template like this:
+
+```html
+<p>Welcome, new user from {{context.tenant.data.name}}!</p>
+<p>Your account is on the {{context.tenant.data.plan}} plan.</p>
+```
+Or
+
+```text
+Welcome, new user from {{context.tenant.data.name}}!
+Your account is on the {{context.tenant.data.plan}} plan.
+```
+
+![Using context data in the template editor](/images/workflows/contexts/context.gif)
+
+<Callout>Refer to the Inbox documentation, to learn how to use context in the <Method href="/platform/inbox/configuration/inbox-with-context">{`<Inbox />`}</Method> component. </Callout>
+
+### Using context in step conditions
+
+You can use context variables in the **Step conditions** tab of a workflow step to add conditional logic to your notifications. For example, only send a "Feature X is now enabled" email if `context.tenant.data.plan` is `enterprise`.
+![Context step conditions](/images/workflows/context-step-conditions.png)
+
+To learn how contexts are structured or how to define them, refer to the [Managing Contexts](/platform/workflow/contexts/manage-contexts) documentation.
+
+## Viewing and debugging contexts
+
+Once you start using contexts in your workflows, Novu provides full observability so you can monitor and debug your context usage after a workflow has been triggered.
+
+### Searching for workflow runs
+
+You can filter your workflow runs to find all executions associated with a specific context.
+
+1. Navigate to the **Activity Feed** in your Novu dashboard.
+2. Select the **Workflow Runs** tab.
+3. In the search bar, click **Context** and enter the context `type` and `id` using the format `type:id`.
+
+![Searching for workflow runs](/images/workflows/search-context-activityfeed.png)
+
+### Verifying the resolved context
+
+To confirm that Novu received and processed your context data correctly, you can inspect the API traces for a specific run.
+
+1. From the **Activity Feed**, select the relevant workflow run from the list in the **Requests** tab.
+2. In the workflow run details, go to the **API Traces** tab.
+
+Here, you will see the full context object that was resolved and attached to that specific workflow execution.
+
+![Verifying the resolved context](/images/workflows/resolved-context.png)

content/docs/platform/workflow/contexts/index.mdx

@@ -0,0 +1,71 @@
+---
+pageTitle: 'Context'
+title: 'Context'
+description: "Learn what Contexts are in Novu, how they differ from payloads, and how they help you organize and personalize notifications across workflows."
+icon: 'Package'
+---
+
+_Contexts_ are flexible, user-defined data objects that help you organize and personalize your notifications. They let you attach metadata, such as tenant, region, or app details, and enable contextual behavior to workflows, notifications, and other entities across Novu.
+
+In simple terms, a context acts like an extended version of the payload. While the payload exists only for the duration of a single workflow execution, contexts are persistent and can be reused across multiple workflows or API calls. This makes them ideal for multi-tenant environments, dynamic branding, and use cases where notifications depend on shared or reusable data.
+
+## How context works
+
+Context solves the common problem of sending differentiated notifications to the same subscriber without creating duplicate subscriber records or complex workarounds.
+
+For example, if you have a single subscriber entity, `[email protected]`, who uses two different applications you offer: "Notion Email" and "Notion Calendar". You want to send notifications specific to each application.
+
+Without context, you might have to create two different subscribers or use workarounds with subscriber ID prefixes to differentiate the notifications.
+
+```javascript
+// Problem: How does Novu know which app is sending the notification?
+
+// Notion Email notification
+await novu.trigger('new-email-received', {
+  to: '[email protected]',
+  payload: { title: 'You have 1 new email' }
+});
+
+// Notion Calendar notification  
+await novu.trigger('new-calendar-event', {
+  to: '[email protected]',
+  payload: { title: 'You have a new meeting invite' }
+});
+```
+
+However, with context, you can provide this metadata directly in the trigger. This allows you to use a single workflow and subscriber entity, while dynamically changing content or logic based on the context.
+
+```javascript
+// Solution: Pass an 'app' context to differentiate triggers.
+
+// Notion Email notification
+await novu.trigger('new-email-received', {
+  to: '[email protected]',
+  payload: { title: 'You have 1 new email' },
+  context: {
+    app: 'notion-email',
+    branding: {
+      logo: "url_for_email_logo.png"
+    }
+  }
+});
+
+// Notion Calendar notification  
+await novu.trigger('new-calendar-event', {
+  to: '[email protected]',
+  payload: { title: 'You have a new meeting invite' },
+  context: {
+    app: 'notion-calendar',
+    branding: {
+      logo: "url_for_calendar_logo.png"
+    }
+  }
+});
+```
+
+Here are some ways that you can use contexts:
+
+- **Multi-tenancy and app routing**: Use a tenant or app context to dynamically alter notification content, branding, or logic for different customers or applications from a single workflow.
+- **Shared chat credentials**: For chat providers like Slack or MS Teams, store workspace-level credentials (for example, a bot token) in a context. This allows multiple subscribers within that workspace to receive notifications without each subscriber needing to store the shared token.
+- **A/B testing**: Pass a campaign identifier in a context (for example, campaign: 'new-welcome-email-v2'). Use this in a condition step to split users into different notification paths and measure which performs better.
+- **Data residency and compliance**: Use a region context to tag notifications with their origin. This can help in applying data retention policies or filtering data for compliance audits.