Kinabase Logo
Help & Support

Configuring Fields

Create, edit and organise the fields in your collections


Fields

are the foundation of every collection - each one holds a single piece of information about a record . You add and manage fields from the Fields pane of a collection's configuration, where you can create new fields, tidy up outdated ones, and fine-tune how each field behaves. This guide covers the everyday tasks, including checking where a field is used before you change or delete it. The deeper options each have their own guide, linked as you go.

You'll need Configure permission

for a collection to change its fields. If you're unsure, ask your System admin.


1. Open the Fields pane

1. Open the collection

Select the collection from the sidebar.

2. Go to Configure

Click the options menu (⋯) in the top-right corner and select Configure, or right-click the collection name in the sidebar and choose Configure.

3. Select Fields

Under Setup, click Fields to see all of the collection's existing fields.

The Fields pane in a collection's configuration, listing its existing fields

2. Create a field

1. Click Add field

At the top of the Fields pane, click Add field.

2. Name the field and pick a type

Enter a Name (for example, Status or Budget), then select a Type. Kinabase suggests a type based on the name - accept it, or select another from the picker. For the full list of types and what each one stores, see Field types.

Field names can't contain », because CSV exports use it to separate a field from its parts, such as Address » City. A name that already contains it is kept until you rename the field.

To link to another collection, scroll to your other collections in the Type picker and choose one - this creates a Linked Collection Field

. See Linked collection fields.

3. Add the field

Click Add to confirm. The new field appears in the Fields pane.

Adding a new field with a name and type

3. The Field Editor

Every field opens in the Field Editor, whether you're adding or editing it. The header holds the Name and Type; below it, a set of tabs groups the options for that field. Which tabs appear depends on the field type.

TabWhat it controls
OptionsThe choices in a Select, Multi-Select or Computed (Select) field, and how they're entered.
DisplayHow the field looks in record views - for example a Select field as a Badge, Text or Progress bar.
DetailsThe Description, the Default Value, and per-type settings (such as currency, precision, a Website field's Preview Card or Simple Link display, a Probability field's Colour Scale, a Phone Number field's Default Dialling Code, a Rich Text field's Plain Text Export, or whether a Person Name shows a title).
FormattingConditional colour rules and number formatting. See Validation and formatting.
InputHow data is entered - for example Use QR Code Scanning on a link field, or an Image Thumbnail for a linked record.
PermissionsField-level Read and Write permissions. See Validation and formatting.
ValidationRules such as Required, Unique and numeric limits. See Validation and formatting.

When you first add a field you see a compact form. Expand it to reveal all of the tabs above.


4. Add a description

A clear description helps your team understand what a field is for - especially Computed Field

, Lookup Field and Aggregation Field types, whose behaviour isn't obvious from the name.

1. Open the Details tab

Edit the field and go to the Details tab.

2. Write, or generate, a description

Type into the Description box, or click the bolt button to Generate description with AI. Kinabase reads the field's configuration and writes a plain-language explanation for you to review and save.

The Generate description with AI button appears only once a collection has been saved. If you're setting up a brand-new collection, save it first. AI features aren't available on the Starter plan - see AI in Kinabase.


5. Set default values

A default value pre-fills a field whenever someone adds a record, saving repeated typing and keeping data consistent.

1. Open the Details tab

Edit the field and go to the Details tab.

2. Enter a default

Enter the value to use - for example Open for a Status field. The available options depend on the field type:

  • Yes / No fields offer Yes, No or Formula.
  • Colleague fields offer Blank or Current User.
  • Date and Date + Time fields can offset from the current moment using Now + Offset (for example, a due date three days from creation).
  • Probability fields start at 50% when you turn on Enable Default Value, and you can change it from there.

Formula defaults

Instead of a fixed value, choose Formula as the default and write an Expression

. The field is then pre-filled with the calculated result each time a record is added - useful for defaults that depend on other fields or the current date. Unlike a computed field, a formula default is only a starting point: users can edit the value afterwards. For the formula syntax, see Computed fields.

Setting a default value on the Details tab

6. Set a probability colour scale

A Probability field stores a likelihood from 0% to 100%. Its Colour Scale decides which end is the better outcome, so a high chance of winning a deal and a high risk of a defect don't have to share the same colour. Green marks the better end and red the worse end.

The labels always describe likelihood, whichever way round the colours go:

PercentageLabel
0%Impossible
1–24%Very unlikely
25–49%Unlikely
50–74%Likely
75–99%Very likely
100%Certain

1. Open the field

Go to Configure → Setup → Fields. Click Add field, or open an existing field's options menu (⋯) and select Edit. Set Type to Probability.

2. Set Colour Scale

On the Details tab, under Colour Scale, select Higher is better or Lower is better.

Higher is better is used for a new Probability field, and for any existing Probability field until you change it.

3. Save the field

Click Add for a new field, or Save for an existing one.

Where the colour scale appears

The same scale is used wherever the value appears:

  • Editing a record - a slider that moves in steps of 5, the percentage and the label. You can also type a percentage from 0 to 100.
  • On the record - a coloured dot, the percentage and the label. An empty value shows Not set.
  • In a table - a coloured dot and the percentage. An empty value leaves the cell blank.
  • On a Kanban card - the field name, the dot and the percentage, without the label. See Using Kanban Views.

7. Set a default dialling code

A Phone Number field stores a dialling code, the local number and an optional extension. Its Default Dialling Code is the code that a new number starts with - in the app, in a portal

and on a shared form - and the code given to numbers that arrive without one from a CSV import or the API.

You'll need Configure permission for this collection. If you're unsure, ask your System admin.

1. Open the field

Go to Configure → Setup → Fields. Add a Phone Number field, or open an existing phone field's options menu (⋯) and select Edit.

2. Set Default Dialling Code

On the Details tab, select a Default Dialling Code, then click Add for a new field or Save for an existing one. Leave it blank to use your organisation's code instead.

3. Check the Code box

Add or edit a record and type the local number. The Code box shows the dialling code - select another code if this number is for a different country. Numbers that are already saved keep their code until someone edits them.

When Default Dialling Code is blank

In the app and in a portal, Kinabase uses the first of these that gives a code:

  1. Your organisation's Country, under Settings → Organisation → Organisation Details.
  2. The dialling code of your organisation's Phone Number.
  3. The location of the person entering the number, from their device's time zone or browser language.

A shared form has no organisation details, so it uses the visitor's location. A CSV import falls back to +44 if nothing else gives a code, and so does the API, which skips the location step.

A code already written in the number, such as +33 or 0033, is always kept.


8. Export rich text as plain text

In a CSV export, a Rich Text field's column keeps its formatting, which is hard to read in a spreadsheet. Turn on Plain Text Export to add a second column with the same wording as plain text. The plain text column exists only in the file - the field on the record is unchanged.

You'll need Configure permission for this collection. If you're unsure, ask your System admin.

1. Open the field

Go to Configure → Setup → Fields. Add a Rich Text field, or open an existing rich text field's options menu (⋯) and select Edit.

2. Tick the export option

On the Details tab, under Plain Text Export, tick Include a plain text column in CSV exports, then click Add for a new field or Save for an existing one.

3. Export the collection

Open the collection's options menu (⋯) and select Export (.csv). Whenever the field is part of an export, the plain text column sits beside it, headed with the field name, such as Notes » Plain text. Paragraphs, bullets and numbered lists are laid out on their own lines.

A lookup of the field includes the plain text column too. When you import the file back, leave the plain text column on Ignore - it's the default - so the formatted column is what's written to the record. See How CSV columns are named.

Read our Product Update for more.


9. Reorder fields

Fields appear on records in the order they're listed in the Fields pane.

  • Hover over the drag handle to the left of a field and move it up or down, or
  • Click the field's options menu (⋯) and choose Move Up or Move Down.
Editing, moving and deleting a field from its menu

10. Set the primary and secondary fields

Every collection has a Primary Field - the field used as each record's title - and an optional Secondary Field shown alongside it for context.

1. Find the primary and secondary settings

At the top of the Fields pane, locate Primary Field and Secondary Field.

2. Select your fields

Select a field from each dropdown, then click Update. The primary field is required; the secondary field is optional. Click Undo to discard a selection you have not updated yet.

Choosing the primary and secondary fields for a collection

A field set as the Primary Field can't be deleted, and can't have its Unique Identifier

settings turned off while it's the primary. See Adding unique identifiers.

Changing the Primary Field or Secondary Field refreshes the name already shown on records that link to this collection. See Linked collection fields.


11. Check where a field is used

A field is often read outside its own collection - in a Filter

, a formula, an Automation , a Form , a Report , a Document Template or a portal. Check usage lists those places before you change or delete the field.

1. Open Check usage

Click the field's options menu (⋯) and select Check usage. For a Collection List

, open the parent collection's Lists pane, click Edit on the list and use the options menu (⋯) on its Fields tab.

2. Review each place

The Usage of window groups the places by kind, such as Views, Reports, Automations or Forms. Select a group to see how each place uses the field. Click the arrow to open a place in a new tab, update it, then click Refresh.

Kinabase names only the places you can configure. Places you can't access are counted instead - ask a colleague who can configure them.

What Check usage leaves out

A column on a View

is listed only when it's that view's only column. A column among others, the field's place in a field group, and record type settings for the field go with the field when it's deleted, so they aren't listed.

Read our Product Update for more.


12. Delete a field

Click the field's options menu (⋯) and select Delete. The confirmation says whether any records hold a value in the field. Deleting a field is permanent and erases all of its data across every record.

If the field is still used somewhere that would break, such as a chart, a filter, a formula, a form, an automation or a portal, the confirmation lists those places and Delete stays unavailable. Remove each use, then click Check again. Worth a look first lists uses that don't stop the delete, such as a view whose only column is this field.

Delete isn't offered for the Primary Field, the Sort Field, the stage field, the type field, or the field that links a list or child collection to its parent. Reassign the primary or sort field first (see step 10). A field filled by a connector or managed by an extension can't be deleted either - the confirmation explains what to change.

The same confirmation appears when you change a record ID format - see Adding unique identifiers.


13. Tips

  • Create only the fields you'll actually use - you can always add more later.
  • Mark critical data as Required so records can't be saved without it. See Validation and formatting.
  • Use AI-generated descriptions to document your computed, lookup and aggregation fields for the rest of the team.
  • Remove outdated fields so they don't clutter your records.

Need more help? Ask your System admin, or contact our support team via Help & Support.