System status
Lab componentSystem status
System status communicates essential platform-wide information or alerts, such as system maintenance or outages. These messages are designed to be quickly noticed and prompt users to take action if needed. System status offers 4 severity levels, each with a dedicated icon and color; info
, success
, warning
and error
.
The primary purpose of the system status is to provide information and, if necessary, prompt further action.
We advise against embedding excessive content into the system status due to potential color contrast issues. If you need to include additional components within the system status, it will be the responsibility of the application team to ensure accessibility compliance.
- To inform users about critical system-wide issues, security updates or vulnerabilities that require immediate attention.
- To notify users about new system-wide features or enhancements.
- To alert users about planned maintenance schedules and potential service disruptions affecting the entire platform.
- For general updates or information that requires immediate user action.
- For inline messaging. Instead, use
Banner
. - To show a notification that applies to the user’s current task or workflow. Use
Banner
instead. - To communicate when content is loading, instead use the Content Status pattern.
- When the notification requires immediate action and relates to the user’s current task. Instead, use
Dialog
to interrupt the user's workflow.
A system status typically has one or two lines of text. Make content short, clear, and concise, allowing users to quickly understand the situation and/or next steps.
Body Default applies to the content, however, if titles are necessary, configure them to display the Body Strong typography style across densities. See the typography foundation for more information.
To import SystemStatus
and related components from the lab Salt package, use:
Name | Type | Description | Default |
---|
Name | Type | Description | Default |
---|
Name | Type | Description | Default |
---|
The primary purpose of the system status is to provide information and, if necessary, prompt further action.
We advise against embedding excessive content into the system status due to potential color contrast issues. If you need to include additional components within the system status, it will be the responsibility of the application team to ensure accessibility compliance.
- To inform users about critical system-wide issues, security updates or vulnerabilities that require immediate attention.
- To notify users about new system-wide features or enhancements.
- To alert users about planned maintenance schedules and potential service disruptions affecting the entire platform.
- For general updates or information that requires immediate user action.
- For inline messaging. Instead, use
Banner
. - To show a notification that applies to the user’s current task or workflow. Use
Banner
instead. - To communicate when content is loading, instead use the Content Status pattern.
- When the notification requires immediate action and relates to the user’s current task. Instead, use
Dialog
to interrupt the user's workflow.
A system status typically has one or two lines of text. Make content short, clear, and concise, allowing users to quickly understand the situation and/or next steps.
Body Default applies to the content, however, if titles are necessary, configure them to display the Body Strong typography style across densities. See the typography foundation for more information.
To import SystemStatus
and related components from the lab Salt package, use:
Name | Type | Description | Default |
---|
Name | Type | Description | Default |
---|
Name | Type | Description | Default |
---|
The primary purpose of the system status is to provide information and, if necessary, prompt further action.
We advise against embedding excessive content into the system status due to potential color contrast issues. If you need to include additional components within the system status, it will be the responsibility of the application team to ensure accessibility compliance.
- To inform users about critical system-wide issues, security updates or vulnerabilities that require immediate attention.
- To notify users about new system-wide features or enhancements.
- To alert users about planned maintenance schedules and potential service disruptions affecting the entire platform.
- For general updates or information that requires immediate user action.
- For inline messaging. Instead, use
Banner
. - To show a notification that applies to the user’s current task or workflow. Use
Banner
instead. - To communicate when content is loading, instead use the Content Status pattern.
- When the notification requires immediate action and relates to the user’s current task. Instead, use
Dialog
to interrupt the user's workflow.
A system status typically has one or two lines of text. Make content short, clear, and concise, allowing users to quickly understand the situation and/or next steps.
Body Default applies to the content, however, if titles are necessary, configure them to display the Body Strong typography style across densities. See the typography foundation for more information.
To import SystemStatus
and related components from the lab Salt package, use:
Name | Type | Description | Default |
---|
Name | Type | Description | Default |
---|
Name | Type | Description | Default |
---|