LumApps overview
The LumApps connector allows you to integrate your LumApps intranet with Glean, enabling search and discovery of LumApps content directly within Glean. The connector indexes content pages, community pages, and posts, while strictly enforcing LumApps permissions so that users only see content they are authorized to access.
Supported features and limitations
The LumApps connector supports permissions-enforced indexing and search for a range of LumApps content types. It is designed to keep your Glean index in sync with LumApps, reflecting changes in content and permissions as quickly as possible.
Supported objects/entities
- Content pages including homepages, directory listings, and custom content pages
- Community pages
- Community posts
Where available, Glean processes and displays the title, last updated time, author, and text snippets in search results.
Localized content
Glean prefers English values when indexing LumApps content. If a title, source URL, or body-text field has no usable English value, Glean uses an available localized value from LumApps for that field. The connector doesn't translate content during indexing.
Supported API endpoints/features
- LumApps API v1 for content, users, groups, and permissions.
- OAuth 2.0 authentication for secure access.
Limitations
- Only content visible to the admin user who authorizes the connector is indexed. Private pages not accessible to the admin will not be indexed.
- Sections within a content page that have special permissions (different from the page default) are ignored and only content visible to the default groups is indexed.
- Incremental crawls aren't supported due to API limitations.
- Webhooks must be available in your LumApps tenant. If webhook registration fails, changes appear after the next full crawl.
- Webhooks don't cover identity or comment changes. If comment indexing is enabled, comment changes wait for the next full crawl.
- Indexing of Spaces requires API v2, which is not currently supported.
Crawling strategy
Glean enables content webhooks by default and uses the following crawl types to keep content and permissions up to date.
| Crawl type | Full crawl | Incremental crawl | People data | Activity | Update rate | Webhook | Notes |
|---|---|---|---|---|---|---|---|
| Content | Yes | No | No | No | Frequent | Yes | Full crawls run hourly by default. Webhooks send creates, updates, deletes, and archives for pages, communities, and posts in near real time. |
| Identity | Yes | No | Yes | No | Frequent | No | Users and groups fetched to determine permissions |
Crawls are performed using the admin access token, which has access to all content visible to the admin in the LumApps instance.