Learn Mokapen

Card (form layout)

The Card editor decides how the Data tab looks on entity cards: which fields are visible, in what order, with any separators and spaces. It does not create new fields: it arranges those already defined in Fields.

The flow is the same on Contacts, Companies, Tasks, Projects, Appointments, Deals, Quotes, Orders, Products, Services and Tickets. Changes are organization-wide: every member sees the same form layout.

What it is for

• Lean cards — only what the team uses every day is in view; the rest stays in the palette (hidden from the form, not deleted from the system).
• Mental order — registry → commercial data → internal notes, with clear separators.
• Onboarding — an ordered form reduces errors and fields left blank.
• Alignment — the same experience for the whole team.
• Complement to field rules — a field with restricted Visible/Editable in Fields still follows those rules even if it is on the Card: anyone who cannot see it will not see it on the form.

Do not confuse — changing a value on an open card (click the field → inline edit) is not the Card editor. Here you only configure structure and position.

Where to open it

• Organization settings → area hub → entity settings → Card card.
• From an open card → menu → Modify card (editor opens in another browser tab).

You need a Member role (or higher) and a suitable Premium plan to drag, add/remove and save. Without a plan, drag controls open the upgrade prompt and at runtime the default fields layout remains.

How the editor works

• Preview on the left — simulation of the Data tab. The Title (or equivalent) is fixed: it cannot be moved or removed.
• Fields palette on the right — fields not yet on the card + layout elements (separator, empty space).

Actions

• Drag from the palette to the preview (and vice versa), or use + / ×.
• Reorder fields already present.
• Insert a Separator (horizontal line, optional label) to create visual sections.
• Insert an Empty space to balance a two-column / grid layout.
• Hide a field: remove it from the preview → it returns to the palette. Saved data stays; the field no longer appears on the form until you put it back.

Locked system fields cannot be removed. Fields with a visibility restriction in Fields stay in the palette/layout, but at runtime they appear only to authorized users.

Separators and form organization

Separators are not real product tabs: they are dividers in the form. Practical ideas:

• Registry data — name, contacts, linked company.
• Commercial — amount, source, probability, custom sales fields.
• Internal / restricted — under a “Team X only” separator, place fields with restricted Visible (so even those who see them find them grouped).
• Operational — deadlines, checklists, external links.

Put required fields and those used on every call at the top: less scrolling before save.

Save and Reset

• Save — applies the layout to the whole organization for that entity.
• Reset — returns to the default Mokapen layout (you lose the custom arrangement; fields and their data are not deleted).

Order with Fields and Columns

1. Define the fields (type, default, visibility) in Fields.
2. Arrange them here in Card.
3. If you need them in the table, add them in List & Columns.

Card and Columns are independent. A field can be on the form and not in the list (or the other way around).

Entities and exceptions

• Same editor on Address book, Activities, Sales, Tickets (entities listed above).
• Pipeline & Stages — this is not the Card: it configures kanban stages (often reserved for owners).
• Documents — Card layout is not always available (features coming soon).
• Report charts — another setting: Charts.

Practical tips

• Hide from the Card fields used only by import/automations if they confuse users.
• Do not overload: if endless scrolling is needed, split with separators or remove the superfluous.
• After a major change, notify the team.
• Try on a pilot entity (e.g. Contacts) before replicating on Deals and Tickets.
• Fields with restricted Visible: put them at the bottom or under an “Internal” separator, so the form stays clean for those who do not see them.

Use cases

• Call-ready contacts — phone, email, company, next follow-up at the top; address and marketing below.
• Lean deals — amount, close date, stage, source; margin and legal notes under an “Internal” separator (with restricted Visible in Fields).
• Support tickets — priority, customer, description at the top; SLA and category below.
• Operational tasks — due date, priority, project; process custom fields hidden from anyone not on the delivery team.
• New team onboarding — Reset to default, then only 8–10 essential fields.
• Two “lives” of the same form — sales see the sales block; admins also see the cost block (thanks to Visible on individual fields).

Frequently asked questions

Q: Why can’t I remove a field?

A: Locked system field, or insufficient Premium plan for the layout.

Q: If I hide a field, do I lose the data?

A: No. It returns to the palette; values remain. It does not appear on the form until you put it back.

Q: The field is on the Card but a colleague cannot see it.

A: Check in Fields the Visible only by users/teams rules (and permissions on the card).

Q: Do colleagues see my layout?

A: Yes, it is organization-wide. It is not Home Personalization.

Q: What does Reset do?

A: It clears the custom Card layout for that entity and restores the default Mokapen one.

Q: Are Card and Pipeline the same thing?

A: No. Card = form fields. Pipeline = kanban stages/columns.

Q: The new field does not appear in the palette.

A: Check creation/save in Fields, then reload the Card editor.