Golden DB stores two main entity types: Person records (individual humans, identified by email + employer history) and Company records (organizations, identified by domain + name). They're linked: every Person has a current Company (and history of past employers).
Person records
Represent individual humans. Identified primarily by email and LinkedIn URL. Each Person has: name, current role, current employer (a linked Company record), contact channels (email, phone, LinkedIn), employer history, and engagement history.
Company records
Represent organizations. Identified primarily by primary domain. Each Company has: name, industry, size, geography, technographics, parent-subsidiary relationships, contact list (linked Person records currently employed there), deal history, and signal history.
The link
Every Person has a foreign key to their current Company. Employer history shows past links. When a Person changes companies (a job change), the old link goes to history and a new link is created — a key signal the agent can trigger on.
Looking up across the link
From a Company record, see all current employees (linked Persons). From a Person record, see their current and past employers. Cross-references work both ways in the UI and the API.
Common confusions
- Same person, multiple employers — past employer relationships are kept; the Person record has a current and a history.
- Same company, multiple domains — Company records can have multiple associated domains (e.g. acme.com, acme.io, acme.eu).
- Subsidiaries — separate Company records with parent-subsidiary linkage; can be configured to roll up or stay separate in reports.
