Knowledge Hub: Access Reviews

Last updated: May 18, 2026

How to use Knowledge Hub to customize AI suggestions during access reviews.

Key Use Cases

  1. Domain-level context — Add context relevant to all reviewers and all apps. E.g., "IT team members having elevated admin access to internal tools is expected" or "Contractors are those whose emails begin with ext_ and their access should be scrutinized."

  2. App-level context — Scope context to specific apps within your environment. E.g., for Salesforce: "Sales managers are expected to have Report Builder access." Or for Figma: "Engineers should only have developer licenses."

How to Scope Context

  • Domain-wide — Rules that apply across all apps for your organization (e.g., "Users on leave should have access suspended across all non-essential apps").

  • Domain-app level — Rules scoped to a specific app. This is the most common and impactful scoping level.

Note: If you add domain-wide context for Access Reviews, it may also be picked up by other Lumos agents like Albus — e.g., "IT team having elevated access is okay" flows into both agents.

Examples

App

Knowledge Hub Entry

—

Apply less scrutiny to basic access to apps. Examples include viewer-level permissions and initial collaborator roles.

Figma

Webinar marketing can have full Figma license.

Slack

Single or multi-channel guests should only be flagged if they are inactive.

Semgrep

Do not consider any activity data for this app. The activity data is too sparse and unreliable. No rejects should be flagged because of inactivity.

Quality Check

After adding or editing context:

  • [ ] Re-sync the review — verify AI suggestions update accordingly

  • [ ] Check that AI insights and decision suggestions match your context intent

  • [ ] Test domain-app scoped context vs. domain-wide to confirm correct retrieval