Address & Geography records postal locations and electronic contact details for people, companies, units and venues.
"Head office, third floor" typed forty ways is not a location — it is a spelling problem. Here an address is a governed record with structure: the division hierarchy, the coordinates, the validity window. This manual covers the address entry, the electronic address, and the lattice they form.
What you record
The address entry
| Field group | What it holds |
|---|---|
| Identity | The label; the building name, floor, unit, PO box |
| The place | The division (the geographic hierarchy node), the country, the postal code |
| Precision | The latitude/longitude, the geocode accuracy and source, the formatted address |
| Validity | Valid from / valid to — addresses have lifetimes; record the effective period when an address changes |
| Governance | The verification flag, the notes, the custom fields, who created and updated |
The validity window matters: use effective dates and the applicable retention workflow to distinguish the former address from the current one.
The division hierarchy is the lattice: every address resolves into the geographic structure — the country, the city, the district — so "everything in Izmir" is a real query, not a string match.
The electronic address
Emails, phones, the electronic contact points — held as typed records with the same governance: which is current, which belongs to whom, which is the main one. An entity's contact surface is data, not a note field.
The caches and mains
Entities across the platform (employees, accounts, units, venues) hold their address caches with a main-address flag — the one that ships, the one the letters use. The wiring below keeps them honest.
What you can do
- Record addresses — postal and electronic, with structure and validity
- Record geographic precision — hold coordinates, accuracy and their source
- Maintain validity — retire an address cleanly when it changes
- Query by geography — the division hierarchy makes regional queries real
- Relate — the wiring below
What it connects to
| Target | Examples |
|---|---|
| Employees & accounts | Where people sit; how they are reached |
| Venues | The spatial anchor every venue resolves to |
| Org units | The department's address, the site's address |
| Content & media | Location-bearing knowledge and files |
Where it feeds
Governed geography makes every "where" question computable: regional activity, multi-site presence, the customer's district. The address platform story is the buyer page; this manual is the recording surface.
The pattern note: same four-part structure — record, do, connect, feed. The address manual is where the validity pattern shows: locations with lifetimes, so the past stays true and the present stays current.
Implementers load your operation's geographic reality at adoption — the divisions, the countries, the existing addresses; consultants help define the hierarchy that matches how your business thinks in place.
No record is an island
Every address relates to the entity it locates, the venue it anchors, the division that contextualises it. The lattice is the relationship layer, mapped — and every location on it is true to its window.
Review the record and its context before deciding what to do next.
Venues → · Accounts → · All manuals → · The Address platform page →
Check your work
When a customer moves, check which address is current, its effective dates and the main-address assignment. Keep the previous address where the retention rules require it. Coordinates record a location and its source; they do not prove that the address has been verified.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.