Custom attributes are additional details that can be associated with Users' profile in the system and used to organize or search for Users. Administrators can manage these attributes. Custom attributes can be used to store additional information about a user, such as their employment type, joining date, etc.
How to create custom attributes within the Genea Application?
To create custom attributes in your Genea dashboard, follow the steps:
1) Navigate to "Attributes > Custom Attributes" from your Genea admin dashboard. To create a custom attribute, click on "Add".
2) The "Add Custom Attribute" window displays. Enter a Name and Description. From the dropdown list, click a Type.
Text fields are single-line fields into which you can type your information. When creating a text field, input the name of the field and click ‘Save.’ Once created, this field will appear under users' profiles and will let you enter details and edit text.
The checkbox form field type provides a set of checkboxes. This should always be used for a field that has a boolean value, if the box is checked, the field will be set to true, if the box is unchecked, the value will be set to false.
The dropdown is a field type where you can define a menu of choices from which only one answer can be selected. It is ideal for presenting a long list of options without cluttering your form.
When you define a field as a date picker, it provides a GUI widget that allows the selection of the date from the calendar.
Added attributes will be displayed under the "Custom Attributes" tab.
Name: Indicates the name of the field that will appear under the users' profiles.
Type: Indicates if the field is used to store text, dates, dropdown, or checkbox options.
If you would not like to show the specific attributes under the user profile, click the toggle button under the 'Enable/Disable’ column. When the button is grey, it means that the attribute will be hidden under the user profile.
Click on Edit to modify the attribute name and description.
Edit Options: This action is available when the attribute type is defined as "Checkbox" or "Dropdown". It allows you to manage the options.
Click on Delete to remove the attribute from the list.
Managing the default Genea attributes
Employee Number, Cost Center, Mobile Number, and Department are the default attributes from Genea. However, you can disable these default attributes by clicking on the toggle button under the 'Enable/Disable’ column. When the button is grey, it means that the attribute will be hidden under the user profile.
Using Custom Attributes with User Profile:
When at least one custom attribute is defined then a new section called Custom Attributes appears under the User profile page.
You can edit the section and add the required information.
Genea preserves the log of events when any custom attribute is created, edited, or deleted under "Audit Logs".
Once the attributes are added to all user profiles within Genea, you can view, search, and export data based on the attributes within your Genea admin dashboard.
Okta to Genea Access Control attributes mapping
When you integrate Genea with OKTA, you can use attribute mappings to control which all added attributes are to be exchanged during the provisioning process. You can use this attribute mapping to push data from Okta to your Genea application to provision and update user accounts.
Note: For proper syncing, the data type and data values (in case of drop-down and checkbox options) for the defined custom attribute should match between OKTA and Genea. For example, if any field in Genea is added to support the "TEXT" data type, then that field should be added as "string" on the OKTA profile and SCIM app attribute.
Similarly, if an attribute is added in Genea to support a "check-box" with certain options, then the OKTA and SCIM app attributes to be mapped should be defined as a "string array" with an enumerated list of values same as options added to the Genea attribute.
See the example below:
Create Attributes in OKTA to map with attributes in your Genea application
Step 1: Get the attribute's external name and namespace from the Genea:
1) Go to the Attributes > Custom Attributes from the Genea dashboard. Click on "Connect", to be able to use the attribute on the list with the directory integrations.
2) For mapping the attribute, copy the "External Name" and "External Namespace" and keep them saved for future use, we will need them while creating the attributes in OKTA.
Step 2: Create Custom Attributes in Okta User Profile:
1) Locate "OKTA" user profile editor under "Users".
2) Click on "Add Attribute".
3) Add an appropriate display name, variable name, and click "Save". The attribute added to this step, to the OKTA profile editor will required to be mapped with SCIM app attributes to be able to push data from OKTA to the Genea application.
Step 3: Create Custom Attributes in SCIM app, Genea Access Control:
1) Navigate to the 'Provisioning' tab in your Genea Access Control app within your Okta Admin dashboard and click on "Go to Profile Editor."
2) Click 'Add Attribute' and enter the details. Use the "External Name " and "External Namespace" that you earlier copied from Genea dashboard. Click 'Save.'
Step 4: Map attribute from Okta to Genea Access Control
1) Once the attributes have been created, it's time for mapping. Click on 'Mappings.'
2) Click on the 'Okta to Genea Access Control' tab and map the attributes you've just created, as shown in the screenshot below, then click 'Save.'
Once the new mappings have been created, Okta can push all user profile updates as soon as the new mapping is saved, or you can choose not to do push the profile updates. If you choose to 'Apply Updates Now,' all users' profiles within Genea will be updated so please choose this option carefully.
Once the mappings are done, Okta will send mapped user profile attributes to corresponding user profile attributes in Genea.
Azure to Genea Access Control attributes mapping:
Just like with OKTA, when Genea is integrated with your Azure AD, you can use attribute mappings to allow custom attributes to be exchanged during the provisioning process. Attribute mappings can be used to push data from Azure AD to your Genea application during provisioning and updating user accounts.
Apart from standard User profile attributes (name, email, department, and phone number), Genea also allows you to create custom attributes such as Job Title, Company Name, City, Country, Postal Code, etc., and map within Azure AD.
Step 1: Get the attributes' external namespaces from the Genea application:
1) Go to the Attributes > Custom Attributes from the Genea dashboard. Click on "Connect", to be able to use the attributes on the list with Azure directory integrations.
2) For mapping the attribute, copy the "External Namespace" and keep it saved for future use, we will need them while creating the attributes in Azure.
Step 2: Create Custom Attributes in your Azure SCIM app:
1) Sign in to the Azure portal.
2) Navigate to 'Azure Active Directory' > 'Enterprise Applications,' >, search for the name of your SCIM App. Click on the App name.
3) Navigate to "Provisioning" under your SCIM App. Click "Edit Provisioning".
4) Click on "Provision Azure Active Directory Users" under Mappings.
5) Make sure "Show advanced options" is checked and click on "Edit attribute list for customappsso".
6) Use the "External Namespace" that you earlier copied from the Genea dashboard and add it under the Name column of attribute and click "Save".
Step 3: Map the Azure Active Directory Attributes with customappsso Attributes:
1) Once the attributes have been created, it's time for mapping. Click on 'Add New Mapping'.
2) Map the customappsso Attribute you've just created with inbuild Azure Active Directory Attributes as shown in the screenshot below, then click 'Ok.'
3) Click "Save". Once the mappings are saved, you can see the mapped attributes under the list of Attribute Mapping. Azure will now start sending mapped user profile attributes to corresponding user profile attributes in Genea.
IMPORTANT NOTE: Azure AD currently can't provision null attributes. If an attribute is null on the user object, it will be skipped. Therefore, if you remove the attributes from users' Azure profile, then Genea will not get any patch request and those removed attributes will not be updated in Genea.
For more details, please refer to the Null attribute can't be provisioned from the Microsoft document.
If you have any questions about this feature or have any other requests, please reach out to firstname.lastname@example.org.