> ## Documentation Index
> Fetch the complete documentation index at: https://agents.concierca.ch/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Views

> Table views over your business data: filtering, columns, editing, and the visibility picker.

A **view** is a live table page over one of your data sources — customers, orders, leads, whatever your company tracks. Views appear in the sidebar's **DATA** section, and the same table engine also powers built-in surfaces like Knowledge, Decisions, and Runs, so everything in this chapter applies there too.

<Note>
  New here? [Your Data](/guide/data) is the plain-language map of every data domain — what each one holds and where its full reference lives.
</Note>

**Where:** Sidebar › **DATA** › *(your views)*. Each view lives at its own page.

## Views in the sidebar

* Each view shows with its own label and icon. Drag entries to reorder (your order is saved).
* Which views you see depends on your **departments**: a view can be assigned to specific departments (set by an admin under Settings › Departments › *Visible Data Tabs*); unassigned views are visible to everyone in the company. Admins see all views.
* **Delete a view** *(Company Admins)*: hover the entry and click the trash icon — this removes the view from navigation only; *"The underlying table is not touched."* Built-in foundation views cannot be deleted.

### Adding a view

Click the **＋** button at the bottom of the DATA section (*"Add view from database"* — creating views requires the Company Admin role):

1. **Add View from Database** — search all tables and views in your database, grouped by schema, each showing its column count.
2. **Configure** — set the Label, a Group (Views / Agents / Knowledge / Data / Reports / Custom), and pick an icon. Click **Add View**; columns are discovered automatically and the view appears in your sidebar.

## The table

Every view page shows the view name, row count, last-updated time, **stat cards** (Total plus automatic counts like Active/Success/Failed or per-category counts), and the table itself.

### Finding data

| Control            | What it does                                                                                                                                    |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Search**         | One search box across all searchable columns                                                                                                    |
| **Filter pills**   | One pill per filterable column — multi-select values (with search), min/max for numbers, a date-range calendar for dates. **Clear all** resets. |
| **Quick filters**  | Saved shortcuts defined for the view (when configured)                                                                                          |
| **Filter presets** | Auto pills like Success / Failed / Running / Pending / Error on status columns                                                                  |
| **Time filter**    | All time / Today / Yesterday / Last 3 / 7 / 30 days / Custom range                                                                              |
| **Scope tabs**     | On views with a status/department/category-style column, tabs above the table split rows by value, with counts                                  |
| **Group by**       | Group rows under expandable headers by any filterable column                                                                                    |
| **Sort**           | Click column headers (asc / desc / off)                                                                                                         |

### Shaping the table

* **Columns** button — show/hide columns.
* **Drag column headers** to reorder; **drag the header edge** to resize (60–800 px).
* All of it — widths, visibility, order, sorting, filters — is saved **per user per view** and restored next time. A **Reset** button restores the view's defaults.
* **View modes:** Table, **Cards** (auto-arranged record cards with their own sort dropdown), and **Kanban** (auto-pivoted on the status-like column). *Note: dragging kanban cards between columns is visual only — it does not change the data.*

### Selecting and exporting

* Row checkboxes + Select all. With a selection, a bar shows *"N selected"* and a **Copy** button (copies the selection as a Markdown table).
* **Export CSV** exports the currently filtered rows and visible columns.
* Pagination at the bottom: first/previous/next/last, with the row range and page indicator.

## Working with records

* **Add** (＋ in the page header) creates a record in a form dialog with the same layout as the detail view.
* **Click a row** to open the record detail popup with three tabs:
  * **Details** — fields grouped into Overview, Content, Configuration, and Metadata sections. Edit and **Save changes**.
  * **Linked** — related records. *Not yet available.*
  * **History** — on views with history enabled: every saved version with a field-level diff (before → after) and a **Restore** button per version.
* Long cell values truncate with a tooltip; IDs of related records display as names automatically.
* There is no row delete on generic views — records are managed by their owning surface (e.g. Memories has its own delete).

## "Who sees this?" — record visibility

On views whose records support scoping (e.g. Decisions), the detail and create dialogs show a **"Who sees this?"** selector at the top:

