mirror of
https://github.com/Part-DB/Part-DB-server.git
synced 2025-08-07 11:44:38 +02:00
Created Concepts (markdown)
parent
c339c41254
commit
d5d1c13ba3
1 changed files with 16 additions and 0 deletions
16
Concepts.md
Normal file
16
Concepts.md
Normal file
|
@ -0,0 +1,16 @@
|
|||
# Concepts
|
||||
This page explains the different concepts of Part-DB and what their intended use is
|
||||
|
||||
## Part managment
|
||||
|
||||
|
||||
## User System
|
||||
### User
|
||||
Each person which should be able to use Part-DB (by logging in) is represented by an user entity, which defines things like access rights, the password, and other things. For security reasons, every person which will use Part-DB should use its own personal account with an secret password. This allows to track activity of the users via the log.
|
||||
|
||||
There is a special user called `anonymous`, whose access rights are used to determine what an non-logged in user can do. Normally the anonymous user should be the most restricted user.
|
||||
|
||||
For simplification of access management users can be assigned to groups.
|
||||
|
||||
### Group
|
||||
A group is entity, to which users can be assigned to. This can be used to logically group users by for example organisational structures and to simplify permissions managment, as you can define groups with access rights for common use cases and then just assign users to them, without the need to change every permission on the users individually.
|
Loading…
Add table
Add a link
Reference in a new issue