List View

The List View widget helps you visualize data in tabular or badge format.

Using the List View

Apart from viewing your data, the List View can help you:

List view options
  1. Change view between List, Badge and Kanban Board

  2. Select Multiple Records

  3. Record options like - record access (sharing with Lite Users), view, edit, delete.

  4. Sort records

  5. Modify Field settings (requires Admin access)
  6. Search your records

  7. Show / Hide Fields

  8. Additional options like Export, Bulk share, Bulk edit, and Bulk delete.

  9. Add a new Field (requires Admin access)
  10. Set the number of records displayed per page

Inline Editing

Keyboard shortcuts for navigation

Move Up
Move Down
Move right Tab or
Move left Shift + Tab or
Edit / Save a record Enter
Cancel changes Esc

Badge View

Apart from viewing data in tabular format, you can switch the view mode on List Views and visualize data in Badge format.

Note: Switching between Tabular and Badge views will only be applied to the user in context.

Badge Configuration

If you have Admin access you can change the Fields displayed in the App’s Badge.

To do this, just click on the icon which is available in every badge.

Badge Config

Note: Only Text, Email, Web URL and Number Fields can be used as Badge Heading. The Field set as Badge Heading will represent records in List and Badge Views.


By default only two slots are used in the Badge - Heading and Main Content. If you wish to show more data in the badge, just click on Add more content. You can add up to three more slots.

Badge Content


Badges are also used to visualize App relationships. Since the space is more limited here, only the first three content slots are shown:

Badge relationships


Note: Badges adhere to Field permission settings. If a user doesn't have access to a particular Field, it won’t be shown in the Badge, even if the Badge is configured to display that Field.

Badge Type

When you're using the Badge View, you can switch between different badge types to display more badges in your working area.

Badge Types


There are three different Badge types:

Badge Type Preview
Heading only
Heading only
Small badge
Small Badge
Large badge
Large Badge

Kanban Board

When you’re using the Badge View, you can group the records and visualize them in a Kanban Board.

You can make use of the Kanban Board to improve organization and efficiency.


Configuring your Kanban Board. Just select the Field to group by

Kanban config


Using your Kanban Board

Want to change your project status from "In Progress" to "Completed"?

Just drag and drop your project in the "Completed" group and you’re good to go.

Kanban drag


Records can be grouped by the following Field Types:

Apply Layout

If you're a Fusioo Admin, you can click on Apply Layout and apply your List View Widget settings on other Users in your team.

List view apply layout
List view apply layout

The following settings will be copied and applied:

  • Fields shown/hidden in the List View
  • Field used to sort records
  • Number of records shown per page
  • Pinned Column
  • Resized column widths
  • Widget Layout (List, Badge or Kanban)
  • Badge Type (Heading, Small or Large)
  • Field used to group records in Kanban Board

Note: After you apply your layout settings, Users can still override them with their personal settings.

List View Filtering

You can apply two types of data filtering: widget filtering and saved views.

Widget filtering should be applied as a base filter.

For example, you might want a List View widget to always display the Projects assigned to the logged in user. In this case, you will need to apply the following widget filter:

Filter on Widget

Note: Widget filtering will be applied to all users.

Saved views can then be applied on the whole dashboard (unlike widget filters, that are applied per widget) and you can, for example, show only ongoing Projects, as shown below:

Dashboard filtering

Note: Saved views are applied on top of widget filters. Unlike widget filtering, saved views are only applied to the user in context. You can share them with other team members.

What would you improve in this article?