# Entity naming

> Rename entities workspace-wide. Call Feedback 'Voices', Themes 'Patterns', your team's vocabulary, propagated everywhere.

Source: https://productos.ca/documentation/pages/settings/naming (last reviewed 2026-09-22)

The Entity Naming section lets you rename every entity in ProductOS workspace-wide. The new label propagates to the sidebar, page titles, dialogs and dropdowns, the notification feed, and the MCP connector (`whoami` reports your names to Claude Code and other MCP clients).

## What you can rename

For each entity, set the **singular** and **plural** forms and the ID **prefix** (up to four characters, the `FEAT` in `FEAT-42`):

- Feedback → Voice / Voices
- Theme → Pattern / Patterns
- Feature → Capability / Capabilities
- Initiative → Bet / Bets
- Release → Drop / Drops
- Outcome → Result / Results
- Account → Customer / Customers
- Persona → Audience / Audiences
- Product / Module / Team, plus every strategy, intelligence, GTM, sales and design-system entity (Objectives, Competitors, Launch Plans, Battle Cards, Components, …)

API URLs are **not** affected, `/api/v1/feedback` stays `feedback` regardless of what you call it in the UI. The prefix does change the IDs the app displays and accepts (`CAP-42` instead of `FEAT-42`).

## How it propagates

The rename is saved on the workspace and every surface reads it through one shared hook, so it applies for every member once you click **Save**. Admins can open the section, but saving is owner-only.

MCP clients receive the names too: when you ask Claude Code for "all bets" with custom naming, it knows to query initiatives.

## Reset

A single **Reset** button next to Save flips every entity back to the ProductOS defaults; there is no per-entity reset.

## Related

- [Workspaces and roles](https://productos.ca/documentation/guides/concepts/workspaces-and-roles)