From 489ccb8e15e16526b93f7aa2961111b4017f171a Mon Sep 17 00:00:00 2001
From: Vlad Matsiiako <78047717+vmatsiiako@users.noreply.github.com>
Date: Tue, 29 Oct 2024 21:57:50 -0700
Subject: [PATCH] fix link in docs

---
 docs/documentation/platform/identities/machine-identities.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/documentation/platform/identities/machine-identities.mdx b/docs/documentation/platform/identities/machine-identities.mdx
index 98d654c22..b4a18708c 100644
--- a/docs/documentation/platform/identities/machine-identities.mdx
+++ b/docs/documentation/platform/identities/machine-identities.mdx
@@ -20,7 +20,7 @@ Key Features:
 
 A typical workflow for using identities consists of four steps:
 
-1. Creating the identity with a name and [role](/documentation/platform/role-based-access-controls) in Organization Access Control > Machine Identities.
+1. Creating the identity with a name and [role](/documentation/platform/access-controls/role-based-access-controls) in Organization Access Control > Machine Identities.
    This step also involves configuring an authentication method for it.
 2. Adding the identity to the project(s) you want it to have access to.
 3. Authenticating the identity with the Infisical API based on the configured authentication method on it and receiving a short-lived access token back.