WE People settings
9 areasThese are the areas of WE People an administrator at Wilkinson controls without calling us — the people record, leave, onboarding and access. Each one is rows in a table that you edit — not a value compiled into the software. That distinction is the difference between “we can change our holiday list in September” and “we can raise a ticket and wait for a release”.
Access levels
Who may see compensation, government identifiers, benefits and medical detail, and discipline records — by group, not by person.
Open the access matrix →Employee fields
Add your own fields to the employee record — shirt size and last completed class are already two of yours. Every new field is classified as general or restricted when it is created, with no default and no “decide later”.
See where fields surface →Time rules — in WE Time
Rounding and approval depth per division are configuration of the time app, not of the people record — they live on WE Time's own settings page, next to the screens they govern.
Open WE Time → Settings →Holidays
Your seven paid holidays, Pioneer Day included, plus the birthday rule that is a leave type rather than an eighth holiday.
Open configuration →Time-off policies
The grant tiers by years of service and position, the yearly increment, the carryover treatment, and what happens above the ceiling.
Open configuration →Onboarding checklists
Different task lists for office, field and apprentice hires — with real blocking dependencies between tasks, not just a display order.
Open configuration →Certifications registry
Which licences, safety cards and driving credentials you track, and the reminder ladder. Admin-editable by design — the list is never fixed in code.
Open configuration →Email alerts
New hire, termination, pending approvals, expiring certifications, birthdays. Inside your Microsoft tenant these arrive in Teams; on the portable stack the same alert degrades to email rather than silently doing nothing.
Who receives each alert is still being confirmed — and it matters more than it sounds, because your hire and termination alerts are the trigger for manual keying into Sage, not a courtesy copy.
Surveys
eNPS or your own questions, on a schedule you set. Anonymity is set per survey — some anonymous, some attributed and routed foreman to electrician.
Said plainly because it is easy to get wrong: storing who answered and hiding them in the interface is not anonymity. An anonymous survey has to not know. Who may create a survey, and whether small groups have their results hidden, is still being confirmed.
Divisions
North and South today. A division is not a label on a report here — it is the attribute the approval engine reads to decide where a timesheet goes.
A contractor with one division, five, or none is the same software with different rows. That is the test every setting on this page has to pass.