A structured process, built from Stages and Actions, that a record moves through to represent its status in a business process, such as a sales pipeline.

on a Collection

Collection

A container for records in Kinabase, similar to a table in a spreadsheet or database, used to organise one type of data such as Projects or Contacts.

: enabling it, defining the Stages

Stage

A step within a Workflow that shows a record's current status, displayed as a coloured badge on the record.

records pass through, and creating the Actions that move a record from one stage to the next. For what a workflow is and when to use one, start with Workflows.

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

1. Enable the workflow

1. Open the collection's configuration

In the sidebar, right-click the collection and select Configure (or open the collection and use the options menu (⋯) at the top-right). Open the Workflow pane, under Setup.

2. Turn on stages

Turn on Enable workflow stages for this collection. The Stages and Actions section appears, ready for you to build your process.

2. Define your stages

Each stage is one phase of your process. Every collection starts with a single default stage, which you can rename.

1. Add a stage

Click Add Stage and give it a clear, action-oriented name - for example Submitted, In Review, Approved, Paid.

2. Give it a colour

Choose a colour for the stage. This is the badge colour shown on records and in lists, so pick colours that make progress easy to read at a glance.

3. Repeat for every phase

Add a stage for each phase of your process. Records will always sit at exactly one stage.

The first stage carries a Default badge - every new record starts here, and this stage cannot be deleted.

3. Create actions to move records between stages

An Action is the button a user clicks to move a record to another stage. Without actions, a record has no way to progress.

1. Add an action to a stage

Within a stage, click to add an action and choose the target stage it moves records to.

2. Name and colour it

On the General tab, set the action's Label (for example Approve, Reject, Send to Production) and its Colour. The label and colour are what users see on the button.

3. Add more actions where a stage can branch

If a stage can progress in more than one direction, add an action for each route - for example an Approve action and a Request Revision action on the same In Review stage.

Action tabs in depth

Editing an action gives you tabs for the finer detail:

General - the label, form title, colour, and whether the action opens a guided multi-page form.
Permissions - who is allowed to perform this action (see section 5).
Fields - the fields a user updates when performing the action, plus any additional fields captured only for this transition (these are logged as an activity).
Lists - collection-list items (such as line items) a user can add while performing the action.
Signatures - whether a signature is required before the action can complete, and from whom.
Validation - rules that must pass first. A warning shows a message but still allows the change; an error blocks it.
Notifications - whether a Notification
Notification
A message from Kinabase that alerts you to events such as a task being assigned, a due date approaching, or an Automation completing, delivered in-app, by email or as a desktop notification.
is sent when the action runs, and to whom. This creates a Stage Change automation behind the scenes - see Automations.

4. How a stage change works for users

When a user clicks an action on a record's Details tab, Kinabase opens a confirmation before anything changes.

The confirmation asks the user to confirm the move (for example, "Are you sure you want to change this record to Approved?"). If the action requires extra fields, signatures, or list items, the user completes those here first. Where the action will set off automations, the confirmation previews how many will run.

Actions are filtered by permission, so a user only sees the buttons they're allowed to use. When a stage has three or more available actions, they collapse into a Next Stage dropdown to keep the record tidy.

Some transitions can be marked as irreversible; the confirmation then warns that the change cannot be undone.

5. Set per-stage permissions

By default, who can view and edit a record does not depend on its stage. When you need that to change - for example, locking a record once it reaches Approved - use per-stage permissions.

Permissions are configured in the collection's Permissions pane, under Security. You'll need Configure permission for the collection.

1. Open the Permissions pane

In the collection's configuration, open Permissions. Alongside the Default tab you'll see one tab per stage.

2. Override a stage

Open a stage's tab and turn on Custom permissions. The stage now uses the record permissions you set here instead of the Default ones, but only for records currently at that stage.

For a full explanation of roles and permission levels, see Assign Roles and Permissions.

6. See stages on records and in views

Once configured, the current stage shows as a coloured badge on each record and as a column in your tables.

To review a collection stage by stage, open the list and select Group by → Stage. Records cluster under their current stage, giving you a stage-by-stage breakdown you can scan quickly.

Grouping by stage is not a board or kanban view - Kinabase has no such view. It groups records within the Table and Side by side views. See Views.

Guided multi-page forms for a stage change

When a stage change needs several fields, list entries, or signatures, turn the action into a guided multi-page form so users complete it step by step.

Edit the action and, on its General tab, turn on Use multi-page form, then open the form layout editor.
Click Add Page and give each page a title and, optionally, an icon and instructions.
On each page, assign the record fields, additional fields, and lists you want completed there. Fields must first be selected on the action's Fields tab before they appear here.
Save the action. Any enabled field not yet placed on a page is flagged, and empty pages are removed automatically.

When a user performs the action, the form opens as a pop-up with a sidebar listing every page. A validation summary flags issues across all pages with links straight to the field, and progress is saved automatically to the browser in case the page is refreshed. In a Portal

Portal

A secure, branded web interface, separate from the main app, that shares a filtered view of your Kinabase data with internal colleagues or external collaborators.

, the same form opens full-screen with a progress bar, optimised for mobile.

7. Best practices

Start with the essentials

Define your core stages and actions first, then layer on validation, signatures and notifications as your process matures.

Test with a real record

Run a record through every stage to confirm each action, permission and validation rule behaves as you expect.

Check who can transition

Review action permissions regularly so only authorised colleagues can perform critical transitions such as approvals.

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

PreviousWorkflows

Next Automations