Workspace creation is separate from user signup
Multi-workspace SaaS products have users who create additional workspaces after initial signup. These need their own confirmation email — not just a login welcome.
SaaS email template
Fire workspace.created with the workspace name, URL and setup steps. else.events sends a confirmation that drives immediate activation.
Multi-workspace SaaS products have users who create additional workspaces after initial signup. These need their own confirmation email — not just a login welcome.
A "workspace created" email with no "invite your team" or "connect your first integration" CTA misses the activation moment.
Users who create workspaces across multiple organisations need the workspace URL in the confirmation to navigate back easily.
Workspaces created via API (multi-tenant setup) also need notifications — to the workspace owner or the creating user.
Whether created through the UI or via API, your backend fires workspace.created. else.events sends the confirmation.
Include workspace_name and workspace_url in the event payload. The template renders the workspace link as the primary CTA.
Include an invite_url or setup_url in the payload. The template renders "Invite your team" or "Complete your workspace setup" as the primary action.
Edit workspace confirmation copy, add setup steps or change the CTA without touching the workspace creation code.
{{ user.name }}Creator's name{{ data.workspace_name }}Name of the newly created workspace{{ data.workspace_url }}Direct link to the new workspace{{ data.invite_url }}Link to invite team members to the workspace{{ data.plan }}Plan assigned to the workspaceWorkspace name, direct link and first-step CTA — all from the event payload.