Contact List

A directory of the workforce with nothing but how to reach people: name and nickname, worker type, role, project, company, work email, phone and manager. It exists for the person whose job is to phone or email — a leave approver chasing cover, a site manager ringing a crew — and it carries no rates, documents, compliance or personal data. It has its own key, sub.view_contacts, so a task role gets exactly this and nothing more.

You enter

A corrected phone number, straight in the cell, for readers with sub.edit_contact or sub.edit — the person ringing is the one who finds out a number is dead.

Saral fills in

Every row from the worker records in your HR scope: name, nickname, type, role, project, company, work email, phone, manager and status; the counts of how many have an email and a phone.
A phone number saved here is normalised to the international form.

It produces

Click-to-call and click-to-email links; a list you can sort and filter by type, role, project, company or manager.

What this page is for

The full Workers roster carries everything about a person — pay, compliance, documents, onboarding, personal details — which is far more than someone needs in order to ring them. This page is the deliberately thin version: who they are, where they work and how to reach them. A leave approver chasing a return-to-work, a site manager who needs a labourer's number at seven in the morning, an office that must email a crew — each gets exactly this list under its own key rather than the whole roster.

What it shows and what it never does

The fields are a fixed list, not a masked view: work email and phone are ordinary contact information, while personal email, date of birth, home address, National Insurance number, bank details and every rate are simply never read by this page. Who appears follows your HR scope — the companies, sites or crew your role covers — the same scope the rest of HR uses. Rows are sorted by name; the search and the column filters work together, and the previous rows stay visible, dimmed, while a new scope loads.

Correcting a number

A dead phone number is found by the person who rings it, so the fix happens here rather than as a request to HR. With sub.edit_contact or sub.edit, hover the phone cell, press the pencil, type the new number and press Enter or click away; Escape cancels. The number is saved in the background and normalised, and a failed save puts the old number back with a message. Everything else about a person is edited on their worker record.

Where the settings live

Nothing on this page is configured here. Who may open it is the sub.view_contacts key on a role, set in Settings → User Permissions; the details themselves — email, phone, role, project, manager — are owned by the worker record and edited on the Workers screens.

Next screen: /hr/messages

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.