Summary
We’re requesting a way to prioritize file deletions, file movements, and file permission changes ahead of new/updated content during crawling and indexing, with a configurable, per-tenant policy and admin-facing ETA visibility for when these changes will be reflected in Glean.
Problem statement
Organizations need a predictable, faster path to remove content from search and to apply permission changes in results. Today, it’s unclear how long it takes for deletions, moves, or ACL updates to propagate through standard crawling and indexing, and admins lack an estimated time to completion.
Key use cases
- When a file is removed at the source (e.g., SharePoint/OneDrive), we need Glean to prioritize removing it from the index so it no longer appears in results.
- In oversharing scenarios, files often aren’t deleted; instead, permissions are corrected. Those ACL changes should be prioritized so access is restricted in results as quickly as possible.
- Admins also need visibility to explain that Glean should be updated in "x amount of time" to provide better communications to their users.
Why this matters
- Reduces exposure time for overshared or sensitive files
- Builds admin trust with clear progress and timelines
- Provides predictable governance controls aligned to security policies
Questions for the community
- Are you also prioritizing deletions vs. permission updates? Which events are most critical in your environment?
- What ETA breakdowns would be most useful (e.g., per datasource, per site/library, per item)?
- Would a global policy plus overrides by datasource cover your needs?
