Log inContact
Log inContact

Person Profiles

Public sites usually need to show people: who leads a department, who to ask about a service, who to approach about a project. The Person type holds those details once, in one place, so they can be shown wherever they are needed.

What a person record holds

A name, a photograph, an email address, a telephone number, a room and a building, and a short piece of text. Fields left empty simply do not appear, so a record carrying only a name and an email address still displays cleanly rather than leaving gaps.

Where person records appear

A person can be shown on a page of their own, gathered into a listing of a team or department. Every one of those draws on the same underlying record, so correcting a telephone number once corrects it everywhere it is shown — which is the main reason for keeping people as records rather than typing their details into pages.

Person records correspond to the site's own user accounts, so the people who can sign in and the people presented to visitors stay aligned rather than drifting apart into two separate lists.

Where the details come from

Person records correspond to the site's own user accounts, so the people who can sign in and the people presented to visitors stay aligned rather than drifting apart into two separate lists.

Drawing details from an external staff directory instead — an LDAP server, for instance — is possible, but it is not part of the standard setup and has to be arranged separately.