Jingga/User-Guide
1
0
Fork 0
mirror of https://github.com/Karaka-Management/User-Guide.git synced 2026-01-10 20:08:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update permissions.md

Browse Source
This commit is contained in:
Dennis Eichhorn 2022-03-18 13:44:12 +01:00 committed by GitHub
parent 4e114186d7
commit 23b8b89517
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
administration/permissions.md
View File

@ -39,7 +39,7 @@ These permissions can be assigned on multiple levels (descending in the followin
* Unit/Organization * Unit/Organization
* Application * Application
* Module * Module
* Type * Category
* Element * Element
* Component * Component
@ -55,9 +55,9 @@ Every unit/organization can have multiple applications. One application could fo
Different modules provide different features, by defining the modules permissions can be managed more granular. A sales person for example doesn't need access to R&D for example. Different modules provide different features, by defining the modules permissions can be managed more granular. A sales person for example doesn't need access to R&D for example.
### Type ### Category
Often a module provides multiple features or functionalities. The type can be used to give accounts even more specific permissions. In a organization an account may be allowed to create new invoices for customers but is not allowed to create a new customer. Often a module provides multiple features or functionalities. The category can be used to give accounts even more specific permissions. In a organization an account may be allowed to create new invoices for customers but is not allowed to create a new customer.
### Element ### Element