LUCION ID
One account that follows you.
Your profile, language, time zone, security settings, devices, memberships, and consent travel with you across Lucion.
Explore Lucion IDIDENTITY, AUTHORIZATION & TRUST
Lucion Identity gives you one trusted account across Lucion — with authentication, privacy, permissions, organizations, and control designed in from the start.

BUILT FOR THE LUCION ECOSYSTEM
ONE TRUST LAYER
Lucion Identity is not just a sign-in screen. It is the shared identity, permission, organization, developer-access, and audit layer for Lucion and Helios.
LUCION ID
Your profile, language, time zone, security settings, devices, memberships, and consent travel with you across Lucion.
Explore Lucion IDIDENTITY CONSOLE
Review sessions, trusted devices, app access, organization memberships, security events, and the permissions you have granted.
Explore Identity ConsoleORGANIZATIONS
Manage people, groups, roles, application access, policies, verified domains, invitations, and audit history from one place.
Explore OrganizationsDEVELOPER
Register applications, request precise scopes, configure redirects and webhooks, and integrate through Lucion Identity APIs.
Explore DeveloperSECURITY BY DESIGN
Every Lucion Identity decision is designed around explicit authorization: a person, an organization, an application or agent, and the exact permissions granted for that action.
LUCION IDENTITY FOR ORGANIZATIONS
A company joins once, creates its organization structure, then decides which people and groups can use each Lucion or Helios application.
Illustrative preview · sample data
LUCION IDENTITY DEVELOPER
Register applications, define redirect URIs, request scopes, publish webhooks, and integrate with one consistent identity contract across Lucion.
Open DeveloperGET /oauth/authorize
?client_id=lid_client_...
&redirect_uri=https://calendar.lucionglobal.com/auth/callback
&scope=identity.profile.read calendar.events.write
&state=...LYRA + LUCION AI
Lyra can act across Lucion only through delegated authorization. Every request is tied to a user, an organization, an allowed app, and specific scopes — and every action can be reviewed later.
IDENTITY CONSOLE
Security, sessions, organizations, app permissions, and AI activity remain understandable instead of disappearing into separate systems.
Illustrative preview · sample data
calendar.events.write2 min agoFREQUENTLY ASKED QUESTIONS
The General Availability release distinguishes live production capabilities from independently gated server capabilities.
Lucion Identity is the shared identity, organization, authorization, developer-access, and audit layer designed for Lucion and Helios products.
A Lucion ID is the individual account that carries profile, language, time zone, security settings, devices, organization memberships, app permissions, and consent across supported Lucion experiences.
Yes. After you verify your email, you can create a password-based Lucion ID and use that password as a full sign-in method. Passkeys remain available when you want the convenience of device-based sign-in.
Organizations can be modeled with members, groups, roles, app access, policies, verified domains, invitations, and audit history so access follows the company structure instead of being recreated app by app.
Lyra is designed to use delegated authorization. A request must be tied to a user, organization, approved application, required scopes, and an auditable outcome rather than receiving universal access.
Yes. Identity Developer defines application registration, exact redirect URIs, scopes, OAuth/OIDC, signed ID tokens, webhooks, and API contracts. Production credentials remain hash-only and are shown only once.
ONE IDENTITY. EVERY LUCION EXPERIENCE.
6.6.6 supports verified-email enrollment, passkey or password authentication, secure server sessions, recovery safeguards, OAuth/OIDC, organization authorization, and scoped Lyra delegation behind explicit production gates.