Documentation
Go to RedFlag
Documentation
Go to RedFlag
Getting Started
User Guides
User Guides Overview
Location Details
Setup
Profile Data Field SetupData Field PreferencesDefault Email DomainContact CardRecipient Verification MessageWelcome Message
Users
Groups
Recipients
Desktops
Messages
Templates
Chats
Incidents
Integrations
Branding and Customization
Resources

Profile Data Field Setup

📍 To access Data Fields, go to: More > Setup > Profile Data Field Setup

Overview

Use the Profile Data Field Setup page to configure the data fields used to store and import recipient and desktop profile information.

RedFlag supports up to 33 data fields for recipient and desktop profiles. You can configure as few or as many fields as needed to match your data requirements.

  • Some fields are flexible and can store general information (e.g., Job Title, Department).
  • Other fields are designed for specific data types, such as Address, Phone Numbers, or Delivery Channels.
  • The setup also supports automated recipient imports through integrations like Azure AD and Paylocity.

🛡️ Note: If your location uses a Data Integration for data import, you must map the Unique ID field for successful recipient synchronization.

Configuration of Data Fields

To use a field, enable it in the left column of the Profile Data Field Setup page.

Column Descriptions

Enable

  • Turn on a field to store data for recipients or desktops. 

Recipients / Desktops

  • Choose whether the field applies to recipient profiles, desktop profiles, or both.

🛡️ Note: To group both recipient and desktop records by a field like Job Title, enable it under both columns.

API Field

  • This is the backend name of the data field. Used for sFTP data import or when using the Recipient API.

Field Type / Max Characters

  • Indicates the type of data allowed (e.g., TEXT, PHONE # ONLY) and the character limit for the field.

Dynamic

  • Fields marked with a ✅ icon are eligible for use in dynamic group filters.
  • Fields designed to hold unique values (such as Email Address) are not eligible for dynamic grouping.
  • We recommend enabling as many dynamic fields as possible to support more precise audience targeting.

Display Name

  • Update the field name visible to platform users. Some system fields (e.g., Email) must retain their intended purpose but can be relabeled for clarity (e.g., “Work Email”).

Required

  • When enabled, the field must contain a value to save the profile.

Drop Down List

  • Configure predefined values to ensure consistent input—ideal for fields used in dynamic grouping (e.g., avoid typos like "HR" vs "Hr").

Recipient App

  • Enable to display this field on a recipient's profile in the Recipient App.

Read Only

  • Make the field view-only on the Recipient App so recipients cannot edit the value.

🛡️ Note: If your location uses a Data Integration for data import, additional columns will be included that must be mapped to import recipient data. 

Field Types

Standard Information Fields

Includes core identity fields:

  • First Name, Last Name, and Unique ID – can be enabled as needed.
  • For desktops, the Device Name and Display Name are always enabled in the backend and not editable through this page.

🛡️ Note: For locations that manually upload recipient data, it is strongly recommended to assign a Unique ID to each recipient profile whenever possible. RedFlag uses a mobile number, email address, or unique ID as the primary unique identifier for recipients. If a recipient profile is missing both a mobile number and an email address, having a unique ID ensures the system can properly match and update existing records during bulk uploads. Without a unique identifier, the recipient may be re-added as a new record each time a file is uploaded, since the system cannot recognize who they are.

Delivery Channels

Lists the available message delivery methods for your location:

  • These are used for message routing and cannot be repurposed for other data types.
  • Cannot rename: Mobile App, Microsoft Teams, Desktop App

Address Information

Dedicated fields for physical address data. Useful for:

  • Dynamic grouping
  • Geofencing
  • Threat Intelligence

Other Information (Repurposable Fields)

Custom text fields you can enable, such as:

  • Job Title
  • Location
  • Region
  • Shift

Advanced Fields

  • Advanced fields support multi-value entries.
  • You can set dropdowns as single-select or multi-select.
  • For bulk uploads with multiple values, use commas inside double quotes:
    "Dallas, Fort Worth" → stores as Dallas and Fort Worth
  • Only text values are supported (not emails or phone numbers for delivery channels).

Data Field Preferences

📍 To access Data Field Preferences, go to: More > Setup > Profile Data Field Setup

Overview

Configure the display preferences for your data fields, including selecting a primary data field that will be shown for recipients and desktops throughout the platform.

Primary Display Data Field

Choose which data field should serve as the primary display for recipients and/or desktops. The value from this field will appear prominently in profile slide-outs and list views, with additional fields available by expanding each row. This selected field will also be included in the Message Report.

  • Any enabled data field can be selected as the primary display field, with the exception of:
    • Channel fields (e.g., Mobile App, Desktop App, Microsoft Teams)
    • Advanced Data Fields

🛡️ Note: You can update this preference at any time as your organizational needs evolve.

English
Powered by Product Fruits