Alerts and advisories
Alerts explain conditions that affect what you are doing in the app. Their severity helps you distinguish useful context from a reason for caution or an error. An alert's severity alone does not determine whether you can continue; the action's permissions and configuration rules still apply.
| Severity | Meaning |
|---|---|
| Info | Relevant context, such as a wallet chain mismatch that the transaction flow resolves before signing. |
| Warning | A consequence to consider before continuing with a valid choice. |
| Critical | An error or a consequence serious enough to merit strong concern. An authorized person may still be allowed to proceed. |
Confirming a consequential action
An alert dialog interrupts an action when its consequence needs acknowledgement. It explains what will change and offers cancellation or continuation where the action permits it. For example, the confirmation for removing Admin asks you to consider the governance that will remain after setup authority ends.
The browser also asks for confirmation when leaving a wizard would discard entered information. That confirmation uses the browser's prompt, independently of the app's alert treatments.
Inline advisories and field errors
Inline advisories keep relevant context beside the work it affects. They remain until the state that produced them changes, giving you time to read and act on the information. Field errors appear beside the input that needs correction.
When a collection cannot load or has no results, the app shows the corresponding failure or empty state. A failure means the requested information could not be retrieved; an empty result follows a successful retrieval with nothing to show.
Last updated on