---
title: How To Guides for People and Places Lookups
excerpt: ''
deprecated: false
hidden: false
metadata:
  title: ''
  description: ''
  robots: index
next:
  description: ''
---
<br />

# How to Exclude Records from People Lookups

You can tag records as `SITE_USER` or `SERVICE_ACCOUNT` in the mapping step under the User Identity config to have them be excluded from People Lookups. This is done in the identity vars mapping.

# How To customize the Label for Lookups Discovery Button

1. Navigate to **Lookups** > **Lookup Configs**
2. Find **Label for "Lookups" Discovery Button**

   ![](https://files.readme.io/05742bc4d0c05aa94fecb482442ccd689676ffab142c7810701b2d81b3956f20-Screenshot_2024-08-28_at_11.00.24_AM.png)
3. Input the preferred label for the button
4. **Submit** the changes
5. Once you submit the changes, the label text will be updated

# How To customize Lookup Sample Queries

1. Navigate to **Lookups** > **Lookup Configs**
2. Scroll to find **Sample Queries to Try in the Lookups Discovery Card**

   ![](https://files.readme.io/78353a4978f643c90298774e0b2aade011361af70156082b777d0d924bc4600d-Screenshot_2024-08-28_at_10.53.40_AM.png)
3. Add, edit, or delete the sample queries
4. **Submit** the changes
5. Once you submit the changes, the Lookups Discovery Card will display the updated queries

# How To customize Fields for People Lookup Results

1. Navigate to **Lookups** > **Lookup Configs**
2. Scroll to find **Override default fields** in **People Lookup Card Results Configs**

   ![](https://files.readme.io/7a530192dd28b0537ceda4ee5243355c6e9612ee30d06acc0c9a9052b2111dea-Screenshot_2024-08-28_at_1.50.43_PM.png)
3. Add or delete the fields that you want to show in the people lookup results card
4. **Submit** the changes
5. Once you submit the changes, the selected fields will be shown in people lookup results card

> 🚧 Note
>
> This config will replace all the fields defined in the 'Default Fields' for People Lookups.

# How To customize Field for Lookup fields

1. Navigate to **Lookups** > **Lookup Configs**
2. Scroll to find **Customize default field titles for people and places** in the **Additional Settings for Lookup Result Field Configs**

   ![](https://files.readme.io/e5243f7c4a08c61feeb60302480d6f455a5631927a90d315ca4491968c49bb59-Screenshot_2024-08-28_at_2.03.09_PM.png)
3. Add (or delete) the default field titles as keys and desired field titles as values. For example, if you want `first_name` to be displayed as `First Name`, then `first_name` will be the key and `First Name` will be the value
4. **Submit** the changes
5. Once you submit the changes, the customized fields titles will be shown instead of default field titles in people and places lookup results card
6. **I want to customize fields shown in case of similar or ambiguous results**

   1. Navigate to **Lookups** > **Lookup Configs**
   2. Scroll to find **Distinguishing fields in case of ambiguous results** in the **Additional Settings for Lookup Result Field Configs**

      ![](https://files.readme.io/54256399ec03652631b6c922d4489dc427cdc40b534294e66bbe64006d314c94-Screenshot_2024-08-28_at_2.03.38_PM.png)
   3. From the dropdown, select the fields that should be shown to help distinguish between lookup results that are similar or ambiguous
   4. **Submit** the changes
   5. Once you submit the changes, the selected fields will shown to distinguish results in case of ambiguity

# How To Setup or Update the Conference Room Integration

1. Navigate to **Lookups** > **Conference Rooms Configs**
2. Select the data source from the dropdown menu to determine where the details will be retrieved from

   ![](https://files.readme.io/0372ff8e4ba3508e8fa157c40011f75d3025e6f997b5e6a8423a6a1b3f1ccf14-Screenshot_2024-08-28_at_10.28.09_AM.png)

   1. For **OfficeSpace**, you don’t need to provide any key or ID
   2. For **SpaceIQ**, you will need to provide your API key

      ![](https://files.readme.io/049d7f6c6d58d26e91a3e85d316ac11b8625e2fd1505762720ea52d5db54a9d2-Screenshot_2024-08-28_at_10.09.16_AM.png)
   3. For **Google Sheets**, you will need to provide the sheet ID

      ![](https://files.readme.io/03f8cd53139bb69b3e0198fd4243412967e56c59af2b4e98e5ae12388708584f-Screenshot_2024-08-28_at_10.28.26_AM.png)
3. **Submit** the changes
4. Once you submit the changes, the new/updated conference room details will be ingested

> ❗️ Note
>
> There are certain advanced or deprecated configs that we do not recommend modifying. If you need to update those settings, please contact our customer success team for assistance.

# How To Add Custom Attributes to the User Roster

### Prerequisite

* There should be an already configured user ingestion before continuing with this guide.
* The external identity system API field names should be validated.

### Configuration

First, navigate to **User Identity -> Import Users**.

1. Click **Edit** on the existing user ingestion settings.

![](https://files.readme.io/af43e707fe13974464e987b39a852b6ab32db8a057ca2c947da2c80d43f8672d-image.png)

2. Click **Next**.
3. Click the **Advanced mode** toggle to switch to Advanced Mode

![](https://files.readme.io/1a28f09341045423a3b7ad623132a7ad1eb676bc0e64be9aef22733fe1a72190-image.png)

4. Click **Continue**

![](https://files.readme.io/f90faa0c80d26504e2b8dcafe4e91877ebd2748c2527f74b09c67e75f615a424-image.png)

5. Navigate to the identity system settings that the custom attribute is to be sourced from and click into the **Source-Specific User Attribute Mapping**.

![](https://files.readme.io/6521d01c33a87e3edf379a00ea4fc1b79ed8d5d26cc0339ece19608dc31fdd62-image.png)

6. Add in a **custom_attributes** JSON object and the attribute that should be saved to the user roster.
   1. In this example, there are two okta fields that will be ingested as custom attributes. **is_manager** and **is_contractor**. In okta, all user fields are stored within the **profile** object. This is different per other system APIs.

![](https://files.readme.io/e82ee3c71a54928d14f501db75a38f4d0cc7fada8d0fe3b3b59291d45e54073c-image.png)

7. Click **Submit** in the lower right.

Next, navigate to **Analytics and Data -> Custom Attributes**.

1. Click on the **Custom Attributes Registration** toggle.

![](https://files.readme.io/ea0f6f193030ad9801d4ed70bbf34f5e1bab7c2a30d3abf116016de833a47764-image.png)

2. Click **Add +**

![](https://files.readme.io/ab2878f8c64a458c28cec2dd8410b9635a90314a5ecd59eaf1f94ad0b692ddb5-image.png)

3. The **Model** dropdown will be **User Data Model**.

![](https://files.readme.io/90eeda13c170b1301633ac3bfc788f3afec23742f4efaebb1c887ac6b72f3743-image.png)

4. Click **Add +** to add a blank **Attributes** object

![](https://files.readme.io/39f2771cd9f8c70e4d3ea56042e9b8619cf94ce27311ac129a27055ea87c1f72-image.png)

5. The **Name** will be the custom attribute name that was listed within the **Import Users** mapper.

![](https://files.readme.io/0de2656d5077bb5283fa07ce51627820f3313587fe0d031faf7b9fc96b966460-image.png)

6. The **Data Sensitivity Policy Policy Type** dropdown will be set to **Customer Data**.

![](https://files.readme.io/40c7f35e7f28323c67b48cae203c5a49b0e6e583c519c21097d6587314f1789e-image.png)

7. The **Customer Data** dropdown will be set to **CUSTOMER_DATA_USER_DATA**.

![](https://files.readme.io/e3777a252b17acbbf6ccd1c04160255e9e361ea580a2b1f6f8de7d0564fcd593-image.png)

8. Click **Submit** in the lower right.

### Validation

This new custom attribute can be found within the **User Identity -> Imported User** roster lookup after the next user ingestion. It can take 24 - 48 hours for a custom attributes to propagate to the user roster.