Cortex Units: records, fields and relations
A Cortex Unit is a table you design for anything in your business: clients, deals, contracts, visits. Each row is a record, each column is a field, and you link units to each other with relations. This page is a map of everything about units and fields.
How it works
Think of Corteksa as linked tables that you build to fit your company:
Start here
Create a unit → get to know its built-in fields → add your own fields → link it to other units → view your data.
Managing units
- Activating, deactivating and reordering a unit
- Folders
- Duplicating a unit or a whole folder
- Installing from a ready-made template
- Making a unit public for public forms
Fields and their settings
- The full list of field types (35 types)
- Required and conditionally required fields
- Unique fields
- Fixed and smart default values
- Conditional show and hide
- Field groups
- Status transition rules
- Showing dates in Hijri
- Shared fields and copying fields
- Who can edit a field: locked fields and API-only fields
- The workspace’s shared tags
One guide for each field type
Basic: Text, Long Text, Number, Currency, True/False, Rating, Date, Date and Time, Start Date, Due Date, Select, Multi-select, Status, Priority, Tag, Email, Phone, WhatsApp Number, Link, Location, File, Photo, Relation.
Filled in by the system: Source, Session Name, Provider ID, Ad Campaign, Ad Set, Ad, Lead Form.
Smart fields
- An overview of smart fields
- The calculation field and the functions reference
- The rollup field
- The lookup field
- The serial number
- The smart catalog, line items and tax and matching rules
Preventing duplicates
- Deduplication control and how matching works
- The modes: Separate + Flag, Unify, Mirror, Comment
References
The Tasks unit exists in every workspace and can’t be deleted. See Add tasks to a record and follow them in My Tasks.
A real example
The company managed contracts in Excel, and visits in a WhatsApp group.
- It created three units, “Clients”, “Contracts” and “Visits”, and put them in an “Operations” folder.
- It linked each client to their contracts, and each contract to its visits, with relations.
- In the contract, it added a rollup that counts the visits done, and a yearly serial number for contracts.
The client’s record now shows their contracts and visits on one screen, instead of three files.