Button is a primary UI element that can trigger an action in a flow.




Figma component

Includes a link to a Figma component that has been imported to Supernova


Use when

  1. there is a request or a transaction that needs to be occur.
  2. progressing an interaction to imply any behavior or flow.
  3. enabling the common actions such as creating, canceling, resetting, deleting, archiving.
  4. enabling the CRUD (create, read, update, delete) actions.

Use don’t when

  1. redirecting to an external resource, use a link instead.
  2. as a navigation element, use a check out tab or content switcher instead.
  3. if the element doesn't trigger any action or interaction.
  4. there are informational messages or alerts where users don't need to take any immediate action.


  1. Button label
  2. Icon
  3. Container




Primary button is the principle button and has the highest emphasis on a page. Also, it should used once on the context.


The secondary button is used to support the main action (primary button) with secondary prominence, offering additional actions.


Outline button are ideal for less prominent actions, standalone or with a primary button for multiple calls to action, and for sub-tasks when a primary action button is present.


The ghost button has the least emphasis on a page and is used to support primary and secondary buttons when they are used together.


Destructive buttons are used when an action (for example: delete, remove, etc.) leads to a dangerous, destructive, irreversible outcome on users’ data or record.


Destructive-outline buttons serve the same role as destructive buttons but with lower emphasis.




Use when there is not enough vertical space for the default or field-sized button in areas such as modal, widgets etc.


Use as primary layout actions and other standalone actions.


Use for pages like login, sign-up, and password reset containing only a couple of inputs.



Enabled button when it is interactive and ready to be clicked.


The hover states indicates that the button is interactive and can be clicked. On icon button, a tooltip can be used while hovering.


When the button is focused via the tab key, it is ready to be activated.


Active state is the button is in the process of being activated.


The disabled state indicates that the button is not currently interactive and communicates that an action is unavailable.


The busy state lets users know the button is on action or task, using a spinner. In this state, the button is temporarily unavailable for interaction.



Text label

Text-only buttons, common in our products, convey actions through labels.

Text label with icon

Text label with icon buttons are used when action needs to be supported with an icon.

Icon button

An icon button expresses the action solely through its icon. Each button type (primary, secondary, outline, ghost) can be used as an icon button.

Icon buttons are typically used in areas where text or text+icon buttons don’t fit in its container, or where buttons need to be used in a toolbar format.


Use tooltip for the related action that represents as icon on a button.


Avoid using icons that are difficult to describe or may be hard to predict as icon buttons, use text button with icon instead.



Buttons should be placed in a location that is relevant to the context of the task or action they take.

Proximity to actions


Ensure that when buttons are used in a group, they are positioned at the correct distance from each other on modals and cards.


Buttons should be close to the content or form elements they are associated with.


Maintain consistent alignment across similar types of buttons.


In areas where approval is required, the cancelling and approve buttons should be positioned with the main CTA on the right.


The action with greater emphasis according to the context should be used as the primary action and should also be aligned to the right.


Buttons should be hug content with their labels; however, they can be used as full-width in widgets or cards.


In areas like login/sign-up flows, the button can be used as full-width considering the usage of other components.


When using widgets to list similar actions according to the context and their emphasis, these buttons can take the size of the container.

Icon usage

Icons should support and enhance the text label, not replace it. Exceptions include icon-only buttons in toolbars where space is limited.

Icon placement


Icons should be placed to the left of the text label to maintain what is label’s express directly.


However, the text label indicates the direction of actions such as next, proceed, add, back, or open menu. The icon should be placed to the right of the text label. Do not place the icon to the right except in these situations.



The emphasis of buttons should be carefully considered to establish a clear visual hierarchy and guide users towards the most important actions. Different button types (primary, secondary, outline, ghost, destructive) should be used to create this hierarchy.

It's important to ensure sufficient contrast between these different button types and the background to maintain visibility and usability. This is especially crucial for primary and destructive buttons, as they often represent the most critical actions on a page.


The button labels should always be simple enough to describe the action in the simplest way possible. This way, when a user interacts with a screen, the buttons on the UI will help reduce visual load.

Also, if a button is used for an action related to accounting terms, it should be labeled using terms that the user is familiar with.


Buttons are always should be sentence case.


No ALL CAPS allowed.


Always state the action with noun+verb.


Choose words that support the action itself, such as on create, edit, and so on.

Figma source