HubSpot customisation: what admins can change
Record layouts, views, board cards, properties, forms, quote templates and custom objects are admin work in Settings, limited by your tier. App cards, custom coded actions, CMS modules and API work need a developer.
Most HubSpot customisation is admin work you can do yourself in Settings, with no code. That covers record page layouts and cards, saved views on index pages, what shows on pipeline board cards, custom properties and property groups, forms, quote templates and conditional options on dropdown properties. Your subscription tier sets the limits more than your skills do. Team-specific record views, board card appearance and conditional options need Professional or Enterprise. Custom objects need Enterprise.
You need a developer when the change needs code that runs. That means app cards that pull data from another system onto a record, custom coded workflow actions (Data Hub Professional or Enterprise), custom modules for your website or quotes, and anything built on HubSpot's APIs.
A simple rule: if the change is about what people see and what they can type, an admin can usually do it. If it needs data HubSpot does not hold, or logic a workflow cannot express, it is developer work. The table further down maps every change to where it sits in HubSpot, the tier it needs and who does it.
How do you customise a HubSpot record page?
Go to Settings, then Data Management, then Objects. Pick the object (contacts, companies, deals, tickets or a custom object) and open the Record Customization tab. You need Super Admin or the "Customize record page layout" permission.
Every account can edit the default view. Here is what you can change and the limits HubSpot sets:
- Tabs. Up to five tabs in the middle column, including Overview. The Activities tab cannot be edited or deleted. Showing a tab only when a condition is met needs Starter, Professional or Enterprise.
- Cards. Up to 50 cards across the left sidebar, middle column and right sidebar. Card types include property lists, association tables, data highlights, stage trackers, property history and a single-object report.
- Team views. A different layout for each team needs Professional or Enterprise. A new team view starts from HubSpot's system default, so changes you made to your own default view do not carry across. To keep them, clone your default view instead of starting fresh.
- Default cards. Cards marked "(default)" cannot be deleted, only reset. Cards you created can be deleted.
Each card type has its own cap. A property list holds up to 24 properties in the middle column and up to 50 in a sidebar. An association table holds up to 12 properties and 5 quick filters, and a data highlights card holds 4 properties. If a rep scrolls past 40 fields to find the three they use, split the list into two cards and put the three that matter in data highlights.
Maximum properties per card type, from HubSpot's Knowledge Base article on creating record cards.
For a worked example, see how to use record customisation to collect properties during playbooks.
How do you change what shows on index pages and pipeline boards?
Saved views work on every plan. Open the object's records, click the add view icon, choose a table or board view, add filters and columns, then click Publish. Views are private by default, and you can share them with a team, everyone, or a custom set of teams and users. To change columns, hover over the right edge of the table and click the edit columns icon. Only five view tabs stay pinned at once: open a sixth and the first one closes.
Pipeline board cards are set per pipeline. Open deals (or tickets), switch a saved view to board, pick the pipeline, click the view configuration icon, choose Board settings and then Card settings. Customising how board cards look needs Professional or Enterprise. Running more than one pipeline needs Starter or above.
The newer card contents setting lets you show up to 15 items on each card, mixing properties, associations and sections. It is in beta, and you opt in through HubSpot's "CRM Views: Auto-Save & Collaborative Sharing" beta. You can save board settings for the whole account or for yourself only.
How do you add custom properties, groups and conditional options?
Custom properties. Settings, then Properties, select the object, then Create property. You need the "Edit property settings" permission. How many custom properties you can have depends on your subscription. Before adding any, check what is already there. A portal that has run for a few years often has two or three versions of the same field. Our guide to finding the HubSpot properties nobody uses shows how to sort them.
This short video from our YouTube channel covers setting up required fields on HubSpot deal properties.
Property groups. On the same Properties page, open the Groups tab and click Create group. Groups only appear inside property settings. To group fields on a record, use property list cards in the record layout.
Conditional options. This limits the choices in one dropdown based on another, so picking "Australia" as the country only offers Australian states. It needs Professional or Enterprise, and both properties must be enumeration types: dropdown select, multiple checkboxes, single checkbox or radio select. Set it on the dependent property, in its Conditional options tab. It applies when someone creates a record by hand, edits a value on a record, uses the HubSpot Sales extension or works through a playbook. It does not apply in forms, which have their own logic.
What about forms, quote templates and custom objects?
Forms. Go to Marketing, then Forms, then Create form. Splitting a form into steps needs Starter or above. Conditional logic on a form (show a field only when another answer is given) needs Marketing Hub or Content Hub Professional or Enterprise. Because conditional options on properties are ignored in forms, set the form's own logic as well.
Quote templates. Settings, then Data Management, then Objects, then Quotes, then the Quote templates tab. HubSpot's current article (updated 15 October 2026) lists Revenue Hub Professional or Enterprise, an assigned core seat, and Super Admin or "Manage quote templates" permission. Without code, an admin can lay out the template, reorder modules, show, hide or lock sections, set branding for that template, and add rich text and attachments. Anything the standard modules cannot do needs a custom quote module, built on HubSpot's developer platform. Accounts on legacy quotes with free tools or Starter can change the logo, colours and fonts on the default templates, and cannot create custom templates.
Custom objects. These need Enterprise on any hub. Create one in Settings, then Data Management, then Data Model, then Edit data model, then the plus icon next to All objects. Clicking through that is admin work. The hard part is the thinking: how the object relates to contacts, companies and deals, and how existing data moves across. Our guide to custom objects in HubSpot covers that planning.
Is HubSpot set up the way your team works?
Talk to Matt about HubSpot setup and development.
What needs a HubSpot developer?
Four kinds of change need someone who writes code and can look after it afterwards.
- 26 October 2026New legacy private apps can no longer be created. Existing ones keep working.
- 31 October 2026Deadline for classic CRM cards to move to app cards.
- From now onNew cards and integrations are built as developer platform projects, versions 2025.2 or 2026.03.
Dates from HubSpot's developer documentation and spring 2026 changelog, as listed in the post's sources.
- App cards (UI extensions). Custom cards built in React as projects on HubSpot's developer platform, versions 2025.2 and 2026.03, using the HubSpot CLI. They can appear on record pages, in record preview sidebars and in the help desk ticket sidebar, and can show live data from your ERP, billing or job system. HubSpot's spring 2026 changelog says private App Functions, the server code behind a private card, need an Enterprise subscription or a free developer test account. Classic CRM cards had to move to app cards by 31 October 2026.
- Custom coded workflow actions. JavaScript (Node.js) or Python (in beta) inside a workflow. They need Data Hub Professional or Enterprise, must finish within 20 seconds, can use up to 128 MB of memory and take up to 50 properties as inputs. If a call fails on a rate limit or server error, HubSpot retries for up to three days, so the code must be safe to run twice. Start with writing HubSpot custom code actions with Claude.
- CMS modules. Reusable website components defined in a fields.json file with an HTML and HubL template, built in the design manager or with the CLI. Public endpoint functions need Content Hub Enterprise.
- The APIs. Since 26 October 2026, you can no longer create new legacy private apps. Existing ones keep working, and new integrations are built as apps on the developer platform, with a static auth token when the app is for your account only. API rate limits are 100 calls per 10 seconds per app on free and Starter, and 190 on Professional and Enterprise. Our developer's guide to the HubSpot API covers objects, webhooks and auth.
Who does what: the HubSpot customisation table
| Change | Where in HubSpot | Tier needed | Admin or developer |
|---|---|---|---|
| Record page layout, tabs and cards | Settings, Objects, Record Customization | Any plan (tab conditions Starter and up) | Admin |
| Record layouts per team | Record Customization, team view | Professional or Enterprise | Admin |
| Saved views and index columns | Object index page, add view | Any plan | Admin |
| Pipeline board card appearance | Board view, Board settings, Card settings | Professional or Enterprise | Admin |
| Custom properties and groups | Settings, Properties | Any plan (count limited by tier) | Admin |
| Conditional options on dropdowns | Property, Conditional options tab | Professional or Enterprise | Admin |
| Form steps and conditional logic | Marketing, Forms | Steps Starter and up; logic Marketing or Content Hub Professional | Admin |
| Quote templates | Settings, Objects, Quotes | Revenue Hub Professional or Enterprise, core seat | Admin |
| Custom objects | Settings, Data Model | Enterprise | Admin builds it, plan it with help |
| Custom quote modules | Developer platform | Same as quote templates | Developer |
| App cards | Developer platform projects, HubSpot CLI | Enterprise or developer test account for private App Functions | Developer |
| Custom coded workflow actions | Workflows, custom code action | Data Hub Professional or Enterprise | Developer |
| CMS modules | Design manager or CLI | Content Hub (Enterprise for public endpoint functions) | Developer |
| API integrations | Developer platform apps | Any plan (rate limits vary) | Developer |
When should you stop configuring and call a developer?
There is a whole post on this: when to stop configuring HubSpot and start writing code. The short checks, from the admin's side:
- The data is somewhere else. If reps need to see stock, invoices or job status that sits in another system, a record card cannot show it until something brings it into HubSpot. That is an app card or an integration.
- The rule has outgrown workflows. Branches stacked five deep, or a calculation a calculated property cannot do, usually means a custom coded action.
- You have checked your own setup first. Plenty of "HubSpot cannot do this" turns out to be a missing property, a team view nobody set up or a tier you do not have yet.
Before any code is written, decide who will own it in a year. A configuration change can be undone by any admin. Code needs a person who understands it.
Frequently asked questions
What does HubSpot customization cover? HubSpot customization (customisation in Australian spelling) covers record layouts, saved views, board cards, properties, forms, quote templates and custom objects, which admins set up in Settings, plus app cards, custom coded actions, CMS modules and API integrations, which need a developer.
Can you customise HubSpot record pages on a free or Starter plan? Yes. Every plan can edit the default record view, with up to five tabs and 50 cards. Showing tabs on a condition needs Starter or above, and separate layouts for each team need Professional or Enterprise.
How do you change the properties shown on HubSpot deal cards in the pipeline? Open deals in board view, pick the pipeline, click the view configuration icon, then Board settings and Card settings. Customising board card appearance needs Professional or Enterprise.
Which HubSpot subscription do you need for custom objects? Enterprise, on any hub. You create them in Settings under Data Management and Data Model, and the number you can have depends on your subscription.
Do HubSpot custom code actions need a developer? Usually, yes. They are JavaScript or Python inside a workflow, need Data Hub Professional or Enterprise, and must finish within 20 seconds, so someone has to write, test and maintain the code.
Sources
- Customize records, HubSpot Knowledge Base, for record layout navigation, tabs, team views and card limits.
- Create cards to display data on records, HubSpot Knowledge Base, for card types and per-card property limits.
- Create and manage saved views, HubSpot Knowledge Base, for saved views, sharing and columns.
- Customize the board view for objects with pipelines, HubSpot Knowledge Base, for board card settings and tiers.
- Create and edit properties, HubSpot Knowledge Base, for property creation, permissions and limits.
- Organize and export properties, HubSpot Knowledge Base, for property groups.
- Limit available options based on a controlling property, HubSpot Knowledge Base, for conditional options.
- Create and customize forms, HubSpot Knowledge Base, for form steps and conditional logic.
- Create quote templates, HubSpot Knowledge Base, for quote template tiers and editing.
- Set up legacy quotes, HubSpot Knowledge Base, for legacy quote theme settings on free and Starter.
- Create and edit custom objects, HubSpot Knowledge Base, for the Enterprise requirement and navigation.
- Add and manage app cards, HubSpot Knowledge Base, for where app cards appear.
- Create an app card, HubSpot Developers, for platform versions, React and the CLI.
- Spring 2026 Spotlight, HubSpot Developer Changelog, for App Functions tiers, public endpoint functions and the classic card deadline.
- Custom code actions, HubSpot Developers, for tier, languages, limits and retries.
- Modules overview, HubSpot Developers, for how CMS modules are built.
- Legacy private apps, HubSpot Developers, for the 26 October 2026 change and API rate limits.
When the change needs code, our HubSpot development work covers HubSpot CMS sites, HubDB, custom modules and API integrations, built by the same team that sets up HubSpot.
Not sure if your next HubSpot change is admin work or a build?
Talk to Matt about HubSpot development. He can explain how we work and whether our HubSpot development service fits what you need.