# Creating records

Source: /ux/product-and-ui/creating-records.md

- Summary: Create from a button where the need arises, or from an embedded list on the parent's detail, with one primary action.
- Status: Adopted, since 2026-10-02
- Principles: Fewest steps, Fewest inputs, One way
- Surfaces: Screen, Form

## When to use

Use it whenever an interface page or screen lets the person add a record.

## When not to use

Intake steps add rows inside grid views on the table, covered in [intake views](/ux/product-and-ui/intake-views.md). An interface never gets a step page.

## How it works

### Open the form from the page where the need arises

Creation goes through a form opened by a button on the page where the person needs the new record. The form is built by hand, because the MCP cannot build it, and is listed in the handover.

Pass: every form opens from a button on a page that lists the rows it creates, in 1 click.

### Add child records from the parent's detail

On the parent's detail, an embedded list with "Allow adding records" turned on creates the child and prefills the link.

Pass: no child record form has a field for the parent the person came from.

### Land on the record the form created

After the form, the person lands on the new record, so they see it worked.

Pass: after submitting the form, the next screen is the new record, with 0 extra clicks.

### Show one primary action per page or area

A page or area has one primary button, the action the person most often takes there.

Pass: every page or area has exactly 1 primary button.

The footer of a creation form.

Do: One primary Create project button.

Don't: Create project and Save draft both styled as primary.

## Research

Atlassian's button page says: "Only include one primary button or call to action (CTA) in a page or area."

The button and the embedded list come from the interface skill's page kit, without an outside source so far.

### Sources

- [Atlassian Design System, Button usage](https://atlassian.design/components/button/usage)