UserMenu

The account menu — identity, organisation, preferences, sign-out. The primitive holds the structure, not the content: layers separated by a rule, and a row of “label on the left, control on the right”.

When to use it

The menu under the account in the top bar. The identity layer on top, then the organisation, the preferences and sign-out at the bottom — always in that order.
Preferences that belong to the person, not to a screen: appearance theme, language, vocabulary, in-page help.
Switching into the organisation the person is signed in under. It is a link to another place in the product, not a settings choice.
Signing out. It belongs in the last layer, separated by a rule from everything that is merely toggled.

When not to use it

Settings that need more than one control per choice. The menu is one column wide; a longer form belongs on a screen of its own.
Preferences bound to a single screen — filters, sorting, table density. Those belong to that screen, not to the account.
A list of actions on a record. This is a person's menu, not a context menu for content.
Any attempt to prescribe which preferences the product should have. The kit knows the shape of the layers and rows; what goes inside them is the application's business.

Properties

children: ReactNode — The menu's layers, typically IngotUserMenuSection. The caller decides their order.
label: string — A translated aria-label for the menu. An unnamed group is just an anonymous block to a screen reader.
testId: string — An anchor for tests. It does not affect the appearance.