Skip to the article

Introduction - Worklink Settings

Twelve screens behind one gear: three about people and access, nine that configure a part of Worklink.

Get to know Worklink Settings through these help pages. Each screen is covered on its own page, field by field.

A tour of Worklink Settings: the rail, the twelve screens, and the order to set them up in.

What you can set up

  • Admin ProfileYour own record, across seven tabs.
  • Users and RolesWho gets in, and what they may do.
  • PreferencesYour header widget, on or off.
  • Attendance PolicyThe rules a working day is judged by.
  • EmployeesTypes, statuses and asset categories.
  • Leave PoliciesWhat each leave type grants, and to whom.
  • HolidaysThe company calendar, per year and per site.
  • Work LocationsYour offices and the hours they keep.
  • KioskWall tablets that need no login.
  • OffboardingExit types, notice and clearance.
  • RegularizationThe corrections people may raise.
  • TrainingThe categories courses are filed under.

One panel, two halves

The Worklink Settings panel filling the window. A rail on the left is headed GENERAL with Admin Profile, Users and Roles and Preferences, then MODULES with Attendance Policy, Employees, Leave Policies, Holidays, Work Locations, Kiosk, Offboarding, Regularization and Training. Attendance Policy is selected and its pane fills the rest of the window, headed Attendance Policy with a Policy Scope picker reading Company default, a Policy Name of Ironvale Default Policy, a Timezone of Europe/London and Grace Periods fields. A Cancel and Save bar sits at the foot.
The gear in the header opens this. General is about people; Modules is about the product.

Open the panel with the gear in the header, from anywhere in Worklink. The red cross closes it and puts you back on the Worklink overview.

Not everybody sees all of it

The rail is drawn from what your role allows. An employee with no administrative access opens the same gear and finds two rows: their own record, renamed My Profile, and Preferences. Modules, and Users & Roles with it, belong to an administrator.

Was this document helpful?