# Customize data fields

Data fields in Fluid are intentionally flexible. You keep only what matters and remove everything else.

### What data fields are in Fluid

Data fields store information about a deal.

They can represent:

* Sales context
* Qualification details
* Links and resources
* Internal notes or metadata
* Non-sales use cases like tasks or projects

Fluid includes:

* Default fields covering the most common sales use cases
* Unlimited custom fields for anything specific to your work

There are no limits and no plan upgrades required.

### Create unlimited custom fields

You can create as many custom fields as you want.

Custom fields can be used to adapt Fluid for:

* Sales workflows
* Project tracking
* Task management
* Internal coordination
* Any custom system you prefer

Supported field types:

* Text
* Number
* Link

Custom fields behave the same way as default fields and can be used anywhere deals are used.

### Control which fields appear when creating a deal

From Preferences, you can control field visibility.

For each field, you can decide:

* Whether it appears in the deal creation modal
* Whether it stays hidden entirely

This allows you to:

* Remove unused fields
* Speed up deal creation
* Reduce visual noise
* Eliminate unnecessary decisions

Only the data you actually use stays visible.

### Reorder fields to match your workflow

You can fully reorder fields in the deal creation modal.

This lets you:

* Place the most important fields first
* Match the order to how you think
* Optimize for speed and muscle memory

Small changes here significantly reduce friction when creating many deals per day.

### Use keyboard shortcuts with link fields

Link fields integrate directly with keyboard shortcuts.

For example:

* Hover over a deal card and press **W** to open the website
* Press **S** to open social media
* Press **C** to open the conversation link

This removes the need to:

* Open the deal
* Copy links
* Switch tabs manually

Execution stays fast and uninterrupted.

### Choose which fields are highlighted on deal cards

Not all data needs to be opened.

For each field, default or custom, you can:

* Mark it as starred
* Choose up to three starred fields
* Reorder starred fields

Starred fields appear directly on the deal card.

This allows you to:

* See critical context at a glance
* Avoid opening deals unnecessarily
* Adapt deal cards to different use cases

### Default data fields in Fluid CRM

Fluid includes a set of default fields that cover the most common sales use cases.

Default fields include:

* Name
* Company
* Value
* Website
* Label
* Title
* Email
* Phone
* Social media
* Conversation link
* Next action
* Expected close date
* Source
* Stage
* Notes

All default fields can be:

* Shown or hidden
* Reordered
* Starred for deal card visibility
* Combined with custom fields

There is no distinction between default and custom fields in daily use. You control what matters and remove everything else.

### Use data fields beyond sales

Because fields are fully customizable, deals are not limited to sales.

Common alternative uses:

* Task tracking
* Project management
* Client onboarding
* Internal requests
* Recruiting pipelines
* Simple workflows that need reminders and ownership

The deal structure stays the same. The fields change to match the context.

### What to read next

* Customize deal cards, how to control which fields appear on cards
* Pipeline customization, how to set up stages and probability
* Keyboard shortcuts, how to use field-based shortcuts in daily work


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://fluid-crm.gitbook.io/fluid-crm-docs/getting-started/customize-data-fields.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.