You will not be able to complete this step until your Glean tenant has been provisioned. If you were not able to switch from Magic Links to SSO in the last section, you will need to return to this step later.

​
About People Data

Synchronizing your employee directory to Glean is a critical part of the setup process, as it allows Glean to:

  • Enforce document permissions.
  • Apply role-based access controls (RBAC).
  • Deliver more relevant search results.

If you configured SSO using OIDC in the last step, and your directory is the same as your SSO platform (e.g. Azure AD/Entra ID, Okta), then you have already configured people data sync as part of the SSO configuration; in which case, you now simply need to enable it as a source.

​
Configure a People Data Source

​
Required Fields

You must ensure that the following fields are populated for every user in your People Data source:

  • Name (First Name, Last Name)
  • Email
  • Department

If you do not provide these fields, directory sync of user data to Glean will fail.

Additionally, the following fields are strongly recommended to enhance the Glean experience for your organization:

Recommended FieldDescription
Manager / Manager EmailThe email of the user’s manager. Used heavily in search ranking signals. Required for the org chart to be populated correctly.
LocationThe working location of the user. Required for location-based personalization.
Start DateThe start date of the user. To show tenure in the user’s profile page.

​
Initial Setup

Navigate to  Admin Console > Settings > People data

If your SSO platform supports directory synchronization, it will be listed here with a green checkmark and status Ready to sync. Click the SSO provider’s icon to proceed.

Select your People Data Source form the list of supported apps

If you wish to set up an alternative source, click the appropriate service and follow the setup instructions.

Using a People Data source not listed?

You will need to manually upload your directory data to Glean using CSV, or leverage Glean’s Indexing API to push your directory data to Glean.

In some cases, Glean may also be able to pull your people data from another connected data source such as BambooHR, or Facebook Workplace. Please contact your Glean engineer or Glean support for more information.

​
Attribute Mapping

On the next screen, and if your People Data source supports it, you will be able to map attributes from your directory to the required field in Glean. This is useful if you store user information differently than what is standard.

Map fields to Glean attributes if these are different to the defaults

For example, you might want to infer a user’s manager from their manager’s email. If they have an Okta field called managerEmail, you could map managerEmail to the Glean attribute “Manager”.

If you are unsure about what information is stored in a given directory attribute, you can preview information pulled directly from your directory specifically for your directory profile within the “Glean profile preview” column.

If your People Data source does not support custom mapping in the Glean interface, the directory attributes will be fixed on the page. Please contact Glean support if you require this feature but do not see it for your configured People Data source.

​
Initiate the Sync

Before you start the sync, you can view statistics about what information will be included. For example, how many users will be created, and how many departments you have. If this is different from what you expected, check that you have provided the correct permissions within the People Data source.

View statistics before you sync

Click “Save” at the bottom of the page to save your changes and begin synchronization. From this point onwards, the sync is automatic: Glean will check your People Data source periodically for any changes.

Click 'Save' to start syncing

​
Verification

The People Data sync will start, and over the next hour, you will start to see your employee directory being populated in Glean.

The synchronization is not immediate: Glean needs to crawl your people data first, and then index it so that it is usable in search.

It can take 2-4 hours for the initial sync to complete.

You can return to this page later to validate that your sync is working.

Your people data should be synced after 2-4 hours

If you do not see people data start to show up within a few hours, this typically points to a permissions issue.

Ensure that you have provided Glean with the correct permissions within your IdP when you configured SSO.

For example, for Azure AD, it is critical to have Directory.Read.All and User.Read.All as Application permissions NOT Delegated Permissions. If your issues persist, please contact Glean support.

​
Missing / Invalid People

Glean can encounter issues when synchronizing certain people from your directory. Common issues include:

  • A person’s email is invalid or malformed (e.g. email is missing the ”@” symbol)
  • One or more required attributes are missing
  • A person’s name or email contains a redlisted term

You can see all of the people marked as missing in the “Attention required” tab on the People Data page. Click the “Resolve” button next to a missing person on the table to see the set of instructions you can follow to resolve this issue.

The 'Attention required' tab shows any missing people from your directory

​
Manual Upload (CSV)

For instances where your directory information cannot be automatically synchronized, Glean also supports the manual upload of people data as a set of comma-separated values .csv.

Because this method is not asynchronous, Glean does not recommend it. Any updates to your directory (new employees, departures, or changes) will require you to re-upload a new CSV.

​
CSV Format

The following are mandatory fields:

Required FieldDescription
first_nameThe user’s first name, eg: Ben
last_nameThe user’s last name, eg: Benson
emailThe user’s email, eg: bbenson@domain.com
titleThe user’s job title, eg: Software Engineer
departmentThe user’s department, eg: Engineering

The following are not mandatory, but highly recommended fields to enhance the Glean experience for your organization:

Recommended FieldDescription
manager_emailThe email of the user’s manager. Used heavily in search ranking signals. Required for the org chart to be populated correctly.
locationThe working location of the user. Required for location-based personalization.
start_dateThe start date of the user. To show tenure in the user’s profile page.

A sample CSV is included below:

name,email,first_name,last_name,nickname,title,department,business_unit,manager_email,location,city,country,desk_location,start_date,status,photo_url
Samuel Sample,s.sample@company.com,Sam,Sample,Sam,CEO,Leadership,Leadership Team,,"Sydney, Australia",Sydney,Australia,"Desk 1/25",27/09/22,active,https://i.postimg.cc/rp2Qfkz6/WFH-2.jpg
Ellie Example,e.example@company.com,Ellie,Example,,CFO,Leadership,Leadership Team,s.sample@company.com,"Palo Alto, California",California,USA,,26/10/22,active,https://i.postimg.cc/rp2Qfkz6/WFH-2.jpg
Steve Smith,s.smith@company.com,Steve,Smith,Steve,CTO,Leadership,Leadership Team,s.sample@company.com,"Auckland, New Zealand",Auckland,"New Zealand","Table 1",27/10/22,active,https://i.postimg.cc/rp2Qfkz6/WFH-2.jpg
Benjamin Benson,b.benson@company.com,Benjamin,Benson,Ben,"Software Engineer",Engineering,Engineering,s.smith@company.com,"Tokyo, Japan",Tokyo,Japan,"Level 6, 1/6",03/12/22,deactivated,

​
Upload the Data

Select CSV as a People Data source and select your CSV file when prompted.

If you do not see this as an option or are having difficulties with the upload, please contact Glean support.

Looking for the original version of this page? You can find the archived version here.