From 6054642205c27b085b39e97c9c827bb9063a1647 Mon Sep 17 00:00:00 2001 From: Amit Lichtenberg Date: Tue, 21 May 2024 11:38:49 +0300 Subject: [PATCH] Small typo fix on the way --- docs/reference/IBAC-Overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/IBAC-Overview.mdx b/docs/reference/IBAC-Overview.mdx index c37d16a31..729784d0f 100644 --- a/docs/reference/IBAC-Overview.mdx +++ b/docs/reference/IBAC-Overview.mdx @@ -68,7 +68,7 @@ so when secure access becomes easy, it's also more prevalent, leading to fewer s Intent-based access control doesn't fly in the face of organizational security policies, and it certainly doesn't replace them. IBAC aligns access controls with the needs of the organization. -It captures and makes explicit the *intents* of developers and their the code, +It captures and makes explicit the *intents* of developers and their code, enables processes for acting on those intents to allow or deny access, and makes explicit the enforcement that's actually put in place. One org might decide that it's best to automatically approve all intents once they undergo code review and apply