```ts
type NotificationToastMessage = object;
```

## Properties

| Property | Type | Description |
| ------ | ------ | ------ |
| <a id="colorscheme"></a> `colorScheme?` | [`ColorScheme`](ColorScheme.mdx) | - |
| <a id="enhancestart"></a> `enhanceStart?` | `React.ReactNode` | - |
| <a id="isclickable"></a> `isClickable?` | `boolean` | - |
| <a id="isdanger"></a> `isDanger?` | `boolean` | - |
| <a id="isinterrupt"></a> `isInterrupt?` | `boolean` | A toast that can interrupt will jump the queue and remove the currently rendering toast and be rendered instead of it. Currently rendering toasts that have a timeout of 0 cannot be interrupted, the toast that tries to interrupt it is discarded and not queued. An example when this can be useful: if many toasts are sent rapidly in response to UI state changes; User mutes, unmute & mutes again and toasts are displayed to reflect these states, the toasts will display without a long timeout between each. |
| <a id="message"></a> `message` | `ReactNode` | - |
| <a id="position"></a> `position?` | [`ToastPosition`](ToastPosition.mdx) | - |
| <a id="testid"></a> `testid?` | `string` | - |
| <a id="timeout"></a> `timeout?` | `number` | - |
| <a id="ondismiss"></a> `onDismiss?` | `() => void` | - |