Fields FieldA column in a Collection that stores a specific type of information for each Record, such as text, number, or date.
are the building blocks of your data - like columns in a database or form inputs.
Each Field Type helps you capture and store information in the right format, making your collections CollectionA list of records in Kinabase, similar to a table in a spreadsheet or database.
accurate, relevant and easy to use.
When creating a new field, Kinabase will suggest a field type based on the name you give it.
Think first about the type of data you want to store - freeform text, numbers, dates, files, etc. - and how you need to interact with it.
For example,
- if you just need to type in any text, use a Text field;
- if you need a numeric value (like currency or ratings), go for Numeric fields;
- for dates or durations, use Date & Time fields; if you’re uploading documents or images, pick File fields;
- if it’s about choosing from a list, use Choice fields; and so on.
If you want data that’s automatically calculated, or pulled from another collection, look at Computed or Collections fields.
By matching the data’s purpose with these categories, you’ll quickly land on the right field for the job.
Allow free-form text input, with optional rich formatting and specialised text formats (e.g., emails, websites).
Field Type | Description | Examples |
---|
Text | A simple text input where you can write any characters, numbers, and spaces. | John Doe, example text, hello world |
Rich Text | A text input where you can add formatting like bold, italics, underline, and bullet points. | Rich Text Example, Rich Italic |
Email Address | An input specifically for email addresses, allowing one-click to send an email. | john.doe@example.com, jane@example.co |
Website | An input specifically for website URLs, automatically adding a hyperlink. | https://www.example.com, www.example.org |
Phone Number | An input specifically for phone numbers (also appears under Numeric). | +1-555-1234, (123) 456-7890, +44 07343012 #123 |
Computed (Text) | Dynamically generated text using other fields in the record RecordAn individual entry within a Collection, like a row in a database table, representing one item or entity. (concatenation, etc.). | e.g. Invoice#{Order_ID} |
Store numeric values (including currency, rating, percentages) and optionally calculate them automatically.
Field Type | Description | Examples |
---|
Number | A numeric input that accepts only numbers (decimals or integers). | 42, 3.14, -10 |
Rating | A rating input for whole numbers; can be shown as stars, slider, or radio buttons (also appears under Choice). | 2, 10, 0 |
Percentage | A numeric input representing a percentage (not strictly limited to 0–100%). | 99%, 50%, 1%, 120% |
Probability | A numeric input for likelihood of an event, often expressed as a percentage. | 100% (Certain), 50% |
Currency | A numeric input representing money or monetary values. | £100, $250, €1,000 |
Phone Number | An input for phone numbers. Listed here if your system allows storing them numerically (also in Text). | +1-555-1234, +44 7331 |
Computed (Number) | A number that is calculated from other fields (using a formula). | e.g. sum(Quantity × Price) |
Record physical or scientific quantities (e.g., length, weight, volume) with associated units.
Field Type | Description | Examples |
---|
Length | A numeric input for length (e.g., meters, km, mm). | 1.5m, 2.5km |
Distance (mileage) | A numeric input for distance in miles. | 1.5mi, 500mi |
Area | A numeric input for area (e.g., m², km², ha). | 3m², 33ha |
Volume | A numeric input for volume (e.g., liters, cubic meters). | 1.5m³, 3L |
Weight | A numeric input for weight/mass (e.g., kg, lb). | 1.5kg, 340kg |
Duration | A numeric input representing a length of time in hours/minutes (also appears in Date & Time). | 1h 45m, 30m |
Scientific Time | A numeric input for time intervals in seconds, milliseconds, etc. | 1.5s, 2ms |
Data | A numeric input representing a data size (e.g., bytes, KB, MB, GB). | 1.5MB, 2GB |
Angle | A numeric input for angles, in degrees. | 45°, 180°, 360° |
Current | A numeric input for electric current, in amps. | 1.5A, 2.3mA |
Voltage | A numeric input for electric voltage, in volts. | 4.5V, 255kV |
Charge | A numeric input for electric charge, in coulombs. | 1.5C, 20µC |
Energy | A numeric input for energy, in joules. | 1.5J, 20kJ |
Power | A numeric input for power, in watts. | 1.5W, 2.3kW |
Resistance | A numeric input for electrical resistance, in ohms. | 333Ω, 1kΩ |
Capacitance | A numeric input for electrical capacitance, in farads. | 1.5F, 2.3mF |
Inductance | A numeric input for electrical inductance, in henrys. | 1.5H, 2.3mH |
Frequency | A numeric input for frequency, in hertz (Hz). | 1.5Hz, 2.3kHz |
Capture specific dates, times, or date ranges for scheduling or historical references.
Field Type | Description | Examples |
---|
Date | A date input with a calendar picker. | 20/12/2020, 04/07/2021, 31/10/1995 |
Date + Time | A combined date/time input with a calendar and time picker. | 20/12/2020 14:30, 04/07/2021 09:15 |
Month | A date field restricted to just month and year. | December 2020, July 2021 |
Year | A date field restricted to just the year. | 1857, 2021, 1985 |
Duration | Time in days/hours/minutes, used for billing or scheduling (also appears in Measurements). | 1 hour 45 min, 30 minutes |
Date Range | Two date/time inputs indicating a start and end time (time span). | 20/12/2020 14:30 to 04/07/2021 09:15 |
Store geographical or address information, often integrated with maps.
Field Type | Description | Examples |
---|
Location | An input for geographic or physical addresses (maps, lat/long). | 1600 Pennsylvania Ave NW, Washington DC, 1600 Amphitheatre Pkwy, etc. |
Provide predefined lists of options (single or multiple) for consistent, categorical data entry.
Field Type | Description | Examples |
---|
Yes / No | A true/false or binary toggle. | True, False, Yes, No |
Select | A dropdown menu to choose one option from a predetermined list. | To Do → Doing → Done |
Multi-Select | A dropdown menu to choose multiple options from a predetermined list. | Red, Blue, Green |
Rating | A rating input for whole numbers; can be stars, sliders, or radio buttons (also appears under Numeric). | 2, 10, 0 |

