awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix images in docs

Browse Source
This commit is contained in:
Vladyslav Matsiiako
2024-04-01 09:15:04 -07:00
parent 4a325d6d96
commit 1e4b4591ed
4 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/documentation/platform/access-controls/role-based-access-controls.mdx
View File

@@ -17,7 +17,7 @@ By default, every user and machine identity in a organization is either an **adm
Overall, organization-level access controls are significantly of administrative nature. Access to projects, secrets and other sensitive data is specified on the project level.
![Org member role](../../images/platform/rbac/org-member-role.png)
![Org member role](/images/platform/rbac/org-member-role.png)
## Project-level access controls
@@ -28,7 +28,7 @@ As such:
- **Developers**: This role restricts identities from performing project control actions, updating Approval Workflow policies, managing roles/members, and more.
- **Viewer**: The most limiting bulit-in role on the project level – it forbids user and machine identities to perform any action and rather shows them in the read-only mode.
![Project member role](../../images/platform/access-controls/rbac.png)
![Project member role](/images/platform/access-controls/rbac.png)
## Creating custom roles
@@ -41,4 +41,4 @@ By creating custom roles, you are able to adjust permissions to the needs of you
It is worth noting that users are able to assume multiple built-in and custom roles. A user will gain access to all actions within the roles assigned to them, not just the actions those roles share in common.
</Note>
![project member custom role](../../images/platform/rbac/project-member-custom-role.png)
![project member custom role](/images/platform/rbac/project-member-custom-role.png)