Custom Terminology

Rename Blue's core concepts to match your team's vocabulary — workspaces become projects, records become tasks, or whatever else fits.


Your team doesn’t have to speak Blue’s language — Blue can speak yours. If you call them projects instead of workspaces, clients instead of records, or anything else entirely, you can change it once in settings and the whole app updates to match.

Configuring terminology

Workspace name (organisation-wide)

An organisation administrator can rename the term “workspace” across the whole organisation:

  1. Open Organisation SettingsGeneral.
  2. Find the Terminology section.
  3. Set your preferred singular and plural forms — e.g. Project / Projects, Client / Clients.
  4. Save the changes.

This applies to every workspace in the organisation — all members see the updated label.

Record name (per workspace)

A workspace owner can rename the term “record” within a specific workspace:

  1. Open Workspace SettingsRecords.
  2. Find the Terminology section.
  3. Set your preferred singular and plural forms — e.g. Task / Tasks, Ticket / Tickets, Lead / Leads.
  4. Save the changes.

Each workspace can have a different record name — a CRM workspace can call them “Leads” while a support workspace calls them “Tickets”.

Both settings support singular and plural forms so labels read naturally everywhere they appear — “Create a Task” vs “View All Tasks”.

Where it applies

Once saved, the new terminology shows up across the whole application:

  • Menus and navigation
  • Buttons and dialogs (Create WorkspaceCreate Project)
  • Empty states and onboarding screens
  • Notifications and email subjects
  • The mobile apps

API field names, URLs, and developer-facing identifiers stay on Blue’s canonical names — only the user-visible labels change.

Behavior

  • Workspace terminology is organisation-wide — every member across all workspaces sees the updated label.
  • Record terminology is per-workspace — each workspace can have its own name for records.
  • Changes apply instantly; there’s no need to reload.
  • Switching back to Blue’s defaults is a single click — clear an override field and that term reverts.

Custom terminology is great for matching your team’s existing process language, especially if you’re rolling Blue out alongside another tool you’re migrating from. Keep the overrides short — long terms can crowd dense interfaces like the database view.