Hi Glean Community,
Quick question from our side: we’ve noticed that GitHub Wiki ingestion requires a two-step authentication process for each user - first connecting GitHub, and then granting additional permissions specifically for wikis.Could you help us understand why this additional layer is necessary from a technical and security stand point? Given that these wikis are often shared org-wide, the individual re-auth step is causing friction and limiting adoption across teams.
Also, is there any way we can simplify this flow -perhaps by allowing admin-level authorization or using a service account for org-wide wiki access?
Appreciate any clarity or options you can share
