> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to show conditional fields on a card cover
- URL: https://blog.jestor.com/conditional-fields-on-card-cover/
- Published: 2026-09-16T18:50:37.000Z
- Updated: 2026-09-16T18:50:37.000Z
- Author: Bruno Bannach

**Conditional fields on a card** let the cover display different information depending on the record's situation, not just its stage. In **Jestor**, any condition can control which fields and buttons appear on the outside of the card, using either show or hide logic.

## Why stage alone is not enough

Configuring the card by stage covers the common case: show the contract field at closing, hide it earlier. It falls short when relevance depends on something else.

An approval button should appear only on records awaiting approval. An overdue warning should appear only when the date has passed. Neither maps cleanly to a stage.

Where conditions beat stages:

- An approval button shown only to records awaiting a decision
- A warning appearing only when a deadline is missed
- A field displayed only above a certain amount
- A tag shown only for a specific client type
- A button hidden once the action has been taken

## Show logic or hide logic

| Approach                           | Default state        | Best when                        |
| ---------------------------------- | -------------------- | -------------------------------- |
| Hide by default, show on condition | Card starts minimal  | Most fields are rarely relevant  |
| Show by default, hide on condition | Card starts complete | Most fields are usually relevant |

## Step by step to configure it

1. **Open the board** and go into the edit view.
2. **Find the card cover settings**, alongside the color and open card conditionals.
3. **Select fields displayed on the card** as the area to configure.
4. **Choose your logic**, hiding by default and revealing, or the opposite.
5. **Write the condition**, based on any field, not only the stage.
6. **Include buttons** where an action should only appear in certain situations.

## Why this reduces mistakes, not just clutter

A button that is always visible will eventually be clicked at the wrong moment. Making the action appear only when it is valid is a form of guardrail, and a gentler one than an error message after the fact.

- **Any condition, not only stage:** relevance defined by the data
- **Buttons included:** actions appear only when they apply
- **Two logics available:** show on condition or hide on condition
- **Configured like other conditionals:** the same familiar interface

## Frequently Asked Questions

### Can I control buttons as well as fields?

Yes. Conditions can determine whether a button appears on the card cover. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Does this only work by stage?

No. Any condition can be used, not just the stage of the card.

### Can I start with a minimal card and reveal fields?

Yes. Both hide by default and show by default are supported.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.