People Directory (Atlas) web part

The People Directory web part is a pre-configured In Focus web part showing a view of all the users in Atlas, usually with some filtering applied to show a subset of users.

Most Atlas deployments include a pre-configured People Directory page which includes the In Focus, In Focus Search box and In Focus Filters web parts, but you can also add the People Directory web part to specific pages, for example Department Landing pages where you might filter the users shown to those in that Department.

You can use the following options to sort and filter the users in the pre-configured directory:

1. Enter search terms and press enter to find users with your search terms in their name or other profile information.
2. Click the dropdowns and choose Refiners to filter the users. You can refine by:
   • Office Location
   • Department
   • Title (Role)
3. Choose the sort order from the dropdown. You can sort by:
   • Full Name
   • Title (Role)
   • Department
   • Office Location
   • Rank/Relevance

Each tile shows the name, profile picture, job title and contact details for the users. Clicking on one of the users will take you to their Delve profile.

Adding to the People Directory

Results for the People Directory are automatically generated based on the active users in your Microsoft 365 tenant. New users will automatically be included in the results.

Hide users from the People Directory

Azure Active Directory (where the user profile originally comes from and where the user will be managed) syncs to SharePoint Profiles, and then Atlas reads User info from the SharePoint profiles – this is what SharePoint indexes for People Search. Occasionally a user who has left the business can still appear within the People Directory webparts and searches as the AAD to SP Profile sync can sometimes fail when removing users.

To ensure expired users in AAD no longer show up in People Directories, please follow the instructions below to safely hide users from search.

To hide a user from the Atlas People Directory you will need the help of a SharePoint Administrator. They will know how to edit the SharePoint User Profile for the user from the SharePoint Admin Centre. In the profile, the Administrator would need to scroll down to the bottom of the profile and set the property "Hide profile from Atlas People Directory" to Yes by checking the box:

It may take a few hours for this change to push through but usually it should happen in a few minutes.

Custom configuration

You can customise the layout and query of a People Directory web part by editing the page, then editing the web part and modifying the configuration options. All the configuration options for In Focus web parts are described in the linked article: Configuration for In Focus web parts (Atlas 5.0+)

However in the third page across in the edit window for the People Directory webpart, underneath 'Template Options', there is a button called Manage Persona Fields. This will present which fields are pulled through by Atlas from Active Directory to be displayed against the people profile, such as name, location and email.

There are a maximum of 5 editable fields, 4 are KQL (keyword query language) search syntax fields, the 5th is a SharePoint refiner search. All fields are configurable depending upon your requirements on what to display.

We expect that FirstName, LastName, JobTitle, and Department, are all consistently filled out within Active Directories and would prefer to be displayed, however 'AccountName' can sometimes lead to inconsistencies across AD profile data if the AccountName field within AD does not display email.

If the incorrect email is appearing for some users there are two options: review & alter this AccountName field within AD, or, alter the KQL search for Tertiary Text option to present another field/search property from AD which contains email.

Please note this will be consistent across all People brought in to be displayed in Atlas.

For example; if you would prefer to hide the AccountName in the tertiary field so emails are not displayed on the People landing page, or have a variety of phone number fields or extensions used within AD, you can alter the KQL search query here to:

{{#if MobilePhone}}
{{#if CPClientTeleExt}}
{{MobilePhone}} - EXT:{{CPClientTeleExt}}
{{else}}
{{MobilePhone}}
{{/if}}
{{else}}
{{#if CPClientTeleExt}}
EXT:{{CPClientTeleExt}}
{{/if}}
{{/if}}

(replacing Client with your appropriate searchable query field from AD).

Note: When hovering over an individual, their profile will still pop-up and cannot be configured - this will show location and contact details (including email) by default.