Custom user information fields extend each user record with data your business cares about beyond the basics — department, employee number, hire date, manager, payroll system ID. Different from custom user preferences (which control UI behaviour), these store information about the user.
Information Fields vs Preferences
- Information fields: Facts about the user (department, manager, hire date) — read or write by admin or HR; typically don't change UI behaviour.
- Preferences: Settings the user controls (theme, language, density) — change UI behaviour.
- Both are technically custom fields on the user record but serve different audiences and roles.
Common Information Fields
- Department: Dropdown of org units.
- Job title: Free text or dropdown from HR system.
- Employee number: The HRIS-issued identifier.
- Hire date / start date: For tenure-based features.
- Manager: Linked user — drives approval chains.
- Office location: Building / city.
- Cost centre: For expense routing.
- Skills / certifications: Multi-select for filtering.
- Emergency contact: Group field with name + phone + relationship.
Where Values Come From
- Self-service: User fills in via profile.
- Admin/HR: Filled in by admin on creation.
- HRIS sync: Automated pull from Workday / BambooHR / SuccessFactors.
- SSO claims: Mapped from IdP attributes at sign-in.
Worked Examples
- Internal staff system: Department, manager, employee number sync nightly from HRIS.
- Healthcare staff: Job title, certifications, on-call schedule. Certifications drive what records they can access.
- Field service: Office location, skills, current location coordinates (for dispatch).
- Marketplace seller user: Business name, VAT number, payout account.