This site requires JavaScript to be enabled
An updated version of this article is available

How LDAP is Organized

529 views

9.0 - Last modified on 2026-09-10 Revised by Summer Scanlan

8.0 - Last modified on 2026-09-11 Revised by Summer Scanlan

7.0 - Last modified on 2026-09-11 Revised by Summer Scanlan

6.0 - Last modified on 2026-09-09 Revised by Summer Scanlan

5.0 - Last modified on 2026-09-04 Revised by Summer Scanlan

4.0 - Last modified on 2026-09-04 Revised by Summer Scanlan

3.0 - Last modified on 2026-08-20 Revised by Summer Scanlan

2.0 - Last modified on 2026-05-06 Revised by Gillian Hu

1.0 - Created on 2026-03-18 Authored by Lynn Gu

Campus Directory Organizational Units (OU) and LDAP Structure

Table of Contents

Data in the Campus Directory is divided into "Organizational Units" (OUs) based on function and/or purpose. An OU is also referred to as a "bucket," "branch," or "node."

Top-Level Directory Root

The OUs directly beneath the top-level Directory root or suffix entry "dc=berkeley,dc=edu" are:

People OU

ADVCON People OU (alumni)

PreSIR OU

Guests OU

Expired People OU

People OU Advcon OU PreSIR OU Guests OU

Sponsored Guests
Student-Delegates

Expired People OU

Applications OU

Org Units OU

Authorizations OU

Campus Groups OU

Applications OU Org Units OU Authorizations OU Campus Groups OU

People (ou=people,dc=berkeley,dc=edu)

The 'people' branch contains all LDAP entries representing students, staff, and affiliates of the University of California, Berkeley. Please see the links below for details on how data is represented in LDAP for these groups:

Primary LDAP Person Entry

For each campus user, there will be one primary LDAP "person" entry representing the user.

People Entry Example