| Option                            | Meaning                                  |
| --------------------------------- | ---------------------------------------- |
| **Just me**                       | Only you (the record's owner) can see it |
| *A department*                    | Members of that department (and admins)  |
| **Company**                       | Everyone in your company                 |
| **Mandat** *(agency admins only)* | Visible at the agency/provider level     |

Two layers of visibility work together:

1. **View level** — which departments can open the view at all (admin-managed).
2. **Record level** — the "Who sees this?" scope on each record.

Admins see all records; everyone else sees company-wide records plus what is scoped to them. Agents obey the same rules — they read through their owner's eyes.

## Live views

The activity views (**Runs**, **Agent Inbox**, **Agent Decision Log**) auto-refresh every 5 seconds and show a green *"Auto-refreshing"* indicator. **Analytics** and **Cost** are dashboards rather than tables (see [Agent Activity](/guide/agent-activity)).

## Where the data comes from

A view reads either a real table/database view in your workspace database, or an imported dataset. Rows are always isolated to your company, then filtered by your departments and the record-level scopes above. External systems can push data in through **ingest endpoints** (admin-managed under Settings › Data Sources — see [Settings](/guide/settings)).

## What each view is for

**Your standard catalog.** Every new company starts with a ready-made set of views — nothing to build: the **Commerce** tables (Products, Orders, Order Line Items, Customers), the **Procurement** surfaces (Purchase Orders, Suppliers, Procurement Queue, Product Demand, and the related analytics — see [Purchasing & Procurement](/guide/procurement)), and the **governance** views (Strategy, SOP, and the agent activity surfaces). They are wired for ingest and agent access out of the box; your data fills them as it arrives.

The standard commerce/procurement views, each linked to its full field reference:

| View                                                         | What it's for                                                                             |
| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------- |
| [Orders](/api/data-model/orders)                             | E-commerce orders with payment and fulfillment status, Shopify-sourced                    |
| [Order Line Items](/api/data-model/order-line-items)         | Per-position line items of orders — read-only, linked to orders                           |
| [Customers](/api/data-model/customers)                       | Customer/contact records with lifecycle status                                            |
| [Products](/api/data-model/products)                         | Product master data: stock, prices, lead times, lifecycle, model families                 |
| [Suppliers](/api/data-model/suppliers)                       | Supplier master data: name, currency, lead time and target stock defaults                 |
| [Purchase Orders](/api/data-model/purchase-orders)           | Purchase order lines (header + line combined, Katana-compatible)                          |
| [Procurement Config](/api/data-model/procurement-config)     | Per-tenant procurement tuning: demand weights, cutoffs, seasonality                       |
| [Meeting Notes](/api/data-model/meeting-notes)               | Meeting notes + action items pushed in from external tools                                |
| [Product Demand](/api/data-model/product-demand)             | How fast each variant sells and how long the stock lasts                                  |
| [Procurement Queue](/api/data-model/procurement-queue)       | One procurement decision per tracked SKU — filter *Action Required* for the order list    |
| [Customer Reorder Due](/api/data-model/customer-reorder-due) | Repeat customers due for their next purchase — filter *Needs action* for the working list |
| [Family Trend](/api/data-model/family-trend)                 | Which model families are picking up and which are falling off                             |
| [Weekly Sales](/api/data-model/weekly-sales)                 | Units sold per product and calendar week                                                  |
| [Seasonality](/api/data-model/seasonality)                   | The seasonal factor per month, and where it comes from                                    |
| [Strategy](/api/data-model/strategy)                         | Company strategy documents (knowledge base, category = strategy)                          |
| [SOP](/api/data-model/sop)                                   | Standard operating procedures (knowledge base, category = sop)                            |

For the full plain-language map of every data domain — including the marketing, outreach, and knowledge domains — see [Your Data](/guide/data).

## Getting data in

Admins connect external systems under **Settings › Data Sources**: generate a scoped API key per table, point the external tool at `POST /api/ingest/<slug>`, and rows appear in the matching view — idempotently, so re-sending the same record updates instead of duplicating. Ready-made Make.com flow templates cover the Shopify tables. Full details in the [Ingest API](/api/ingest) reference.

## Permissions summary

| Action                              | Member                   | Company Admin      |
| ----------------------------------- | ------------------------ | ------------------ |
| Open views                          | Department-visible views | All views          |
| Add / edit records                  | ✔                        | ✔                  |
| See all records regardless of scope | —                        | ✔                  |
| Create a view / delete a view       | —                        | ✔                  |
| Assign views to departments         | —                        | ✔                  |
| Set record visibility to "Mandat"   | —                        | agency admins only |