Workspaces & products
One account can own several businesses. Each business activity has its own workspace and operating limits.
Tenant = workspace = product
In BenjiAds, tenant, workspace, and product refer to the same business unit. The interface calls it a workspace; some internal and API field names use tenantId.
For example, Alex Plumbing is one workspace with the plumber vertical. Alex Landscaping is another workspace with the landscaper vertical, even if Alex owns both.
Alex's account
├── Alex Plumbing · workspace A · vertical: plumber
│ ├── Website and lead-capture funnel
│ ├── Leads and performance
│ ├── Subscription and advertising wallet
│ └── Campaigns, creatives, locations, and connections
└── Alex Landscaping · workspace B · vertical: landscaper
└── Its own site, leads, subscription, wallet, and connectionsWhat belongs to what?
| Concept | Meaning | Example |
|---|---|---|
| Account | The signed-in owner | Alex |
| Workspace / tenant / product | One business activity operated in BenjiAds | Alex Plumbing |
| Vertical | The trade template and its configured rules | plumber |
| Location / service area | Where this business works | Austin, TX |
| Site | The workspace's public website and funnel | alex-plumbing.benjiads.com |
| Campaign | Advertising prepared for that workspace | A plumbing campaign targeting its service areas |
| API key / OAuth connection | Access to exactly one workspace | A reporting assistant for Alex Plumbing |
A vertical is a template, not a shared customer account. Two plumbers have separate workspaces. Their sites, leads, billing, and advertising funds stay separate.
Multiple locations
A workspace can have multiple locations or service areas for the same business activity. A location is not automatically a new workspace. For location ad packs, the daily budget is divided across the selected locations; it is not multiplied by their count.
State-specific requirements are evaluated from the workspace's selected locations. Read licenses and restrictions before targeting more than one state.
Ownership and authorization
Every integration connection belongs to one workspace and carries explicit permissions. Its resource IDs are resolved inside that workspace. A campaign or job ID from another workspace cannot be used to access it.
To connect a second workspace, create a second key or approve a second OAuth connection. The x-workspace header cannot move an integration credential to another workspace.
Billing boundaries
Subscriptions and advertising wallets belong to workspaces. Advertising funds are separate from the SaaS subscription, and integration request counters are separate from both.
The existing included advertising credit is granted once per owner account, not once for every newly created workspace. Creating more workspaces does not reset that allowance.