On this page
The workspace for researching customer discussion: one customer's own classification vocabulary, an approved corpus and the decks delivered to that customer.
Configured with the Content Intelligence blueprint, a research organization dedicated to one customer; it refuses an organization already running a marketplace connection. Data enters only through upload and mapping; Connectors, Data Pipeline, Dashboard, Explore and the decision loop are hidden for every role.
Landing page: automatic. With no Home, Marketing Performance or Market page, it opens your first openable dashboard in sidebar order, never the saved-dashboards list. Owner or Admin can change the landing page in Settings > Organization, and per brand in Settings > Brands (how the landing page is chosen).
Who can do this: every role reads its reports; Admin and Editor set up and load data, as the tables below show.
Before you start#
- The organization has this type, chosen by a super admin when it is created (Organization types).
What you get#
| Area | Pages | Who |
|---|---|---|
| Conversation taxonomy | The customer's content-group vocabulary: confirm a value, merge an alias, write a customer-facing definition | Every role; edits: Editor and up |
| Saved views | The delivered decks, such as the content group glossary, conversation overview, drill-down and evidence pages | Every role |
| Layout studio | Author a deck's layout, board by board | Owner, Admin |
| Upload data, CSV/Excel mapping | How a discussion corpus enters, and the column mapping reused per source | Editor and up |
Editor also holds organization settings here, so upload, mapping, taxonomy and deck run without an admin. A deck exports PDF whole or by page; a table in it exports CSV or Excel. Question-and-answer attaches to each deck over its own data; there is no organization-wide assistant or morning brief.
Steps#
- Day 1 (Super admin): create a dedicated organization for the research project.
- Day 1 (Editor): upload the first discussion corpus in Upload data and confirm its column mapping (Upload CSV or Excel files).
- Day 2 (Editor): build the vocabulary in Conversation taxonomy: confirm values, merge aliases, name them for the customer.
- Day 3 (Admin): pick a deck template and adjust its boards in Layout studio, then write the narrative.
- Week 1 (Editor): preview the deck through its share link, export the PDF and compare it with the on-screen version before sending.
If it fails#
| Symptom | Cause | Fix |
|---|---|---|
| The blueprint will not apply | The organization already runs a marketplace connection | Use a dedicated organization for the research project |
| No Connectors item | This organization type hides the connector plane by design | Data enters through upload and mapping |
| A content group shows a technical name | The vocabulary value has no display name yet | Name it in Conversation taxonomy |
| PDF differs from the on-screen version | The layout changed after the export | Finish the layout in Layout studio, export again |