Rename fields and terminology for your org

You can tailor the platform's vocabulary and fields to how your org actually works — call an "Opportunity" a "Deal," hide a field you never use, or make one required. Customizations are scoped to your org only; they never change anything for anyone else on the platform.

Three ways to do it:

• **Account → Terminology & Fields** — the visual editor. Pick a customizable field, rename its label, rename a module term, or set its behavior (visible / hidden / required).
• **Wally** — just ask: "rename Opportunity to Deal," "hide the fax field on Contacts," "make phone required." Wally shows an action card to confirm.
• **/console** — the CLI, for power users who want to script changes.

Only fields on the customization allowlist can be changed — that guardrail keeps the system stable. CRM is the flagship surface (Contacts, Accounts, Opportunities). Renames flow through the translation layer so the new label shows everywhere that field appears, and hide/required behavior is enforced in the forms.

Made a change you want to undo? Reset a field to its default from the same editor, or ask Wally to reset it.