Workspaces
A workspace holds one product's templates, triggers, automations, contacts and API keys.
Workspace "Acme app"
├── Email provider: Resend (acme.com)
├── Templates
├── Triggers
├── Automations
├── Contacts and the suppression list (Audience)
└── API keysA workspace is the unit everything else belongs to. The API and the code call it a project: projectId in a contact is the workspace id.
What a workspace holds
- Templates designed in the editor.
- Triggers that send one template through the API, and automations that react to events. See Triggers and automations.
- Contacts, created from events, and the suppression list (Audience).
- API keys. A key works for its own workspace only. See Authentication.
- One email provider, selected in the workspace's Settings.
Use one workspace per product or per sending domain. Contacts, suppressions and keys are never shared between workspaces.
Providers belong to the account
Email providers are added under Providers, outside any workspace, and each workspace picks one of them in its Settings. Two workspaces can use the same provider; a workspace uses exactly one at a time.
Cloud only
On senlo.io, workspaces and providers belong to an organization. Everyone you invite to the organization sees its workspaces, with a role: owner, admin, editor or viewer. Viewers read, editors and above change things, owners and admins manage members. Plan limits (workspaces, emails and automation runs a month) apply per organization. See Pricing.
Self-hosted only
On your own instance, workspaces and providers belong to the user who created them. There are no organizations, roles or plan limits.