Skip to main content

Select people data source

banner

People data is your employee directory synced into Glean. Syncing this data lets Glean enforce document permissions, apply role-based access controls (RBAC), and deliver more relevant, personalized search results.

tip

If you configured SSO using OIDC in the previous step, and your directory is the same as your SSO platform (for example, Entra ID or Okta), your directory is already configured as part of SSO — you only need to enable it as a people data source here.

note

You won't be able to complete this step until your Glean tenant is provisioned. If your tenant is still provisioning, click Do this later and return to this step once provisioning is complete.

Add a people connector

In the Select a data source to sync with people data section, select a people connector to sync your employee directory.

Select a data source to sync with people data

Select a data source to sync with people data

Follow the in-product instructions to connect your people data source. Or, see the following topics for detailed instructions on configuring common connectors:

After you select a connector, Glean shows the Attribute mapping screen so you can confirm or customize how source fields map to Glean attributes. See Attribute mapping for what each column means, which connectors support custom mappings, and which Glean attributes are required for each connector.

The initial sync typically takes two to four hours to complete. For troubleshooting missing or incomplete people data, see People data issues.

Manual upload (CSV)

If your directory cannot be automatically synced from one of the supported people connectors, upload your people data as a CSV file.

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

CSV format

The following are mandatory fields:

Required fieldDescription
first_nameThe user's first name, e.g. Ben
last_nameThe user's last name, e.g. Benson
emailThe user's email, e.g. bbenson@domain.com
departmentThe user's department, e.g. Engineering

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

Recommended fieldDescription
titleThe user's job title, e.g. Software Engineer. Used in search ranking and on the user's profile page.
manager_emailThe email of the user's manager. Used heavily in search ranking signals. Required for the org chart to be populated correctly.
cityThe user's city, e.g. Tokyo. Used for location-based personalization.
stateThe user's state or province (where applicable).
countryThe user's country, e.g. Japan.
start_dateThe start date of the user. To show tenure in the user's profile page.
nicknameThe name the user goes by, if different from first_name.
phone_numberThe user's work phone number.

Here's a sample CSV:

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 connector and select your CSV file when prompted. If you do not see this option or have difficulty with the upload, contact Glean support.