Note on product naming: As of 2022, Bananatag is Staffbase's Employee Email product.
Some key aspects of Employee Email temporarily retain the Bananatag name, such as app.bananatag.com, etc.
For all intents and purposes, Bananatag and Employee Email are synonymous.
Before you add your organization's custom fields to Bananatag, there are a couple of requirements:
- Your organization's Microsoft Entra ID is based on-premises and synced to Microsoft Entra (previously Azure AD).
- Your Microsoft Entra ID Global Administrator is able to assist in generating the custom fields.
Identifying Custom Fields
To start your organization's Microsoft Entra ID, the Global Administrator must run the following script in Powershell to fetch the unique custom fields your organization uses internally.:
Get-AzureADUser -SearchString email@example.com | select -ExpandProperty extensionproperty
The above information should be returned in this query...
Outside of the “Prefix”, each section of the extension value is unique to your organization and includes:
- AppClientID - Your organization's unique Microsoft Entra ID tenant ID.
- DisplayName is the custom field display name as set in your organization's on-prem active directory.
- Value - The value of this custom field for the searched user.
In the above example, Bananatag’s on-prem active directory has a field with the name “isBtagOnPrem” which accepts either a true or false value.
Importing Custom Fields
Once you know your custom fields, you can import them into Bananatag. This allows you to segment lists, or even email metrics, according to the criteria in these fields.
1. Click Import Custom Fields.
2. A dialog opens. Insert your custom fields. You can add more than one by clicking Add Field.
3. After adding all your custom fields, click Import Custom Fields to save them.
4. You see your custom fields on the mapping page. You can then map them to Bananatag fields.