What it covers
Connect ownership, activity, tasks and search to the same workspace boundary as core records.
Customisation and integrations
Custom objects
Model records unique to the organisation with typed fields and relationships.
How it works
Represent records that do not fit a standard CRM type
Define custom records with typed fields and relationships for the work unique to your organisation. Ownership, activity, tasks and search stay within the workspace boundary.
In practice
Connect custom records to people and work using reusable relationships.
When to use it
Useful situations
- Model a record type unique to your organisation.
- Relate a custom record to customers and operational work.
- Search and assign custom records inside the workspace.
A working path
How the work moves
Define
Create the object with typed fields and supported relationships.
Connect
Relate records to people, companies and relevant work.
Operate
Use ownership, activity, tasks and search to work the record day to day.
Illustrative scenario
property inspection
A facilities team creates an Inspection object, connects it to a site and contact, then assigns a follow-up task to the inspector. The inspection remains a first-class workspace record: the team can find it, assign related work and preserve history without forcing a specialised process into a generic note field.
Before you start
What to check
- Custom objects require the applicable plan and configuration access.
- Fields and relationships should be designed before teams enter large volumes of data.
Do custom records have ownership?
Yes, supported ownership and activity patterns are available.
Who can see our custom records?
People see custom records only when their workspace role and area access allow it.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.