User Profile View

User profile view provides a detailed view into ingested user and their corresponding attributes. The user profile view is an important screen to conduct basic troubleshooting with regards to any bot access related issues for a user.

How to access User Profile View?

1. Log in to Moveworks Setup
2. Navigate to User Identity > Ingested User
3. In the "Find User" widget, search for any employee
4. Click on "View Profile" to navigate to the user profile view
5. User profile view can also be accessed by clicking on required user in the All Users table

User Profile View Details

Bot access status

This widget tells whether the user has access to the bot or not. If the user passes the Bot access rule criteria, the status would be Granted.

Data Refresh

This widget tells when the user data was ingested and refreshed. Generally, this is in line with overall user identity pipelines.

User Identity Attributes Table

This list provides a view into standard Moveworks user attributes, org-specific user attributes, corresponding values and overall configuration coverage of these attributes.

This table is important to do basic troubleshooting for any given user. Before we learn few examples for troubleshooting, let's first understand the different columns present within this table.

Attribute: The specific identifier for each user attribute, such as 'Department' or 'Preferred Name'.

Value: The data associated with the user's attribute, displayed here if available.

% Coverage in org: Indicates the percentage of all users within the organization for whom this attribute is populated. A low percentage or 0% suggests the attribute may not be configured for your organization. Please check mapper in identity config.

Is Custom: Specifies whether the attribute is a custom addition beyond the default set.

📘

Example of a troubleshooting use-case:

Let's say, for an org, bot access rule is created using attributes like department and location. Say a user X, is unable to access the bot. Then, the Admin can come to the user profile view and verify that the "Bot Access Status" is Not Granted for this user. For additional troubleshooting, Admin will verify if the attribute Department or Location is populated or not for this user. If it is not populated, and the % coverage is >0, this means there is some issue with the native system from where this attribute is being pulled.

Admins can then go the respective native system and ensure that the value of the attribute is present in the system.

Source Mapping

1. To explore attribute sources, navigate to the User Identity Configuration wizard.
2. In the second step of the wizard "Configure Selected Sources", toggle to Advanced Mode to get detailed insights into source and attribute mapping.

System Integration Attributes

These are the attributes that are used to facilitate system integration.

How to guides?

In the attributes table, I can’t find the source of the attributes. It was available before, how do I find our the source of an attribute.

Due to engineering limitations, source of the attribute is no longer support directly in the attributes table. In order to understand the source of an attribute, admins can:

1. Navigate to identity ingestion wizard
2. Proceed to wizard step #2
3. Switch to advanced mode
4. First review the override mapping config to confirm if the attribute you are searching for has been overridden with another source. For eg. If the primary source is Okta and I want to know the source for “Phone number” attribute, I will first go the override user profile fields config to check the config. If the attribute is found here, the source will be as per the entry in the this config.
5. If the attribute you are looking for is not present in the override bender, then the source of the attribute is going to be the primary source of user identity.
6. Note: the troubleshooting steps slightly differ in case of custom attributes. Custom attributes are generally defined in the Source-Specific User Attribute Mapping config of that identity source.