User roles and permissions in No-Code - Step-by-Step Execution

Concept Flow - User roles and permissions

Start

↓

Define Roles

↓

Assign Permissions to Roles

↓

Assign Roles to Users

↓

User Tries Action

↓

Check User's Role Permissions

Yes No↓

Allow

↓

Action

This flow shows how roles are defined with permissions, assigned to users, and then checked when a user tries to perform an action.

Execution Sample

No-Code

Roles = {"Admin": ["edit", "delete"], "Viewer": ["view"]}
Users = {"Alice": "Admin", "Bob": "Viewer"}
UserAction = "delete"
User = "Bob"
# Check if Bob's role allows 'delete'

This example checks if user Bob, who is a Viewer, can perform the 'delete' action.

Analysis Table

Step	User	User Role	Action Tried	Permission Check	Result
1	Bob	Viewer	delete	Is 'delete' in Viewer permissions? No	Deny action
2	Alice	Admin	delete	Is 'delete' in Admin permissions? Yes	Allow action
3	Bob	Viewer	view	Is 'view' in Viewer permissions? Yes	Allow action
4	Alice	Admin	edit	Is 'edit' in Admin permissions? Yes	Allow action
5	Bob	Viewer	edit	Is 'edit' in Viewer permissions? No	Deny action
6	End	-	-	-	No more actions to check

💡 All user actions checked against their role permissions; process ends.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
User	-	Bob	Alice	Bob	Alice	Bob	-
User Role	-	Viewer	Admin	Viewer	Admin	Viewer	-
Action Tried	-	delete	delete	view	edit	edit	-
Permission Check	-	No	Yes	Yes	Yes	No	-
Result	-	Deny	Allow	Allow	Allow	Deny	-

Key Insights - 3 Insights

Why can't Bob perform the 'delete' action even though he is a user?

Because Bob's role is 'Viewer', which does not include the 'delete' permission as shown in execution_table step 1.

How does the system decide if an action is allowed or denied?

It checks if the action is listed in the permissions of the user's assigned role, as seen in the Permission Check column of the execution_table.

Can a user have multiple roles at the same time in this example?

No, each user has only one role assigned, simplifying permission checks as shown in the variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result when Bob tries the 'view' action at step 3?

A Deny action

B No action

C Allow action

D Error

💡 Hint

Check the 'Result' column at step 3 in the execution_table.

At which step does the permission check confirm that 'edit' is allowed for Alice?

A Step 4

B Step 5

C Step 2

D Step 1

💡 Hint

Look at the 'User' and 'Action Tried' columns to find when Alice tries 'edit'.

If Bob was assigned the 'Admin' role, what would be the result when he tries 'delete' at step 1?

A Deny action

B Allow action

C No action

D Error

💡 Hint

Refer to the permissions of 'Admin' role in the execution_sample and execution_table.

Concept Snapshot

User roles group permissions.
Permissions define allowed actions.
Users get assigned roles.
When a user acts, system checks role permissions.
If allowed, action proceeds; else denied.

Full Transcript

User roles and permissions work by grouping allowed actions into roles. Each user is assigned a role. When a user tries to do something, the system checks if that action is allowed by the user's role. If yes, the action is allowed; if not, it is denied. For example, a Viewer role may only have permission to view, while an Admin role can edit or delete. This system helps control who can do what in an application.

Practice

1. What is the main purpose of assigning roles to users in a system?

easy

A. To track user login times

B. To store user passwords securely

C. To group permissions and simplify access control

D. To display user profile pictures

Solution

1. Step 1: Understand the concept of roles

   Roles are used to group permissions, making it easier to manage what users can do.

2. Step 2: Identify the purpose of roles

   By grouping permissions, roles simplify access control instead of assigning permissions individually.

3. Final Answer:

   To group permissions and simplify access control -> Option C

4. Quick Check:

   Roles group permissions = simplify access control [OK]

Hint: Roles group permissions to manage access easily [OK]

Common Mistakes:

• Confusing roles with user profile features
• Thinking roles store passwords
• Assuming roles track login times

2. Which of the following is the correct way to assign a permission called edit_post to a role named Editor?

easy

A. Add edit_post permission to the Editor role

B. Remove all permissions from the Editor role

C. Create a new role called edit_post

D. Assign edit_post permission directly to users only

Solution

1. Step 1: Understand permission assignment

   Permissions should be added to roles to control access for all users with that role.

2. Step 2: Identify correct assignment

   Adding edit_post permission to the Editor role allows all editors to edit posts.

3. Final Answer:

   Add edit_post permission to the Editor role -> Option A

4. Quick Check:

   Permissions belong to roles, not just users [OK]

Hint: Permissions go to roles, not only users [OK]

Common Mistakes:

• Assigning permissions only to users
• Confusing permission names with role names
• Removing permissions accidentally

3. If a user has the role Viewer with permission read_only, what action can they perform?

medium

A. Manage user roles

B. Edit and delete content

C. Create new content

D. Only view content without changes

Solution

1. Step 1: Understand the read_only permission

   This permission allows viewing content but prevents any changes.

2. Step 2: Match permission to user actions

   A user with read_only can only see content, not edit, create, or manage roles.

3. Final Answer:

   Only view content without changes -> Option D

4. Quick Check:

   read_only means view only [OK]

Hint: read_only means no changes allowed [OK]

Common Mistakes:

• Assuming read_only allows editing
• Confusing viewing with managing roles
• Thinking read_only allows content creation

4. A user with the role Admin cannot delete posts. What is the most likely reason?

medium

A. The Admin role lacks the delete_post permission

B. The user forgot their password

C. The system does not allow any deletions

D. The user has multiple roles

Solution

1. Step 1: Check role permissions

   If an admin cannot delete posts, the delete_post permission is likely missing from the Admin role.

2. Step 2: Rule out unrelated causes

   Password issues or multiple roles do not prevent permissions if assigned correctly; system-wide deletion block is rare.

3. Final Answer:

   The Admin role lacks the delete_post permission -> Option A

4. Quick Check:

   Missing permission = no action allowed [OK]

Hint: Missing permission means action blocked [OK]

Common Mistakes:

• Blaming password issues for permission problems
• Assuming multiple roles cause denial
• Ignoring role permission settings

5. You want to create a new role called Content Manager that can create, edit, and delete posts but cannot manage user roles. Which permissions should you assign?

hard

A. manage_users, edit_post, delete_post

B. create_post, edit_post, delete_post

C. create_post, manage_users

D. view_post, edit_post

Solution

1. Step 1: Identify required permissions for content management

   Creating, editing, and deleting posts require create_post, edit_post, and delete_post permissions.

2. Step 2: Exclude user management permissions

   Since managing user roles is not allowed, manage_users should not be assigned.

3. Final Answer:

   create_post, edit_post, delete_post -> Option B

4. Quick Check:

   Content management = create, edit, delete posts only [OK]

Hint: Assign only content permissions, exclude user management [OK]

Common Mistakes:

• Including user management permissions by mistake
• Missing delete permission
• Assigning view permission only