On this page
In short. An organization is assembled from a blueprint, not fixed. The blueprint turns on plugins, the plugins own pillars (eCom, marketing, market, audience), and the active pillars decide which screens, brief rules and decision-engine surfaces the organization sees.
How it works#
A super admin picks a blueprint when provisioning (Provision a new organization). An administrator can change plugins afterwards. Each layer reads the one before it, so a layer added on top can hide a surface or add a reader, never widen what the base allows.
- Blueprint. One of six shapes in the picker, listed in Reference. It names the plugins, the dashboard templates and the menu each role starts with.
- Plugin. Connectors are on for the planes the shape runs; feature plugins are on by name or by opt-in.
- Pillar. What a plugin provides: eCom, marketing, CRM, social, market or audience. A screen shows only when its pillar is active.
- Domain layer. HR, finance, warehouse or Multi-dimension panel. Each is the Organization datasets blueprint plus one layer, which adds that layer's pages and measures. HR and warehouse also add a morning-brief reader; finance and the panel layer add none.
A commerce and a marketing organization run the same decision loop. Commerce measures orders; marketing measures leads, deals or deal value. A dataset workspace declares no lever, so the engine abstains instead of borrowing the commerce list.
What each organization reads#
Each plugin resolves to its own pillar, screens and brief pack, so most organizations stack several: marketplace orders next to marketing spend next to market estimates. The three data planes never mix (Connectors and data planes). Only orders and CRM leads/deals can be a decision's measured outcome. Market data is an estimate: it is labelled, never reconciled, and never an outcome.
The first page a member opens after sign-in depends on the pillars that are on, then on the default page an admin set (Multi-brand workspaces).
Where it stops#
The picker offers a fixed set of blueprints and layers. A shape outside it is a missing declaration, not something an admin builds from the UI. Rollout state of each pillar is on Project status.
Reference#
Blueprints
| Blueprint | Pillars | Lands on |
|---|---|---|
| Standard commerce | eCom; marketing for the seller's own ads | Commerce overview dashboard; marketplace and marketing connectors |
| Standard dashboard pack | eCom; marketing | The four retail dashboards and Data validation, open to every role |
| Marketing analytics | Marketing, CRM, social; market estimates beside them | Marketing performance pages, social listening, the decision loop |
| Market data only | Market, a third-party estimate | Market intelligence hub; every commerce screen hidden |
| Content Intelligence | Audience, a first-party corpus | Taxonomy studio, Layout Studio, delivery decks; no brief |
| Organization datasets | None; a domain layer instead | Saved dashboards, uploads, Google Sheets, the data assistant |
| Plus HR, finance, warehouse or panel layer | None | The layer's data pack: pages, measures and, for HR and warehouse, a brief reader |
"Lands on" is the starting point for a member whose role may open it, before an admin sets a default page.
What it reads and never reads
| Reads | Never reads |
|---|---|
| The pillars its own plugins turn on | A marketing metric in an organization without the marketing plugin |
| Its own declared datasets, scoped to the organization | Another organization's dataset, even under the same industry pack |
| Market estimates, labelled, inside their own hub | A market estimate as a KPI, a decision outcome or a brief fact |