How it works
An administrator defines an object model, for example Telecom site or Data center, with its fields and sections. Records of that model can then be created by hand, imported or created through the API.
Records are shown as a list, as a kanban board grouped by a status field, or on a map when the model has an address. Filters and saved views work as they do for contracts.
Object models can be related to contracts, entities and other objects, and access rights can be granted per record, so each team sees the sites or assets it is responsible for.
What you get
- Your own object types and fields
- Linked to contracts and entities
- List, kanban and map views
- Access rights per object
Why teams use it
Model what you really manage instead of forcing it into contract fields.
Contracts, documents and deadlines for a site, in one record.
Administrators create models and fields from the settings.
List, kanban and map views across all your assets.
Objects are exposed through the API and MCP like any other record.
More in Entities & custom objects
Entity directory
All your companies, with their data and documents.
Learn more →Entity aliases
Recognise a company under all its names.
Learn more →Document drive per entity
Each company has its own document space, for statutes, certificates and minutes.
Learn more →Entity roles in contracts
Know who is buyer, seller, supplier or guarantor.
Learn more →