Fields
“Add” is the Add a contact form; “Edit” is the Edit contact page.
| Field | Required | Where you set it | Notes |
|---|---|---|---|
| First name, Last name | Yes | Add, Edit | Identity. Visible even when the rest of the record is restricted |
| Title | No | Add, Edit | Suggestions come from Configuration → Titles, but any title can be typed |
| Other names | No | Add (block), Edit | Middle names or what they go by |
| Subtypes | Yes, at least one | Add, Edit | Classifications from Configuration → Subtypes. They decide which custom fields apply and can restrict who sees the record |
| Email address, Alternate email address | No | Add, Edit | Stored in lower case. Mark a Shared email address used by several people |
| Phone | No | Add, Edit | Must be a valid phone number, for example 020 7946 0958 or +44 20 7946 0958 |
| Date of birth | No | Add (block), Edit | |
| Gender | No | Add (block), Edit | Options from Configuration → Genders. An archived option stays on contacts that have it, marked “(archived)” |
| National ID | No | Edit | The person’s national identification number, such as a Danish CPR number or a UK National Insurance number. Up to 32 letters, digits, spaces, dots, slashes or hyphens, starting with a letter or digit. Part of the contact details group, so it’s hidden from anyone denied those details. It isn’t included in segments or exports |
| Child | No | Add, Edit | Locks all communications consent to No |
| Beneficiary, Donor | No | Add | Classification. Recording a payment marks the contact as a donor. Together they decide the default access scope |
| Address: Address line 1–3, Town, Postal code, Country, Address comment | No | Add (block), Edit | Shared postal address links other contacts at the same address. Imported addresses that couldn’t be split into lines show as Full address (as imported) |
| Notes (Internal note on the add form) | No | Add (block), Edit | Visible to your team only |
| Connections | No | Add (organisation and resource blocks), Edit, profile | See Link records together |
| Communications consent | No | Add, Edit, profile | Yes/OK, No or Unknown per purpose and channel, with history. See Record communications consent |
| Custom fields | Depends on the field | Edit, profile | Your beehive’s contact fields, filtered by subtype |
| Tags | No | Profile | |
| Access scope, Allowed teams, Allowed individuals | No | Add (teams and individuals), Edit | See Restrict who can see a record |
| Archived, deceased, date of death | No | Edit (Caution zone) | See Create and edit contacts |
| Supporter number | No | Not editable in the app | A numeric identifier, for example from an import |
Access field groups
Parts of a contact can be withheld from particular people. When a group is withheld, its section on the profile shows who does have access.
| Group | What it covers |
|---|---|
| Identity | Name. Never withheld, so a restricted record still shows who it is |
| Contact details | Email, phone, date of birth, gender, national ID and similar personal details |
| Address | Postal address |
| Connections | Links to other records |
| Consent | Communications consent |
| Classifications | Donor, beneficiary and related flags |
The Edit contact page controls who can see the whole record. Field-group restrictions can be present on a record, for example from an integration, but aren’t set from the edit page. Changing access needs relationships:manage_contact_access.