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.
In This Article
- How to locate your Active Directory custom fields
- How to import these to your Bananatag Directory
Before you add your organisation's custom fields to Bananatag, there are a couple of requirements:
- Your organization’s Active Directory is based on-premises, and synced to Azure Active Directory.
- Your Azure Active Directory (AAD) Global Administrator is able to assist in generating the custom fields.
Identifying your Active Directory fields
To start, your organization’s AAD Global Administrator will need to run the following script in Powershell, in order to fetch the unique custom fields your organization uses internally.:
Get-AzureADUser -SearchString firstname.lastname@example.org | 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 AAD tenant ID.
- DisplayName - 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 what your custom fields are, you'll want to import them into Bananatag. This will allow you to segment lists, or even email metrics, according to the criteria in these fields.
The steps required to do this are below.
1. Click on Import Custom Fields
2. A box will pop up and allow you to insert your custom field. You can add more than one by clicking Add Field
3. After you’ve added all of your custom fields, click on Import Custom Fields to save them.
4. You should now see your custom fields in the mapping page, which you can then map to Bananatag fields.