From a614084f0851c09c4ed03d8e76c899ce61cf4e8c Mon Sep 17 00:00:00 2001
From: YapWC <34093361+YapWC@users.noreply.github.com>
Date: Fri, 25 Apr 2025 02:50:32 +0800
Subject: [PATCH] Update Authentik Step 5 (#305)

Making it more explicit
---
 src/pages/selfhosted/identity-providers.mdx | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/src/pages/selfhosted/identity-providers.mdx b/src/pages/selfhosted/identity-providers.mdx
index 32e5c360..43deab77 100644
--- a/src/pages/selfhosted/identity-providers.mdx
+++ b/src/pages/selfhosted/identity-providers.mdx
@@ -536,17 +536,28 @@ In this step, we will add `Netbird` service account to `authentik Admins` group.
 </p>
 
 #### Step 5: Create a authentication flow for device token authentication
-Navigate to Authentik admin interface > Flows & Stages > Flows > Create
+
+- Navigate to authentik  admin interface
+- Click `Flows and Stages` on the left menu, then click `Flows` then `Create`
+- Fill in the form with the following values and click `Create`
+    - Name: `default-device-code-flow`
+    - Title: `Device Code Flow`
+    - Designation: `Stage Configuration`
+    - Authentication: `Require authentication`
+
 <p>
     <img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-new-device-flow.png" alt="high-level-dia" className="imagewrapper-big"/>
 </p>
 
+- Navigate to authentik  admin interface
+- Click `System` on the left menu, then click `Brands`
+- Click on the edit button of domain `authentik-default`
+- Under Default flows set Device code flow to `default-device-code-flow`
+- Click `Update`
 
-Then go to: System > Brands > Edit used default > Default Flows > set **Device code flow** to newly created device flow
 <p>
     <img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-brand-device-flow.png" alt="high-level-dia" className="imagewrapper-big"/>
 </p>
-Press `Update`
 
 Your authority OIDC configuration will be available under: