Invitation-only enrollment in authentik
Onboarding contractors, partners or customers by invitation instead of open signup: the invitation stage, single-use and expiring links, prefilled attributes and binding the enrollment flow to policies.

Specific login, enrollment and recovery flows and the policies that decide them, from invitations and password rules to GeoIP, reputation and branding per domain.
Onboarding contractors, partners or customers by invitation instead of open signup: the invitation stage, single-use and expiring links, prefilled attributes and binding the enrollment flow to policies.
Building a recovery flow that does not let an email link alone take over an account: email verification, MFA before reset, account enumeration settings and recovery for administrators.
Requiring users to change their password at the next sign-in, for example after a migration or a leak: the documented flow pattern, user attributes and communication.
Writing Python expression policies for rules the built-in policies cannot express: available context, group and attribute checks, the 2026.2 change from ak_groups to groups, and locking down who may edit expressions.
Blocking or challenging logins by country, ASN, distance from recent logins or impossible travel: the bundled GeoIP database, updating it, session binding and what breaks if the database is missing.
Responding to failed logins and suspicious requests with reputation scores: CAPTCHA for low-reputation clients, deny bindings, notifications and tuning to avoid locking out shared IP addresses.
Setting password rules auditors ask about: length and complexity, Have I Been Pwned and zxcvbn checks, expiry, Enterprise password history, and offline alternatives in air-gapped networks.
Adding a CAPTCHA to login or enrollment flows: supported providers including the self-hostable Cap provider added in 2026.8, JSON verification requests, and protecting CAPTCHA settings from tampering.
Giving each domain or customer its own login look and default flows with brands: logo, favicon, backgrounds, custom CSS from 2025.4, default flows per brand, and external user redirects.
Granting contractors or incident responders access that ends on its own: binding expiry dates added in 2026.8 for policies, groups and users, and how expired bindings behave.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.