# Context Help Choosing a proper component for context help. Use context help to briefly explain how a functionality works if it is not clear from the UI or the application behavior. A full description of the functionality should be provided in [product web help](https://www.jetbrains.com/help/idea/). Context help can be shown as an [inline help text](inline_help_text.md), in a [help tooltip](tooltip.md), and in an [empty state](empty_state.md). ## Inline help text Use an [inline help text](inline_help_text.md) in settings dialogs that are not constrained by space and are not frequently used. Since settings are rarely changed, users may forget their purpose, so displaying the information immediately makes sense. Context help in an inline text ## Tooltip Use a [tooltip](tooltip.md): - If the space is not enough for showing the inline help text. - In frequently used dialogs, tool windows, or popups. The more often a person uses an interface, the more likely they are to remember what each option does. - For icons or other controls that do not have a label. Context help in a tooltip ## Empty state Fill in [empty states](empty_state.md) of tool windows, tables, trees, and other containers with: - a reason why the data is missing - an action that can fix it - a link to a corresponding article in the web help. Empty state of a tool window ## When to use Below you will find rules for [tooltips](tooltip.md) and [inline texts](inline_help_text.md).
Explain a setting

Explain complex behavior that a short action or a setting name cannot convey clearly.

Input format requirements

Provide input format requirements and examples.

Suggest alternative ways

Suggest alternative ways.

Warn about possible issues

Warn about possible issues.

Explain limitations

Explain limitations.

Provide quick navigation to related settings

Provide quick navigation to related settings.

Explain IDE-specific entities

Explain IDE-specific entities.

## When not to use ### Do not explain UI Do not use context help to explain how the user interface works. If you need to explain that, consider redesigning the UI.
Correct Don't explain how UI elements should work Incorrect Incorrect UI requires additional explanation
### Do not explain common actions Do not explain common actions and entities. Show a regular tooltip with an action name and shortcut in this case.
Correct Don't explain common actions Incorrect Common actions are explained in the tooltip
### Do not clutter UI with context help Do not explain each option. Too many help icons or too much inline text make a dialog cluttered and harder to navigate visually. If all options need to be explained, consider rewriting the labels to make them clearer.
Correct Don't explain every option Incorrect Every option has its tooltip
## How to use See [Inline help text](inline_help_text.md), [Tooltip](tooltip.md), and [](empty_state.md).