Fields
| Field | Required | Notes |
|---|---|---|
| First name | Yes | |
| Last name | Yes | |
| Supporter number | No | Auto-generated if left blank; must be unique within the workspace |
| Email address | No | |
| Phone number | No | |
| Date of birth | No | |
| Address — line 1 | No | |
| Address — line 2 | No | |
| Address — town | No | |
| Address — county | No | |
| Address — postcode | No |
Access field groups
Contact fields are organised into groups for the purpose of access restriction. Each group can be independently restricted to specific teams or users.
| Group key | Fields covered | Restrictable? |
|---|---|---|
identity |
First name, last name, other names | No — always visible |
contactDetails |
Email, phone, date of birth | Yes |
address |
Full address | Yes |
connections |
Linked organisations, things, other contacts | Yes |
consent |
Communications consent preferences | Yes |
classifications |
Flags such as is beneficiary, is donor | Yes |
To change access, you need the relationships:manage_contact_access permission. See Create and edit contacts.