Multi-tenant
Private templates
Templates, their variables and their version numbers are rows in your workspace behind Postgres row-level security. Another workspace's API cannot list, render or see that they exist.
Content that stays in your workspace
Stored with your workspace
Every template is read and written in a database transaction scoped to your workspace, so a query only ever sees your rows.
Not found, not forbidden
Ask for a template by an ID from another workspace and nothing comes back. The row is invisible, so the answer is a 404.
Variables stay with the template
Variable defaults are stored on the template row and rendered inside your workspace.
Duplicating stays home
Duplicating a template creates the copy in the same workspace.
What is scoped
- Templates
- Name, subject, HTML and text bodies.
- Variables
- The variable list and its defaults.
- Version
- Counted inside your workspace. Each save adds one.
- Duplicates
- Created in the workspace that owns the original.
PostFrame, answered
What happens if another workspace requests my template by ID?
Nothing comes back. Row-level security hides the row entirely, so the request is answered as if the template did not exist: a 404, not a 403 that would confirm it does.
Are my template variables private too?
Yes. Variables are stored on the template row and rendered on the server inside your workspace's transaction. They are never visible to another workspace.
Can a template be shared between two workspaces?
Not directly. Export the HTML and create it in the other workspace, or duplicate it inside the workspace that owns it.
Run your business from one place.
Five plans, 25 launch apps, one dashboard. Change tiers any time.
From $0 · Basic $9.95/mo · Upgrade or downgrade any time