Add a field or an object

A field is missing. In most tools that means a ticket, a prioritisation call, a release, and six weeks.

In Standards, you add it and it exists.

Two layers, two sets of rules

Your workspace has a foundation laid by your technical team: the structural objects and the fields that automations rely on. They are protected. You do not delete the field a procedure reads every morning.

On top of that sits what you add. Fields, objects, views. You create them, you change them, you delete them. They are yours.

That separation is what makes it possible to open up customisation without weakening the application.

The field types available

A field has a type, and the type decides what can go in it and how it displays.

• Text: a single line, or rich text with its formatting.
• Number: a number, or an amount with its currency.
• Choice: status, single select, multi select, checkbox.
• Time and place: date, address.
• Contact: phone, workspace member.
• Attachments: document.
• Links: a relation to another record, single or multiple.

A field can also be computed. A formula draws its value from the other fields on the record; a rollup draws it from the linked records, for example the total of a client's invoices. You do not type them in, they keep themselves up to date.

Saving is silent

There is no Save button, and no message comes to confirm that it worked. That is deliberate: the gesture is frequent, and a confirmation every time would turn into noise.

Before you add a field

Two questions save time later.

Is this really a field, or a relation? If the information points to something that exists elsewhere in your workspace, it is a relation. A company name typed by hand is only text.

Is this a value or a calculation? If the data follows from other fields, a computed field will keep it from drifting out of sync.