Glossary · Security & access
Multi-tenant workspace isolation
Also called: tenant isolation, data isolation, multi-tenancy
Multi-tenant workspace isolation means many customers (tenants) share one software system while each workspace's data, credentials and activity are kept strictly separate, so no tenant can see or affect another's.
Almost all SaaS is multi-tenant: one application and one database serve many customers. That's efficient, and it puts the burden on the vendor to make sure data never crosses between tenants, including through bugs.
How isolation is enforced
- At the data layer. Every row carries its tenant, and the database itself refuses to return rows from another tenant (row-level security), not just the application code.
- For secrets. Credentials and API keys are encrypted and scoped to the workspace that saved them.
- At the edges. Webhook URLs, exports, search and caches are all scoped per workspace.
- For people. Membership is per workspace; being in one gives no access to another.
Why it matters for agencies
An agency running automations for twenty clients holds twenty sets of CRM tokens and AI keys. If everything lives in one account, one mistake (a workflow pointed at the wrong client's HubSpot) leaks data. One workspace per client makes that mistake structurally hard.
Questions to ask
Is isolation enforced in the database or only in application code? Are credentials encrypted per workspace? Can support staff access workspaces, and is that access logged and visible to the customer?
In Fluxo Flow
Every workspace's data is separated in the database with row-level security, and data from one workspace is never visible in another. Credentials and AI keys are encrypted at rest and belong to the workspace that saved them. Agencies give each client its own workspace; on the Partner plan, support access to a client workspace is read-only, limited to an hour, can be switched off by the client and is recorded in the client's activity log.
Read next
Related terms
- White labelWhite-label software is a product built by one company that another company resells under its own brand, name and domain, with the original vendor hidden from the end customer.
- RBAC (role-based access control)Role-based access control (RBAC) is a way of managing permissions in which access rights are attached to roles (such as Admin, Editor or Viewer) and people get rights by being assigned a role, rather than permission by permission.
- Audit logAn audit log is a chronological, tamper-resistant record of who did what in a system and when, kept so that changes, approvals and access can be traced afterwards.
- No-code automationNo-code automation is building automated workflows with visual tools (drag-and-drop canvases, forms and pickers) instead of writing code, so people who know the process can automate it themselves.
- Low-codeLow-code describes development tools where most of an application or workflow is built visually, with small amounts of code (expressions, scripts or API calls) added where the visual tools run out.