# Custom fields

### Custom fields

**Where to find it:** Settings → Fields **Who can access it:** Admins only

Custom fields let you store any data point on customers, users, and team members that isn't covered by Startdeliver's standard fields. Once created, fields are available across the platform — in customer profiles, lists, filters, health scoring rules, automations, and Shared Space.

***

#### Field types

| Type     | Use it for                                                                       |
| -------- | -------------------------------------------------------------------------------- |
| Text     | Free-form strings — notes, categories, identifiers                               |
| Number   | Numeric values — ARR, seat count, contract value, usage metrics                  |
| Date     | Calendar dates — renewal date, contract start, churn date                        |
| Boolean  | Yes/No flags — paid invoice, trial customer, high-touch flag                     |
| Dropdown | Fixed option lists — customer tier, region, plan type                            |
| Dynamic  | Values that update automatically based on connected data sources or calculations |

***

#### Field visibility

Each field has a visibility setting that controls where and how it appears.

**Editable** — the field is shown on the customer profile and can be edited directly. Use this for fields your CSMs update as part of their workflow.

**Visible** — the field is shown on the customer profile but cannot be edited from there. Use this for fields populated by integrations or imports where manual editing would cause conflicts.

**Hidden** — the field does not appear on the customer profile but is available in lists, exports, filters, and automations. Use this for backend data your team doesn't need to see day-to-day but that feeds health scoring or reporting.

***

#### Field options

**Multi values** — allows a field to hold more than one value. Useful for things like tags, product lines a customer uses, or multiple contact roles.

**Related values** — links the field to another object in the platform. For example, a Contact Person field can relate to a user record rather than storing a name as plain text.

**Shared Space** — makes the field visible inside the customer-facing Shared Space. Use this selectively — only expose fields that are meaningful to the customer.

***

#### Applying fields

Fields apply across the object type they are created for. Customer fields appear on all customer profiles. User fields appear on all user profiles. Team member fields appear on team member records.

Once created, a field is immediately available to use in lists and filters. To make it visible on a customer profile, configure it in Settings → Views → Customer view.

***

#### How to create a field

{% embed url="<https://www.loom.com/share/699d98b05c784d8c827c5125768c146d>" %}

1. Go to Settings → Fields
2. Click Add field in the Customer fields, User fields, or Team member fields section
3. Enter a Name — this is what appears in the UI
4. The Alias is auto-filled from the name and is used as the API identifier. You cannot change the alias after creation
5. Select a Type
6. Set Visibility
7. Toggle Multi values, Related values, or Shared Space if needed
8. Mark Required if the field must be filled before a customer or user can be created
9. Save

***

#### Common scenarios

**Tracking whether a customer has paid their invoice** Create a Boolean field called Invoice paid. Set Visibility to Editable so CSMs can update it directly. Add it to the customer header as a colour-coded tile — red when No, green when Yes.

**Filtering customers by tier** Create a Dropdown field called Customer tier with options Enterprise, Mid-market, and SMB. Set Visibility to Editable. It immediately becomes available as a filter in any list and as a header tile on the customer profile.

**Feeding a product-specific KPI into health scoring** Create a Number field for the metric — for example Signed contracts for an e-sign provider. Set Visibility to Hidden if CSMs don't need to see it directly. Connect it to a health scoring rule in Settings → Health.


---

# 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://docs.startdeliver.io/platform-settings/custom-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.