Looking for the interactive hierarchy diagram? Data Model Relationships now lives under Product Design → Information Architecture. Term definitions stay here.

Database Concepts

Schema
A repository for similar data families (e.g. all materials, all production data).
Table
A repository inside a Schema for records containing similar information.
Record
A single data item (row) inside a Table. Contains values for the Fields defined on that Table.
Field
A specific piece of data on a Record (column). Has a data type (text, number, range, tabular, etc.).
Data
The actual values stored in Fields across Records in Tables.

Navigation & Major Sections

N2 Studio
The data modeling and exploration area (Domains, Tables, Projects, Datasets).
N2 Flow
Workflow and automation area (All data tasks, My data tasks, Form Builder, Parsers).
N2 Intelligence
Insights, analytics and decision support area.
Dataset
A curated set of Records, usually for a specific analysis or workflow.

Data Input & Workflows

Form
Individual record creation/editing via a form (see Form Builder).
Data task
A run: collect or transform records through steps. Nav: All data tasks / My data tasks. CTA: Start data task. Routes stay /flows.
Flow template
Admin blueprint a data task follows (forms, parsers, reviews). Do not call this a “data task template.”
Parse
Extracting structured data from files (PDF, Excel, CSV, etc.) to create Records.

Access & Roles (from Definitions.pdf)

Consumer
Can view/consume information on a Table.
Author
Can consume + create/edit/delete data and records on a Table.
Configure
Can do Author actions + modify the table schema/structure.
Administrator
Full access including creating new tables/databases.

Information Architecture Concepts

Faceted Navigation
Filtering the same content set along multiple independent dimensions so users can combine criteria freely (status + domain + assignee, etc.).
Wayfinding
Cues that answer 'Where am I?', 'Where can I go?', and 'Did I arrive?': breadcrumbs, active sidebar states, page titles, and consistent landmarks.
Polyhierarchy
The same content (Records) legitimately appearing in multiple groupings — e.g. a Record lives in one Table but can be collected into several user Projects.
Mental Model
The user's internal picture of how the system works. N2 uses domain-familiar language and flows (not org-chart hierarchies) so materials experts feel at home.
Progressive Disclosure
Revealing complexity only when needed: summary cards and lists first, full details and editors on demand (drawers, expanders, modals).

Core Concepts

Tenets
Flexible, Accountable, Discoverable, Empower.
Domain
A high-level grouping (e.g. Material master). Contains Tables.
Field / Attribute
An individual piece of data stored in a Table (e.g. name, quantity, status).
View
A saved query or presentation of Records, often with filters, sorting, and columns.
Workflow
A defined sequence of steps or states that a Record or process moves through (e.g. approval flow).
Task
An actionable item assigned to a user or team, often part of a Workflow.
Activity
A log entry capturing an action taken on a Record, View, or Project (who, what, when).
Filter
A rule applied to a Table or View to narrow the set of visible Records.
Status
The current state of a Record or process (Active, Pending, Blocked, etc.).
Notification
A message sent to users about events, mentions, or required actions.
Dashboard
A collection of views, KPIs, and activity feeds for at-a-glance monitoring.
Report
A generated or saved output of data analysis, often exportable.
Role
A set of permissions assigned to Users or Teams.
Permission
Specific access rights (view, edit, delete, approve) granted via Roles.
Audit Log
Immutable history of all changes and actions for compliance and traceability.
UX Patterns
The living library of patterns used across the platform (inputs, flows, states, etc.).
Information Architecture (IA)
The structure and organization of content and data across Schemas, Domains, and navigation.
Taxonomy
The system of classification and naming used for Domains, labels, and categories.
State
A defined condition of a Record or Workflow (e.g. Draft, Submitted, Approved).
Transition
The move from one State to another, often triggered by an action or condition.
More detailed terms
Specific Field Types, statuses, etc. will be expanded in future versions. See UP_NEXT.md in source.

Ported from N2 UX pattern library + Definitions.pdf. Grouped by source categories. Searchable. Data model diagram: Product Design → IA.