What are the differences between EdApp custom fields and SafetyCulture user fields?
EdApp custom fields are attributes admins create to segment users, mainly for Dynamic User Groups and SSO mapping. SafetyCulture user fields do more. They let you capture and store additional information about your users — job title, department, employment type, and more. There are two types: system fields that come pre-configured in every organization, and custom fields you create to fit your needs. Where EdApp custom fields were built for segmentation, SafetyCulture user fields also support rule-based group and site memberships and HR system integrations.
Understanding the difference helps you map your EdApp custom fields accurately when migrating your workforce.
Feature | EdApp custom fields | SafetyCulture user fields |
|---|---|---|
Field type | Custom fields only, created in app settings | Includes system fields and custom fields System fields are pre-defined and can't be modified, while custom fields are created by admins and are fully configurable, except for the data type |
Migration mapping | Custom field labels and values carry across during migration | Migrate custom user fields to map fields and resolve naming conflicts with existing system fields |
Pre-migration best practices | Audit the custom field names for conflicts, then review any custom field values used for Dynamic User Groups or SSO mapping, since these rely on exact values | Check for naming conflicts, confirm field types, and remove duplicates before starting |
Before migrating, audit your EdApp custom fields for name conflicts. Manage user fields and confirm field types in SafetyCulture before mapping, because custom field data types can't be changed after creation.
Types of user fields
There are two types of user fields: system fields and custom fields. Both appear together in your organization's user field list and can be displayed on user profiles.
System fields
System fields are pre-defined fields available in every SafetyCulture organization. These cover standard workforce attributes and are ready to use. You cannot create, rename, archive, or delete them. However, you can add or edit options to system fields that have single select and multi select data types.
Field name | Data type | Description |
|---|---|---|
External ID | Text | A unique identifier for the user sourced from an external HR system. Used for user matching during HR integration imports. |
Employee ID | Text | The organization's internal employee number. |
Start date | Date | The date the employee started with the organization. |
Employee type | Single select | The nature of the employment arrangement. For example, Full-time, Part-time, or Contractor. |
Job title | Text | The user's role or position title within the organization. |
Locations | Multi select | The work locations where the user is based. |
Teams | Multi select | The teams the user belongs to in the organization. |
Cost center | Multi select | The cost centers the user is assigned to for financial reporting purposes. |
Department | Multi select | The departments the user belongs to. |
Business unit | Multi select | The business units or divisions the user is part of. |
External groups | Multi select | Groups assigned to the user from an external HR system, used for access and membership management. |
Entities | Multi select | The legal entity or entities the user is associated with. |
Custom fields
Custom fields are fields you create to capture information specific to your organization. You can configure the name, description, data type, and display settings for each field, and update them at any time.
A few things to note about custom fields:
Custom fields cannot share a name with a system field.
You can create up to 2,000 custom fields in an organization.
Editing the data type of an existing custom field is currently unsupported.
In SafetyCulture, user fields can be shown or hidden on a user's profile. Both system fields and custom fields appear in your organization's user field list, and you can use the Display on user profiles setting to control whether a field is visible on profiles.
A few things to note about visibility settings:
Visibility settings control whether a user field appears on a user's profile.
You can turn this setting on or off when creating or editing a custom user field.
User fields can be reordered to change the order they appear on the user profile.
In the context of migration, visibility settings affect how mapped user field data is presented on profiles after migration, not how the data is mapped.
Data type options
To avoid duplicate values in reporting and analytics, archive the duplicate field and migrate your custom user fields.
