Skip to main content

Organization Setup

This guide covers configuring and managing your organization in LumoAuth.


Getting Your Organization​

When you sign up for LumoAuth, you create an organization during onboarding. Your organization is immediately available at:

https://app.lumoauth.dev/orgs/{your-organization-slug}/portal/

Your organization ID is a URL-safe identifier (e.g., acme-corp) that you chose during signup.


Organization Configuration​

Configure your organization settings through the organization portal at /orgs/{orgId}/portal/.

The portal dashboard, the landing page of the organization portal

Sign-in settings​

Navigate to Security → Sign-in settings (/orgs/{orgId}/portal/settings/authentication) to configure:

SettingDescription
Identity methodsPasskeys & biometrics (including the FIDO Metadata Service check of authenticators) and Require push authentication
Login flowEmail-first login, magic link login
Password standardsTemplate or custom rules: minimum length and complexity requirements
Auth lifecycleSession timeout, breached-password checks, password rotation
Platform securityOAuth security and developer-facing protocol features
Progressive profilingAsk for profile details gradually across several sign-ins instead of all at registration
MFA policyOff, optional, risk-based or required MFA; allowed factors, minimum strength, grace period and trusted devices (see MFA)
Admin API keysScoped keys for programmatic access to the Admin API (managed under Applications & developer tools → API keys)

Self-registration is switched on or off with Enable self registration under Settings → Login page & emails → Login page, not on this page.

The Sign-in settings page with its section tabs

Identity Providers​

Configure external identity providers for your organization:

Provider TypeConfiguration Path
Social LoginSocial login section of /orgs/{orgId}/portal/integrations (Add provider)
SAML 2.0 IdPEnterprise SSO (SAML) section of /orgs/{orgId}/portal/integrations, or /orgs/{orgId}/portal/saml-idps
OIDC FederationEnterprise SSO (OIDC) section of /orgs/{orgId}/portal/integrations, or /orgs/{orgId}/portal/oidc-idps
LDAP / Active DirectoryDirectory sync (LDAP/AD) section of /orgs/{orgId}/portal/integrations

All of these are under Settings → Integrations.

The Integrations page with its section tabs and the Enterprise SSO (SAML) section

Adaptive Authentication​

Configure risk-based authentication under Security → Adaptive security (/orgs/{orgId}/portal/settings/adaptive-auth):

  • The adaptive security engine on/off switch
  • Risk score thresholds
  • Detection signals such as impossible travel, new country and IP reputation
  • Network guard (Tor and datacenter/VPN blocking)
  • Trusted IP ranges

The Adaptive security page with the engine toggle and risk thresholds

See Adaptive MFA for details.


Organization Roles​

Every organization starts with one system role, Tenant Admin, which holds every admin permission and cannot be deleted. Any other administrator role is one that you create under Access control → Roles & permissions (Create role). Set an access level per area, or pick Read-only, Editor or Administrator under Start from and adjust. Typical roles teams create:

RoleDescriptionTypical Permissions
Tenant Admin (system role)Full control over the organizationAll organization operations
A user managerManage users and assignmentsCreate/edit/delete users, assign roles
An application managerManage OAuth and SAML applicationsCreate/edit/delete applications
An auditorRead-only access to logsView audit logs, view users

See How the admin permissions work.

Assigning Organization Admins​

  1. Go to Identity → Users (/orgs/{orgId}/portal/users)
  2. Open a user and switch to the Roles tab
  3. Tick the organization admin role (the system role named Tenant Admin) and click Save changes

The Roles tab of a user's page with the available roles as checkboxes


Organization Settings via API​

You can also manage organization settings from code, using the Admin API:

# Update organization authentication settings.
# Note: /api/v1/admin/settings is read-only (GET). Update each settings
# group at its own sub-resource, e.g. .../settings/authentication.
curl -X PATCH https://app.lumoauth.dev/orgs/acme-corp/api/v1/admin/settings/authentication \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{
"session_timeout": 1209600,
"social_login_enabled": true
}'

The Admin settings API is split into per-group sub-resources, each supporting GET (read) and PATCH/PUT (update):

GroupPath
Authentication/orgs/{orgId}/api/v1/admin/settings/authentication
Security/orgs/{orgId}/api/v1/admin/settings/security
Email/orgs/{orgId}/api/v1/admin/settings/email
General/orgs/{orgId}/api/v1/admin/settings/general

GET /orgs/{orgId}/api/v1/admin/settings returns all groups in one aggregate response.

The MFA policy has its own endpoint, GET/PUT /orgs/{orgId}/api/v1/admin/policies/mfa — see the MFA API.

See the Admin API documentation for the full list of available endpoints.


Organization Data Model​

Each organization owns the following resources: