Skip to main content

​
Background

Albus is the AI assistant built into Lumos. From Albus Chat, you can ask questions about your apps, accounts, entitlements, and identities in plain language, generate access matrices for role mining, and get answers backed by your live Lumos data. This article covers what Albus Chat does and how to use it. To give Albus persistent context it can reuse across conversations, see the Knowledge Hub article.

​
When to use Albus Chat

  • Understand who has access to what across your apps without building a report.
  • Run a role-mining access matrix for a team or application.
  • Investigate identities, entitlements, or access-request history.
  • Produce a chart or an exportable summary for a stakeholder or an audit.

​
Prerequisites

  • Albus is enabled for your domain. It is on by default for most customers; if you do not see Albus, contact your Lumos account team.
  • Your integrations are connected and synced, so Albus has data to work with.

​
How to use Albus Chat

Albus chat landing screen

Albus chat: "What can I help you with?"

  1. Navigate to Albus in the Lumos left navigation.
  2. Enter your question in plain language, for example “Show the access matrix for the Sales team.”
  3. Review the answer. Albus considers all available identity attributes automatically, so you do not need to select specific attributes first.
  4. To add context for a question, attach a file with the + button in the chat composer. Supported formats are text and data files: CSV, TSV, TXT, JSON, Markdown, YAML, XML, and logs (up to 10 MB each, 5 files per message). Attached files are scoped to that conversation.
  5. To visualize a result, ask Albus for a chart. Albus renders interactive charts (bar, horizontal bar, line, area, and donut) inline.
  6. To share a result, export it to PDF or Markdown.
Access matrix generated in Albus chat

Access matrix generated in Albus chat

​
Visualize your data

Albus can turn an answer into a visual, rendered inline in the conversation:
  • Interactive charts — bar, horizontal bar, line, area, donut, and pie. Hover any bar or point to see its value.
  • Diagrams — flowcharts, sequence diagrams, and relationship or hierarchy graphs, such as access and org graphs.
  • Structured reports and artifacts — formatted Markdown reports and tables, plus downloadable file and text artifacts you can take out of the chat for a ticket, a deck, audit evidence, or a Slack share.
You can export any result, including charts and full reports, to PDF or Markdown. A graph visualization Albus rendered inline Hovering a bar in an interactive chart

​
What data Albus can access

Albus is grounded in the real assignment, usage, and access-request data already in your Lumos environment, so it knows your tools, teams, and policies. It can draw on:
  • Your app and integration inventory, including multi-instance apps.
  • Accounts and identities, both human and non-human (service principals, IAM roles, and machine credentials).
  • Entitlements, permissions, roles, and group memberships across connected apps.
  • Identity attributes from your HR source of truth, such as department, worker type, employment status, and manager relationships.
  • Assignment and activity signals, including who has access and last-login or inactivity data.
  • Access requests, approvals, and approver history.
  • Knowledge Hub context you have added, such as policies, naming conventions, and documentation.

​
Limitations

  • Albus answers from data synced to Lumos. If an integration is not connected, Albus cannot see it.
  • Newly synced data may take time to appear in Albus after a sync completes.
  • Albus Chat is available to users with the Admin role.
Questions? Contact your Lumos account team or open a support ticket.