Every client in its own sealed workspace.
Every client lives in an isolated workspace; record-level rules enforce data separation at the database level. This isn't a folder convention or a UI filter you can fat-finger past — it's enforced where the data lives. PulseCraft was built multi-tenant from day one, for agencies that can't afford a leak between accounts.
Switching clients swaps the entire dashboard — content, accounts, metrics, history — in one click.
SYS.001
Isolation that's real, not cosmetic
Each client workspace is sealed beneath a shared engine. Record-level rules decide what every user and request can see, so a member working on client A cannot reach client B's content, accounts, or credentials — even by guessing a URL. The engine runs once; the data stays apart.
SYS.002
The client switcher
One control swaps your entire context: the active client's content plans, connected accounts, brand styles, metrics, and history all change together. No logging out, no separate tools per client, no chance of posting to the wrong account because two tabs looked alike.
SYS.003
Role-based access
Role-based access with manager, creator, and publisher roles. Roles decide who can draft, who can approve, and who can publish — per workspace.
| Role | Can draft | Can approve | Can publish | Sees API credentials |
|---|---|---|---|---|
| Manager | ✓ | ✓ | ✓ | ✓ (admins only) |
| Creator | ✓ | — | — | — |
| Publisher | — | ✓ | ✓ | — |
SYS.004
Per-client everything
Every client carries its own:
- Brand styles (visual, language, mood)
- Content sources and schedules
- Connected platform accounts
- Content and publishing history
Nothing is shared by accident.
SYS.005
Workspaces by plan
| Plan | Client workspaces |
|---|---|
| Free | 1 |
| Starter | 1 |
| Professional | 3 |
| Enterprise | Unlimited |
For more than three clients — plus white-label — see Enterprise and the pricing add-ons.
Questions, answered
Can one client's team see another client's data?
No. Separation is enforced with record-level rules at the database layer, not a UI filter — a user scoped to one workspace cannot read another's content, accounts, or credentials.
What's involved in setting up a new client workspace?
Four steps: create the workspace, set its brand styles, connect its sources, and connect its accounts. Each lives only inside that workspace, so nothing carries over from another client by accident — then the engine starts drafting against that client's sources.
Who can see a client's API credentials?
Only admins. Creators and publishers work with content and never see the underlying keys or platform tokens.
Forty minutes from now, this could be running.
Free month · 10 posts · No credit card
Related: Solutions for agencies · Security · Pricing · Brand Intelligence