Skip to main content
Learn how Lumos combines identity, account, and permission data to automate access management.

​
Understand the foundation of Lumos

Lumos is an Autonomous Identity Platform designed to centralize and automate identity management across a wide range of applications—SaaS, on-premise, and beyond. The platform aggregates identity data from various authoritative sources (HRIS, Identity Providers, etc.) and correlates them with user “accounts” and “permissions” in different target systems.

​
Core concepts in Lumos

  1. Identities: Represent real-world individuals (employees, contractors, partners, etc.). Often sourced from HRIS (e.g., Workday), an IdP (e.g., Okta), or other authoritative systems.
  2. Accounts: Represent a user’s profile or login in a specific application (e.g., an account in Salesforce, Microsoft 365, GitHub, etc.).
  3. Permissions: Represent the permissions, roles, licenses, or groups within an application that can be assigned to (or unassigned from) accounts. Examples include a Slack channel membership, an Office 365 license, a GitHub repository role, etc.
  4. Titles, Teams, Managers: These are attributes associated with Identities. They help define organizational structure and can be used in provisioning policies (e.g., “All members of the Engineering team get a GitHub Enterprise license”).
With Lumos, administrators and architects can define which permissions individuals need, based on policies that reference identity attributes (title, department, manager, etc.). Lumos then handles the lifecycle of accounts and permissions in the connected systems—creating, updating, deactivating, assigning, and unassigning as needed.

​
Example

“John Doe, reporting to Lisa Barnes, has Admin Access to Production Repo via GitHub Account, assigned to Engineering Department under Tech Division”