Skip to content

Commit 00f356b

Browse files
juliafmorgadoCathPagiamNoah1seokho-son
authored
Add content/en/role-based access control(RBAC) (#1503)
* Add content/en/role-based access control(RBAC) Signed-off-by: Julia Furst Morgado <[email protected]> Signed-off-by: Catherine Paganini <[email protected]> Signed-off-by: Noah Ispas <[email protected]> Signed-off-by: Seokho Son <[email protected]> Co-authored-by: Julia Furst Morgado <[email protected]> Co-authored-by: Catherine Paganini <[email protected]> Co-authored-by: Noah Ispas <[email protected]> Co-authored-by: Seokho Son <[email protected]>
1 parent 439e96c commit 00f356b

File tree

2 files changed

+28
-0
lines changed

2 files changed

+28
-0
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: Role-Based Access Control (RBAC)
3+
status: Completed
4+
category: concept
5+
---
6+
7+
## What it is
8+
9+
Role-based access control (RBAC) is a method to regulate system and resource access based on individual user roles within an organization.
10+
Each job function has a specific role and permissions.
11+
For instance, a marketing team member may have permission to view sales deals in the pipeline (*read* permission) but won't be allowed to edit them (*write* permission).
12+
Sales and marketing have different permissions based on their roles, hence role-based access control, and the same applies to roles within engineering teams.
13+
14+
## Problem it addresses
15+
16+
Individually managing access permissions of multiple users across various system resources and data can be complex.
17+
After all, each user likely needs access to a different set of resources.
18+
Let's say an organization has 500 developers (users) and 300 resources with varying permission levels (read, write, and no access). The administrator must ensure each user has the correct permissions for all 300 resources.
19+
RBAC simplifies the process by providing predefined access control based on role groups.
20+
21+
22+
## How it helps
23+
24+
RBAC provides granular control over user permissions within software systems.
25+
Depending on their roles, team members can modify a section, only view it, or have no access at all.
26+
This granular permission allocation allows team members with different roles to work on the same system while minimizing risk.

wordlist.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,6 +138,7 @@ oliveira
138138
opencontainers
139139
orchestrator
140140
overdemand
141+
overprivileged
141142
paas
142143
pathconverter
143144
pavel
@@ -152,6 +153,7 @@ py
152153
pypi
153154
pyspelling
154155
ramer
156+
RBAC
155157
rdbms
156158
readme
157159
replicable

0 commit comments

Comments
 (0)