tenant_id
in your event or workflow call. Know more about how to manage tenants within SuprSend here.
📘 If you have a use case where the entire user base and notifications differ between two distinct business lines within your company, we recommend using different workspaces to manage these notifications effectively. This approach ensures clear separation and management of workflows, templates, and user data, tailored specifically to the unique requirements of each business line.
Sending notifications for a tenant
By default, all notifications (aka workflow) are triggered for default tenant (your organization). You can override tenant by passingtenant_id
in your workflow or event instance. Passing tenant_id
in your workflow will:
- Pick tenant properties for sending custom notification content or design for the tenant (by replacing tenant variables in the template).
- Pick per-tenant preferences while executing the workflow.
- Override vendor details for the tenant if set. This is especially useful for cases where you are sending notifications on behalf of your customers and they want the notifications to be sent with their email domain and tenant/brand handles or you have different customer applications for sending messages on chat applications (Slack and MS Teams).