From ac3b9c25ddd2a7c59fabd11209f627354a467cb7 Mon Sep 17 00:00:00 2001 From: Daniel Hougaard Date: Sat, 14 Sep 2024 00:33:52 +0400 Subject: [PATCH] Update permissions.mdx --- docs/internals/permissions.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/internals/permissions.mdx b/docs/internals/permissions.mdx index 1f9aa0602..3eb7059d2 100644 --- a/docs/internals/permissions.mdx +++ b/docs/internals/permissions.mdx @@ -5,9 +5,9 @@ description: "Infisical's permissions system provides granular access control." ## Summary -The Infisical permissions system is based on a role-based access control (RBAC) model. The system allows you to define roles and assign them to users. Each role has a set of permissions that define what actions a user can perform. +The Infisical permissions system is based on a role-based access control (RBAC) model. The system allows you to define roles and assign them to users and machines. Each role has a set of permissions that define what actions a user can perform. -Permissions are built on a subject-action-object model. The subject is what the permission is being applied to, the action is what the permission allows, and the object is what the permission is being applied to. +Permissions are built on a subject-action-object model. The subject is the resource permission is being applied to, the action is what the permission allows. An example of a subject/action combination would be `secrets/read`. This permission allows the subject to read secrets. Currently Infisical supports 4 actions: