Contacts
A Contact is a person who belongs to an Organization: their name, title, and contact details. It is the shared, installation-wide record of a real person — a client's project manager, a consultant, a regulator, a driller — that you then associate with the Sites and Projects they work on. Each Contact belongs to exactly one Organization.
You manage Contacts from Data Management → Directory → Contacts (route /data-management/contacts).
What a Contact holds
A Contact records who the person is and how to reach them. The required fields are short — an Organization, a first name, and a last name — and everything else is optional detail. Every Contact must belong to an Organization; the Organization is chosen when you create the Contact and cannot be changed afterward.
Two flags classify a Contact. Active marks whether the person is still current, and Primary marks the one Contact that is the Organization's main point of contact. Promoting a Contact to primary demotes whichever Contact previously held that flag in the same Organization, so an Organization has at most one primary at a time. A Contact that is not active cannot be primary — Erde rejects the combination and prompts you to clear the Primary flag or keep the contact active.
Figure: a Contact belongs to one Organization and can be associated with many Sites and many Projects.
Fields
The Contacts grid lists each person by Last Name, First Name, and Organization, with their Title, Email, and Phone, a Primary marker on the main contact, and an Inactive marker on anyone no longer active. Active contacts are listed first, then ordered by last name and first name.
| Field | Type | Required | Description |
|---|---|---|---|
| Organization | reference | Yes | The Organization the Contact belongs to. Set on create; cannot be changed afterward. |
| First Name | text (max 100) | Yes | The person's given name. |
| Last Name | text (max 100) | Yes | The person's family name. |
| Title | text (max 150) | No | Job title or role. |
| Active | yes/no | No | Whether the Contact is current. Defaults to Yes. |
| Primary Contact | yes/no | No | Marks the Organization's main contact. Defaults to No; only one per Organization. |
| text | No | Email address; validated when provided. | |
| Phone | text | No | Phone number; validated when provided. |
| Mobile Phone | text | No | Mobile number; validated when provided. |
| Notes | text (max 2000) | No | Free-text notes; multi-line. |
How it fits together
Beyond the Organization it belongs to, a Contact can be associated with the work it relates to. On both a Site and a Project, the Access & Admin tab holds a Contacts grid listing the people associated with that Site or Project. The same Contact can appear on many Sites and many Projects, which is why Contacts are curated once in the Directory rather than re-entered per Site or Project.
| Relationship | Cardinality | Where you manage it |
|---|---|---|
| Contact → Organization | One Organization per Contact | The Contact's own page |
| Contact ↔ Site | A Contact on many Sites; a Site lists many Contacts | A Site's Access & Admin tab |
| Contact ↔ Project | A Contact on many Projects; a Project lists many Contacts | A Project's Access & Admin tab |
Because of those associations, you cannot delete a Contact while it is still associated with any Site or Project — Erde returns a "has dependents" conflict. Remove the Contact from those Sites and Projects first, then delete it.
Who can do what
Any internal user can view the Directory. Creating, editing, and deleting Contacts requires the Administrator, Data Manager, or Manager role.
| Action | Administrator | Data Manager | Manager | Staff |
|---|---|---|---|---|
| View Contacts | ✓ | ✓ | ✓ | ✓ |
| Create a Contact | ✓ | ✓ | ✓ | — |
| Edit a Contact | ✓ | ✓ | ✓ | — |
| Delete a Contact | ✓ | ✓ | ✓ | — |