The User column type allows you to select a Budibase user from a dropdown list as determined by the Application access. This list will include all admins of the tenant, and any members of the app.

Toggle Allow multiple users on to make the list a multi-select.

User column type

Adding a User column type

With the user column added, you can now click the + within your data grid view to select a user as identified by their searchable email address.

Searching for and adding a user

Searching for and adding a user


SQL support

The user column is available for both the Budibase DB and external SQL databases.

In the case of SQL, when a user column is added within Budibase, it will create a varchar column in your table to hold the user id:


A common usage of user columns in your tables is to indicate ownership or assignment.

For example, I can add an 'Assignee' user column to a 'Jobs' table to indicate who is responsible for completing that job.

When making use of a user column in your Forms, you need to use the User Field component.

Show current user records

For single user columns, you can filter on the currently logged in user by using the {{ Current User._id }} binding.

If your user column has Allow multiple users enabled, then the filter will be a contains like so:

Migrate to user column


As of v2.11.0 you will no longer be able to create a relationship between the Users table and a Budibase DB.

To accommodate this change, apps that were created before v2.11.0 can migrate existing user table relationship fields to the new user column, as outlined below.

  1. Open your existing app and navigate to the Budibase table that contains a user relationship
  2. Click the hamburger menu, and select the last option: Migrate to user column
  1. Click Continue to create the new user column. As warned, you may need to update some existing bindings
User column added

User column added

This will remove the link from the App users table and can improve the performance of your apps.

It should also be noted that if you were displaying user data through a migrated relationship link, this would also need to be updated as shown in the 'Usage' section above.