Idea
Match how many customers actually structure their companies. A common pattern is:
- Company
- Org / Business Unit (e.g., Technology, Customer Operations)
- Department / Team within that org (e.g., Support, Knowledge Management)
Right now there’s no first-class Org layer in Glean for either:
- The People Profile (what shows under a person’s org metadata)
- Agent permissions (who can see/run an agent)
This creates a few problems:
- Admins and builders have to choose between too broad (entire company) or too narrow (specific departments or ad-hoc groups).
- Current work-around would be to setup the “Org” with IdP groups or overloaded department values, which is confusing and brittle.
- In the People Profile, users only see Department, not the mid-level Org, even when it exists in the people data.
What I’m requesting
- Expose Org in People Profile
- In addition to Department, surface the mapped Org (or similar mid-level field from Workday/Okta/people data) on the People Profile.
- This gives admins and end users a consistent mental model: the same Org concept they see in profiles is what they can target for agent sharing.
- Org-level audience for agents
- Add a first-class Org / Business Unit layer that can be used as a sharing audience alongside:
- Individuals
- Departments
- IdP groups
- Entire company
- Example: allow sharing an agent to Org: Technology, so it’s available to everyone in Technology, without exposing it to the whole company.
Why this matters
- Governance: Lets customers right-size blast radius (Org vs Company vs Department) for agents, instead of jumping from department directly to “everyone.”
- Usability: Sharing audiences match how customers actually talk about their structure (“Technology org”, “Customer Operations”), not just raw IdP groups.
- Consistency: The Org concept would be visible in People Profiles and reusable in agent permissions, reducing confusion for both admins and end users.
