---
title: "Custom objects: your own kinds of record | SalexHub"
description: "Add the kinds of records your trade needs, with the details you track, formulas that work them out, views for each person and rules every save meets."
url: "https://salexhub.com/platform/custom-objects"
---

# Custom objects

**SalexHub fits the business you have, not the other way round.**

Add the kinds of records your trade keeps, with the details you track. Formulas work out the rest, each person gets the view they work from, and your rules hold on every save, whoever makes it.

Three of Daybook's kinds of record side by side, each a card listing its properties and the type of each. Deal and Company come with SalexHub; Site visit is Daybook's own, at the root of the menu, and looks no different. A deal points at its company, the company adds up the value of its open deals with a rollup and counts the days since its last order with a formula, and a site visit points at the customer it is for, holds its date, the units to deliver and the plan as files, and counts the days until the delivery.

[Start free](https://app.salexhub.com/register) · [See one rule hold everywhere](https://salexhub.com/platform/custom-objects#rules)

## Your business, as it really is.

Every trade keeps things no ready-made system knows about: site visits, vehicles, samples, service visits. Add them, track the details that matter, and work with them like any other record.

- **The kinds of records your trade keeps**: Name a new kind of record, give it an icon and say which part of the business it belongs to: at the root beside Contacts, or on a module's shelf such as Sales or Inventory. It gets its own list, record pages and properties, and works everywhere the built-in records do.
- **Details that work themselves out**: Eighteen kinds of property, from dates and amounts to addresses, files and official numbers checked against their format. Formulas compute a value from the others, such as the days until a delivery, and rollups count or add up the records linked to this one, never mixing currencies.
- **A view for each way of working**: The same records as a table, a board, a calendar or an agenda, filtered the way you need and saved for you, your team or everyone. Keep a list of the records that matter, by hand or by a rule that keeps it up to date. Site visits in one window with the switch between a table, a board by status, a calendar by visit date and an agenda: the same four visits in each.
- **One customer, one record**: Possible duplicates show on the record with how closely they match. Merging keeps the record you choose with its history, and moves the other one's links, timeline, comments and files into it; the other goes to the recycle bin. Two records of one person, compared property by property before they merge.

## What each person gets out of it.

The structure is set once, by whoever runs the system. Everyone else just finds things where they expect them.

- **Owner: A system shaped like the business.** Add the records your trade keeps, put them where your team looks for them, and change your mind later: a record type can move to another part of the menu.
- **Office: Clean data, without policing it.** Write the rule once, a deal above an amount needs a budget confirmed, and every save meets it. Check how many existing records break it today, and merge the duplicates as they show up.
- **Sales: The numbers you need, already on the record.** A company shows what its open deals add up to and how long since it last ordered, computed for you, so the call starts with the facts.
- **Operations: Track what only your trade has.** Vehicles, site visits, samples, service visits: each gets its own list and pages on the shelf where it belongs, with the views your team works from.

## Your data, the way you set it.

Shaping the system never means loosening it. Each property carries its own rules for who sees it and what may change it.

- **Private values stay private.** Mark a property as personal or sensitive and it starts hidden from those who should not see it. Sensitive values also stay out of workflow and AI templates.
- **Sealed with your own key.** On Enterprise an admin can keep a property encrypted with your organization's own key, so no model ever reads it. A property's sensitivity can be raised, never lowered.
- **You decide what AI may change.** For each property, choose whether AI may change it, only propose a value for a person to accept, or never touch it. What it changes on its own, the property's history shows with what it was based on.
- **Nothing is quietly lost.** Every record keeps its edit history. A deleted record waits in the recycle bin, 30 days unless your admins choose another period, and on Business and Enterprise a merge can be undone.

[Field access for every property](https://salexhub.com/docs/control/access)

## One rule, kept at every door.

A rule written once holds for every save of a record: on the screen, in a conversation with the Agent, in an import and in a workflow. Nobody can step around it by choosing another way in.

- **On the screen, a person saves: The save stops, and says why.** The deal is not saved, and the rule's own message says what is missing: a budget confirmed for a deal above the amount the rule names. Waiting for you. Fill in what is missing, then save.
- **In a conversation, the agent saves: The Agent meets the same rule.** The change the Agent prepared is refused like anyone's, and it tells you what the rule needs instead of finding a way around it. Waiting for you. Give it the missing value, or set it yourself.
- **In an import, a file saves: One row refused, the rest saved.** The rows that meet the rule are saved, and the one that does not is listed with the rule's message. Waiting for you. Correct that row and import it again.
- **In a workflow, a step saves: The run stops at the step.** The step that would have broken the rule does not act, and the run's history shows where it stopped and why. Waiting for you. Fix the record or the step, and let the next run go through.

## Where you shape it.

The structure lives in Settings; everything else happens on the records and in the views your team already uses.

- **Settings: Your objects, in one place.** Under Settings > Data: the record types you added, their properties and the rules every save meets.
- **The record: Details and their history.** Each record shows its properties, its possible duplicates and its edit history, so you see where a value came from.
- **Views: The same records, many ways.** A table, a board, a calendar or an agenda, with the filters your team needs, saved for you, your team or everyone.
- **The Agent: Structure in a sentence.** Ask the Agent for a new kind of record or a relationship between two, such as a meal and its ingredients, or to change a property's type after it shows what each value becomes.

## How to get custom objects.

Properties, formulas, views, lists, record rules and merging come with every plan. Record types of your own start with Pro.

- **Free**: included. Properties, views and rules on the built-in records.
- **Pro**: included. Up to 3 record types of your own.
- **Business**: included. Up to 10 record types of your own, and undo a merge.
- **Enterprise**: included. Record types of your own by contract, and undo a merge.

- Records of every kind, your own included, count toward your plan's records.
- Changes to the structure are made by people with the settings permission: Owners and Admins, unless an admin grants it to a role.
- Try Pro or Business free for 14 days.

## Read more

- [Access and sharing](https://salexhub.com/docs/control/access): Field access for every property, on your own record types too.
- [Roles and permissions](https://salexhub.com/docs/control/roles): The rights each role holds, and the roles you build yourself.

## Questions about custom objects

**Do my own record types work with reports and workflows?** Yes. They can be counted in reports, start and change in workflows, and be read and proposed by the Agent, like any built-in record.

**Do I need to write code for formulas?** No. A formula is a short expression over the record's other properties, such as the days until a date, from a fixed set of functions. It never runs code.

**Does a record rule hold for my website's form?** Record rules hold for people and agents working in SalexHub: the screen, the Agent, the API, an import and a workflow. A form on your site, a connector and incoming mail are not held by them.

**What happens to the other record when I merge two?** Its links, timeline, comments and files move to the record you keep, and it goes to the recycle bin. On Business and Enterprise the merge can be undone.

## Keep what your business keeps.

Start with the records you already have, then add the ones only your trade needs. The rules you write hold from the first save.

[Start free](https://app.salexhub.com/register) · [See pricing](https://salexhub.com/pricing)

---

The same page for people: https://salexhub.com/platform/custom-objects. Index of this site for agents: https://salexhub.com/llms.txt
