Attribute mapping: which attribute fills which field
The fields of a person and their directory defaults. Different attributes can be set per field and apply to signatures, licences and policies alike.
Every field of a person is filled from a directory attribute. The defaults match an ordinary Active Directory. Where a company maintains different attributes, the mapping can be changed per field, under Settings, Directory, Directory agent, adjust attribute mapping.
Fields and defaults
| Field | Default in Active Directory |
|---|---|
mail, userPrincipalName | |
| Display name | displayName, cn |
| First name | givenName |
| Surname | sn |
| Job title | title |
| Department | department |
| Phone | telephoneNumber |
| Mobile | mobile |
| Office | physicalDeliveryOfficeName |
| Street | streetAddress, street |
| City | l |
| State | st |
| Postal code | postalCode |
| Country | c, co |
| Fax | facsimileTelephoneNumber |
| Last changed | whenChanged, modifyTimestamp |
Several attribute names can be separated by comma. The agent then takes the first one that is populated. An empty field falls back to the default.
Where the fields end up
Signature templates insert these fields as placeholders, for example job title and department below the name. Changing a phone number in the directory changes the signature of every future message, without anyone touching a client.
The same fields drive licence management, the assignment of policies by department and the people search in the archive.
Secondary addresses
Further addresses of a person come along from proxyAddresses and are kept as aliases. They decide whether a message sent under a secondary address gets its signature and whether a licence applies. Without aliases the same person may be counted twice.
Changes take effect after approval
Every change to the attribute mapping is a change to the scope. The agent then runs a dry run and writes nothing until it is approved. The dry run shows how many people would be created, changed or removed.