Skip to main content

Custom attributes: add your own fields to employee profiles

Create your own employee profile fields, fill them in per person and keep sensitive values visible only to HR and payroll admins. Every value is encrypted.

Custom attributes let you add your own fields to every employee profile, such as a right-to-work expiry date, an NI number or a uniform size. You create a field once, then fill it in on each person's profile. Every value is stored encrypted.

Who can use them

  • Create, edit and delete fields: Admins, HR admins and payroll admins.

  • Mark a field as sensitive: HR admins and payroll admins only.

  • See and edit sensitive values: HR admins and payroll admins only. Everyone else sees nothing for that field.

If you can't see Attributes under Settings, ask us in chat to switch the feature on for your account.

Create a field

  1. Go to Settings → Attributes.

  2. Add a new attribute.

  3. Enter a name and, if you like, a short description so others know what goes in it.

  4. Pick a type: Text, Number, Date, Yes/No or Select (a dropdown list of options you define).

  5. Tick Sensitive if only HR and payroll should see the values.

  6. Save.

The field now appears on every employee profile in the account.

Fill in a field for a person

  1. Open People and select the employee.

  2. Scroll to the Attributes section.

  3. Enter the values and save. All Gravy checks each value against its type, so a date field only accepts a date.

Sensitive values stay masked until you click to reveal them.

How the data is protected

  • Every attribute value is encrypted, sensitive or not, using the same protection as payroll details.

  • All Gravy keeps a history of changes to each value.

  • Sensitive values never appear for people without HR or payroll admin access.

Editing and deleting fields

  • You can rename a field, change its description or add options to a Select field at any time. Existing values are kept.

  • Deleting a field deletes every value saved against it. Rename a field instead if you want to keep the data.

Did this answer your question?