Skip to main content
All CollectionsAccount Settings
Create Custom Team Member Attributes
Create Custom Team Member Attributes

This guide details the process of creating custom team member attributes.

Jascha avatar
Written by Jascha
Updated over a week ago

Overview

In addition to Mercu's native team member attributes, you can create custom attributes specific to your organisation's needs.

These custom attributes may be used to target enrolments or as dynamic variables in your messaging.

Mercu allows you to create custom attributes via the UI on the Mercu web app or via the bulk upload feature.


Via the Mercu UI

To create custom attributes via the UI:

  1. Navigate to the 'Account' page.

  2. Select the 'Employee Attributes' tab

  3. Click on 'Create New'

  4. Provide and name and click on 'Create Attribute'

That's it!

For more information on how to update team members' custom attributes, see our article on updating team member profiles.


Via Bulk Upload

To create custom attributes via the bulk uploader, you will need to prepare a sheet with the data you wish to populate. A template of a sheet can be found here.

The bulk uploader will use the phone number as the unique identifier of a team member. Any mapped fields with a value will be updated with whatever new value is provided via bulk upload.

A location ID must be specified for each team member. If a user does not already belong to that Location ID, they will be added as a team member to that location.

To create a custom attribute, you will need to create a column in your sheet whose header matches the name of your custom attribute.

Once prepared:

  1. Navigate to the 'People' tab and select the 'Invite Team Members' button on the top-right of the page.

  2. Select 'Bulk Upload'

  3. Add your CSV or paste your table data.

    1. If you pasted table data, choose 'Tab' as the delimiter

  4. In the template fields section, map the First Name, Last Name, Phone Number and Location ID template fields to the respective columns in your file.

Any columns NOT mapped to a template field will be added as a custom attribute.

If a custom attribute already exists with the same name as an unmapped column header, the values in that column will be used to overwrite the existing custom attribute value for the respective team member.

Did this answer your question?