Custom fields HR software
Keep the data your company needs
Custom fields hold one value per employee, and custom tables hold many records with dated history. Work permits, laptops, and allowances live on the profile.
Custom HR data that behaves like built-in fields
The data you need lives in side spreadsheets
Laptops sit in Equipment.xlsx, certification dates in a second sheet, and each allowance change overwrites the last. The answers exist, just not on the profile.
Pick a type for every value so the data stays clean
A visa expiry date, a parking space, a permit scan, and a mentor need different inputs. The same 15 field types work for profile fields and table columns, and Select keeps values to a fixed list. There's no limit on how many fields you add, so a cost centre, a uniform size, or a professional licence number each get their own.
Shape the profile so every record arrives complete
Group custom fields into sections and drag them into order. Choose whether each field always shows, shows when filled, or stays hidden, and show it only to the groups of employees it applies to. Make the fields you rely on mandatory. Employees can fill in the fields their role lets them edit. Built-in fields follow the same rules.
Give one employee many records with custom tables
One field can't hold 3 certifications or 2 laptops. A custom table gives each item its own record with the same columns, on the Overview or Work info tab. Employees can request an item, and approved answers land in the table.
Record each change with a date so history stays intact
Make a table historical and every record gets an effective date. A raise or a new contract becomes a new record, Skailer closes the one before, and earlier values stay in the history.
Filter, report on, and get reminders for any custom field
Who still has a company car? Whose permit runs out this year? Filter the People list by any column, custom fields and tables included, and export the result. Skailer sends reminders before a date in a custom field comes up, such as a permit expiry or a licence renewal. You choose who gets them and how far in advance. In HR analytics, you can break down headcount or turnover by any custom field. Old spreadsheets come in through import.
Custom data the rest of Skailer can work with
Roles can be assigned by field value, and a reference field can name an approver. Custom fields and tables define what you store. Roles & Permissions define who sees it.
What does custom fields HR software do in Skailer?
Skailer is customizable HR software that stores employee data built-in fields don't cover in custom fields and custom tables. A custom field holds one value per employee in one of 15 types, and there's no limit on how many you add. A custom table holds many records, and a historical table keeps each change with its effective date. HR filters the People list by any field, uses fields as breakdowns in HR analytics, sends reminders before dates such as a permit expiry, and imports or exports data as CSV or XLSX. Roles & Permissions decide who sees and edits each field, including which fields employees fill in themselves. Asset management is out of scope.
SkailerAdd sensitive data without exposing it
A new field or table stays hidden until a role gets access. For each field, a role gets no access, view, or edit. Read-only roles see only the table columns you open, and the change history has its own switch.
Keep each country's data with the people it belongs to
Each country asks for its own employee data, such as a tax ID in Germany or a work permit in Poland. HR adds these as custom fields and shows each one only to the employees it applies to. An HR role scoped to one legal entity sees only that entity's records. Because every new field stays hidden until you grant access, you collect only the data you need, and only the right people see it.
- Fields for some employees Show a field only to the groups of employees it applies to.
- Legal entity in a field A Directory reference field picks one of your legal entities.
- HR access by entity Scope an HR role to one legal entity or location.
- Data hosted in the EU Skailer stores your data in the AWS Frankfurt region.
What one home for employee data saves HR
Skailer ROI model, 500 employees
DATA RECONCILIATION
REPORT DATA
DATA ERRORS
Custom employee data without side spreadsheets
Teams keep non-standard data in spreadsheets next to the HRIS, in an HRIS with custom fields, or in Skailer. Records, history, and access work differently in each.
| Capability | Spreadsheets next to HRIS | HRIS with custom fields | Skailer |
|---|---|---|---|
| One value per employee | Any format | Text, numbers, dates, lists | 15 types, incl. files and references |
| Many records per employee | A separate sheet | Custom tables in some tools | Custom tables on Overview or Work info |
| Dated history | Kept by hand | Historical tables in some tools | Historical tables, end dates filled in |
| Who sees what | Whoever has the file | Field-level permissions | Per field, per column, history switch |
| Columns in standard tables | Any column | Varies by vendor | Position, Employment, Compensation, more |
| Getting old data in | Copy and paste | Import templates | CSV or XLSX import into fields and tables |
| Reminders before dates | A separate calendar | Date reminders in some tools | Before any date in a field or table |
| Visibility by group | A separate file per team | Varies by vendor | Show a field only to the groups it applies to |
How custom fields and tables work
See how teams use Skailer
Custom fields and tables: common questions
They let HR store employee data that built-in fields don't cover. A custom field holds one value per employee. A custom table holds many records with the same columns, and a historical table adds an effective date to each record. Some HR systems call custom fields "custom attributes".
Yes. FTE is already a built-in field on each employment record, with the date it took effect. For anything else, such as a cost centre, a professional licence number, or a shift pattern, you add a custom field or your own column in the Employment table. Healthcare teams often keep licences and registrations in a historical table, so each renewal has its own dated record.
No. You can add as many custom fields and custom tables as your company needs.
Use a custom field when each employee has one value, such as a parking space number. Use a custom table when one employee can have several records, such as certifications, company devices, or a history of allowance changes.
Yes, if their role lets them. For each field, you choose whether employees can't see it, can view it, or can edit it. Employees then fill in their fields on their profile. Learn more about the employee self-service portal.
Yes. Skailer sends a reminder before a date stored in a custom field or table comes up, such as a work permit expiry, a licence renewal, or a contract end date. You choose who gets it, such as HR, the manager, or the employee, and how many days in advance.
Yes. Make a table historical and every record gets an effective date. Each change is a new record, so earlier values stay in the history, and Export with history downloads all of them. You choose which roles can see the history.
Text, Long text, Email, Phone, URL, Number, Currency, Percentage, Date, Select, Switch, File, Image, Employee reference, and Directory reference. The same 15 types are available for custom table columns.
Not yet. Calculated fields, which work out a value from a formula, are on our roadmap for the coming quarter. Until then, a historical table keeps the inputs, such as base pay and allowances, with their effective dates.
Yes. Upload a CSV or XLSX file and map each column to an employee field or a custom table column, or create a new custom field while mapping. Integrations can read field definitions and table rows, write table rows, and pull the full history for a period through the public API. For example, a payroll system can fetch every bonus record for the quarter.
You can, but under the GDPR, health and similar data need a legal basis and strict access. In Skailer, a new field stays hidden from every role until you open it, so you can give view access to a single HR person.
No. Custom fields and tables define what you store. Roles & Permissions define who sees it. Every new field and table stays hidden until a role gets access. Learn more about roles and permissions.