From 29452a811d261fff9d980a1da7cd49dbb80090e6 Mon Sep 17 00:00:00 2001 From: Nick Amoscato Date: Wed, 1 May 2024 19:52:47 -0400 Subject: [PATCH] docs: fix inherited role select permission example --- docs/docs/auth/authorization/inherited-roles.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs/auth/authorization/inherited-roles.mdx b/docs/docs/auth/authorization/inherited-roles.mdx index 6c2e1d98a7fec..ff67aec5dc2c8 100644 --- a/docs/docs/auth/authorization/inherited-roles.mdx +++ b/docs/docs/auth/authorization/inherited-roles.mdx @@ -172,11 +172,11 @@ Let's take the example of an `users` table with the following columns: 2. `name` - Text 3. `email` - Text -There are two roles defined namely `employee` and `manager`. +There are two roles defined: -1. User role - The user role will be able to access all columns of _**their row**_ when the session variable +1. `user` - The user role will be able to access all columns of _**their row**_ when the session variable `X-Hasura-User-Id` is equal to the `id`. -2. Anonymous role - The anonymous role will be able to access only the `id` and `name` columns of all the users. +2. `anonymous` - The anonymous role will be able to access only the `id` and `name` columns of all the users. Let's create a new inherited role called `user_anonymous_inherited_role` which inherits from the `user` and the `anonymous` roles.