Link records to one or multiple users or colleagues ColleagueA team member who has full access to a Kinabase workspace and its settings.
within your organisation.
Field Type | Description | Examples |
---|
Colleague | A single user in your system (link to the colleague record). | John Doe, Jane Smith, Bob Johnson |
Colleagues | A list of users (links to multiple colleague records). | John, Jane, Bob (multiple selections) |
Upload and manage files or images, either singly or in bulk.
Field Type | Description | Examples |
---|
File | A single file upload (document, image, spreadsheet, etc.). | example.docx, image.png, spreadsheet.xlsx |
Image | A single image upload (with optional device camera capture). | photo.jpg |
Files | Multiple files can be uploaded. | example.docx, image.png, spreadsheet.xlsx |
Images | Multiple images can be uploaded. | photo1.jpg, photo2.png |
Represent and calculate risk scores or compliance metrics.
Field Type | Description | Examples |
---|
Risk Score | A risk score calculated from likelihood/impact (or other formula) to gauge risk severity. | Low, Medium, High, Critical |
Dynamically generate or aggregate values from other fields, including text, numeric, or date data.
Field Type | Description | Examples / Notes |
---|
Computed (Text) | Text automatically generated from other fields (string concatenation, templates, etc.). | Full Name = First Name + " " + Last Name |
Computed (Number) | A numeric field automatically calculated from other fields (formula). | Subtotal = Quantity × Unit Price |
Computed (Date) | A date/time field automatically calculated based on other fields. | Expiry Date = Start Date + 30 Days |
Computed (Select) | An option field selected based on logic or formula. | Status = if(Score >= 80, "High", "Low") |
Lookup | Copies values from a related record in a different collection (linked collection). | “Customer Email” field pulled from a Customer record. |
Aggregation | A numeric or statistical result derived from multiple related records in a linked collection (e.g., sum). | Order Total = SUM(All Items' Price) |
Aggregation (Date) | The earliest or latest date from related records in a linked collection. | “Most recent event date” across multiple child records. |
To learn more about Computed Fields Computed FieldA Field whose value is automatically calculated by a formula or expression rather than entered manually.
, check out the Computed Fields section.
Reference data from linked collections, enabling lookups and aggregations across related records.
Field Type | Description | Examples |
---|
Linked Collection Fields (various) | Special fields generated based on which other collections are linked. They allow referencing other data. | E.g., referencing “Projects” from a Task. |
Linking collections is very powerful, meaning that you can connect your records easily & only have to put in that piece of information once!
To learn more please read our Linked Collections section.
With the right Field Types, you'll make sure each record in Kinabase stores data efficiently and precisely.
It'll pave the way for strong, flexible collections that match your unique business needs.