Glossary

A repository for similar data families (e.g. all materials, all production data).

A repository inside a Schema for records containing similar information.

A table allowlisted on another table so its columns can attach as related children or Grid linked columns. Tab: Linked tables. CTA: Add linked table. Picker: Linked table. Do not say “partner table.” A record link is an instance between two records, not this allowlist.

A single data item (row) inside a Table. Contains values for the Fields defined on that Table.

A specific piece of data on a Record (column). Has a data type (text, number, range, tabular, etc.).

Nested matrix of columns on a field. User-facing type name. Internal dataType may stay “table”. Add column uses one Dialog drill-in (never a second modal).

Fields-tab section: demo grid of the selected View. Label the picker View; the system view name is Default. Do not say Default View. Not the Parser title — create is Parser, a run after Upload file is This file.

Visible label on the Fields view menu. The Default chip means this grid view is the default — not the section title.

Catalog of fields to check onto the Preview. Do not say All available fields.

Visible label on the Fields catalog source Select. First value: This table. Then each linked-table instance name. Do not leave it unlabeled.

Visible label on the Fields catalog search (pairs with Fields from). Do not leave the catalog search unlabeled.

The actual values stored in Fields across Records in Tables.

The data modeling and exploration area (Domains, Tables, Projects, Datasets).

Workflow and automation area (All Flows, My Flows, Form Builder, Parsers).

Insights, analytics and decision support area. Product mark is AiMark (MDMi i-triangle) — never AutoAwesome. Pulse is not in the left nav.

A curated set of Records, usually for a specific analysis or workflow.

Individual record creation/editing via a form (see Form Builder).

A run: collect or transform records through steps. Nav: All Flows / My Flows. CTA: Start flow. Routes stay /flows. Do not say “data task” in the UI.

Admin blueprint a flow follows (forms, parsers, reviews). Nav/H5: Flow templates. Do not call this a “data task template.”

Retired product noun. Use Parser. Do not say File importer or PDF parser in the UI.

Reusable map from a file (PDF, CSV, instrument output, …) onto table fields. List: Parsers. Heading: Parser. Field: Parser name. CTA: New parser. Attach Parser · Open parser. Create primary: Save. Review of a run uses heading This file (not Preview). Format is a property. Parse is the verb.

Extracting structured data from files (PDF, Excel, CSV, etc.) to create Records.

Apply the same simple fields to every checked row on a Studio record table. Drawer: Edit selected records. Empty field = leave unchanged. Hide without write permission. Do not say “batch edit.”

Global: platform seats and domain/table grants. Admin only. Not the table tab. Seats: Admin · Curator · Contributor · Collaborator · Viewer. Never Stakeholder as a seat.

Read-only platform seat. Browse permitted data; no form or flow input. Hide Edit selected and other write CTAs. Stored key may stay guest. Never Stakeholder.

Share list on a table or project — people on this object. Existing user | Invite by email. Admin and Curator managers. Two paths to the same outcome (this tab, or Users & Access). Cross-link; do not merge the screens.

Can view/consume information on a Table.

Can consume + create/edit/delete data and records on a Table.

Can do Author actions + modify the table schema/structure.

Full access including creating new tables/databases.

Filtering the same content set along multiple independent dimensions so users can combine criteria freely (status + domain + assignee, etc.).

Cues that answer 'Where am I?', 'Where can I go?', and 'Did I arrive?': breadcrumbs, active sidebar states, page titles, and consistent landmarks.

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.

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.

Revealing complexity only when needed: summary cards and lists first, full details and editors on demand (drawers, expanders, modals).

Flexible, Accountable, Discoverable, Empower.

A high-level grouping (e.g. Material master). Contains Tables.

An individual piece of data stored in a Table (e.g. name, quantity, status).

A saved query or presentation of Records, often with filters, sorting, and columns.

A defined sequence of steps or states that a Record or process moves through (e.g. approval flow).

An actionable item assigned to a user or team, often part of a Workflow.

A log entry capturing an action taken on a Record, View, or Project (who, what, when).

A rule applied to a Table or View to narrow the set of visible Records.

The current state of a Record or process (Active, Pending, Blocked, etc.).

A message sent to users about events, mentions, or required actions.

A collection of views, KPIs, and activity feeds for at-a-glance monitoring.

A generated or saved output of data analysis, often exportable.

A set of permissions assigned to Users or Teams.

Specific access rights (view, edit, delete, approve) granted via Roles.

Immutable history of all changes and actions for compliance and traceability.

The living library of patterns used across the platform (inputs, flows, states, etc.).

The structure and organization of content and data across Schemas, Domains, and navigation.

The system of classification and naming used for Domains, labels, and categories.

A defined condition of a Record or Workflow (e.g. Draft, Submitted, Approved).

The move from one State to another, often triggered by an action or condition.

Specific Field Types, statuses, etc. will be expanded in future versions. See UP_NEXT.md in source.