# Settings Label Inventory

Standardize setting names, descriptions, defaults, dependencies, consequences, search terms, accessibility, localization, and help references.

## Usage note

Inventory the implemented setting and its current default before renaming it. A clear label cannot compensate for an ambiguous control, hidden dependency, or unsafe default.

## How to use this template

1. Inventory every setting's behavior, scope, owner, default, permission, dependency, and consequence.
2. Compare labels and terms across product, help, notifications, APIs, and support.
3. Draft consistent names, descriptions, search synonyms, warnings, and help links.
4. Review accessibility, localization, inherited state, responsive layout, and live behavior.
5. Approve a controlled vocabulary and maintain it through releases and deprecations.

## Blank template

### Setting record

- **Setting ID and current path:** [Enter]
- **Behavior controlled:** [Describe]
- **Scope:** [User / Workspace / Item / Device / Other]
- **Roles allowed to change:** [Enter]
- **Current default and source:** [Enter]
- **When change applies:** [Immediate / Next session / Other]
- **Reversible:** [Yes / No / Conditions]
- **Owner and release:** [Enter]

### Content

- **Proposed label:** [Write]
- **Current-state expression:** [Enter]
- **Description or help:** [Write]
- **Required warning:** [Enter or None]
- **Confirmation copy:** [Enter or None]
- **Product term and definition:** [Enter]
- **Search synonyms:** [List]
- **Help destination:** [Verified route]

### Dependency and exception

- **Required plan or permission:** [Enter]
- **Parent or inherited policy:** [Enter]
- **Dependent settings:** [List]
- **Unavailable/disabled reason:** [Message]
- **Privacy, security, cost, or sharing impact:** [Describe]
- **Migration from old label:** [Enter]
- **Deprecation behavior:** [Enter]
- **Support escalation:** [Enter]

### QA and governance

- [ ] Label, state, and description are meaningful to assistive technology.
- [ ] Product, help, notification, and support terms agree.
- [ ] Default and consequence are accurate.
- [ ] Dependency, role, and inherited states were tested.
- [ ] Localization has context, screenshots, and sufficient layout.
- **Terminology approver:** [Name/date]
- **Tested build and roles:** [Enter]
- **Update trigger:** [Behavior/default/plan/permission]