Multi-Tenancy

Overview

Hacktionbase is a multi-tenant platform. Each workspace operates in complete isolation — your data, configuration, and users are never shared with or accessible by other workspaces.

Workspace identification

Each workspace is identified by a unique slug, used as a subdomain across the platform:

Dashboard: acme.app.hacktionbase.com
Widget: acme.hacktionbase.com/w
API: authenticated via SDK key or API key, which identifies your workspace automatically

When you initialize the SDK, you provide your workspace slug:

Hacktionbase.init({
  sdkKey: 'sk_live_abc123',
  tenant: 'acme'  // Your workspace slug
});

Data isolation

Every workspace has its own fully isolated data store. This means:

Complete separation — users, conversations, events, and all other data belong exclusively to your workspace
No cross-workspace access — there is no way for one workspace to query or view another workspace’s data
Independent configuration — widget settings, team members, segments, and campaigns are all workspace-specific

Security

All API requests are authenticated and scoped to a single workspace
SDK keys and API keys are tied to your workspace and cannot access other workspaces
Widget sessions are isolated per workspace and per end-user

Plans

Each workspace has a plan that determines available features and quotas:

Plan	Description
Free	Core features with standard quotas
Growth	Extended features and higher quotas
Enterprise	Full feature access with custom limits

Features like session replay, AI assistant, and campaign volume scale with your plan. You can upgrade at any time from the dashboard.

Getting Started

SDK Reference

Widget

Concepts

Overview

Workspace identification

Data isolation

Security

Plans

​Overview

​Workspace identification

​Data isolation

​Security

​Plans

Overview

Workspace identification

Data isolation

Security

Plans