Table row-level actions

Author: Tina Yip | Last edit: December 05, 2023 | Design type: Action menus, Tables | Product area: Ansible

Table row-level actions

Tables should display row-level actions if available. There are a few variations of how the row-level actions can be displayed based on how many actions there are and the importance of each action. The most commonly used action in each area would be surfaced up to the row level, for example “Edit” would be surfaced up in most cases. Actions that are less commonly used on a day-to-day basis, like delete, is relegated to the kebab menu. The kebab menu would always appear last on the row level.

Note: This is the general principle we follow when working with tables but based on the use case there may be some additional variations.

Table row-level with one action

If there is only one row-level action, an icon can be used to represent the action (ex. edit, delete, etc.)

Table row-level with kebab menu and action

Some rows have more than one action available. The most commonly used action, such as “Edit” should be surfaced up, while the rest of the actions such as “Delete,” etc. would remain in the kebab.

Table row-level with kebab menu and two actions

For rows that have an additional commonly used action that needs to be surfaced up, it should appear before the “Edit” button.