mirror of
https://github.com/Karaka-Management/oms-Admin.git
synced 2026-02-01 22:28:42 +00:00
move introduction to lang folder
This commit is contained in:
parent
b29362f55e
commit
bc7447f166
|
|
@ -12,10 +12,10 @@ The id (unique identifier) is automatically generated.
|
|||
|
||||
### Type
|
||||
|
||||
An account can be either a:
|
||||
An account can be either a:
|
||||
|
||||
* `Person`
|
||||
* or a `Organization`
|
||||
* `Person`
|
||||
* or a `Organization`
|
||||
|
||||
Both types can have the same permissions and functionality. This can be helpful for a lot of modules that rely on organizations or companies (e.g. a sales module that handles people as customers but also companies as customers).
|
||||
|
||||
|
|
@ -25,16 +25,16 @@ An account has the following status:
|
|||
|
||||
* Active
|
||||
* Inactive (usually used for long inactive accounts)
|
||||
* Timeout (usually used for timeouts in case of bad behaviour which will be automatically revoked after a certain time)
|
||||
* Banned (usually used to disable accounts for an indefinate time)
|
||||
* Timeout (usually used for timeouts in case of bad behavior which will be automatically revoked after a certain time)
|
||||
* Banned (usually used to disable accounts for an indefinite time)
|
||||
|
||||
### Username
|
||||
|
||||
Name of the account which can be shown in various places insdead of the full name.
|
||||
Name of the account which can be shown in various places instead of the full name.
|
||||
|
||||
### Name1 - Name3
|
||||
|
||||
The name of the account. In some cases 3 names are necessary such as first name, middle name and family name. If more than 3 names are required you have to additionaly put them into one of the 3 name fields.
|
||||
The name of the account. In some cases 3 names are necessary such as first name, middle name and family name. If more than 3 names are required you have to additionally put them into one of the 3 name fields.
|
||||
|
||||
### Email
|
||||
|
||||
|
|
@ -68,19 +68,19 @@ The module this permission is set for. Leave empty to address all modules
|
|||
|
||||
### Type
|
||||
|
||||
The type is a `module` specific subpart which only should be set if the module is defined in the permission. For further information what kind of types are available for a module please refere to the module specific documentation. Usually it referes to a single page of a module.
|
||||
The type is a `module` specific subpart which only should be set if the module is defined in the permission. For further information what kind of types are available for a module please refer to the module specific documentation. Usually it refers to a single page of a module.
|
||||
|
||||
### Element
|
||||
|
||||
The element is a `module` and `type` specific subpart which only should be set if the `type` is defined in the permission. For further information what kind of elements are available for a module and type please refere to the module specific documentation. Usually it referes to a section on a module page.
|
||||
The element is a `module` and `type` specific subpart which only should be set if the `type` is defined in the permission. For further information what kind of elements are available for a module and type please refer to the module specific documentation. Usually it refers to a section on a module page.
|
||||
|
||||
### Component
|
||||
|
||||
The component is a `module`, `type` and `element` specific subpart which only should be set if the `element` is defined in the permission. For further information what kind of components are available for a module, type and element please refere to the module specific documentation. Usually it referes to a single input or option in a module.
|
||||
The component is a `module`, `type` and `element` specific subpart which only should be set if the `element` is defined in the permission. For further information what kind of components are available for a module, type and element please refers to the module specific documentation. Usually it refers to a single input or option in a module.
|
||||
|
||||
### Permission
|
||||
|
||||
The actual permission consists of create (C), read (R), update (U), delete (D), permission (P) options.
|
||||
The actual permission consists of create (C), read (R), update (U), delete (D), permission (P) options.
|
||||
|
||||
#### Create (C)
|
||||
|
||||
|
|
@ -106,7 +106,7 @@ This allows a user to change permissions. Usually a user should also have (C, R,
|
|||
|
||||

|
||||
|
||||
In the groups section you can see all groups that this account is assigned to and you can also add or remove the account to other groups. If you would like to add the account to the same groups as a different account just select the account whos groups you would like to copy and the account will be added to the same groups (one time only, there will be **no relation** between the two accounts.
|
||||
In the groups section you can see all groups that this account is assigned to and you can also add or remove the account to other groups. If you would like to add the account to the same groups as a different account just select the account whose groups you would like to copy and the account will be added to the same groups (one time only, there will be **no relation** between the two accounts.
|
||||
|
||||
## Audit Log
|
||||
|
||||
|
|
|
|||
|
|
@ -12,11 +12,11 @@ The id (unique identifier) is automatically generated.
|
|||
|
||||
### Name
|
||||
|
||||
In some cases it makes sense to put some additional information in the group name. In some cases a group is only for a specific unit or application in such a case it could make sense to prefix the group name e.g. `unitname_groupname` or `appname_groupname`. Group names can be changed any time without any side effects.
|
||||
In some cases it makes sense to put some additional information in the group name. In some cases a group is only for a specific unit or application in such a case it could make sense to prefix the group name e.g. `unitname_groupname` or `appname_groupname`. Group names can be changed any time without any side effects.
|
||||
|
||||
### Description
|
||||
|
||||
Sometimes it makes sense to provide some additional information for a group. In such a case you can add this in the discription field.
|
||||
Sometimes it makes sense to provide some additional information for a group. In such a case you can add this in the description field.
|
||||
|
||||
## Permissions
|
||||
|
||||
|
|
@ -38,19 +38,19 @@ The module this permission is set for. Leave empty to address all modules
|
|||
|
||||
### Type
|
||||
|
||||
The type is a `module` specific subpart which only should be set if the module is defined in the permission. For further information what kind of types are available for a module please refere to the module specific documentation. Usually it referes to a single page of a module.
|
||||
The type is a `module` specific subpart which only should be set if the module is defined in the permission. For further information what kind of types are available for a module please refer to the module specific documentation. Usually it refers to a single page of a module.
|
||||
|
||||
### Element
|
||||
|
||||
The element is a `module` and `type` specific subpart which only should be set if the `type` is defined in the permission. For further information what kind of elements are available for a module and type please refere to the module specific documentation. Usually it referes to a section on a module page.
|
||||
The element is a `module` and `type` specific subpart which only should be set if the `type` is defined in the permission. For further information what kind of elements are available for a module and type please refer to the module specific documentation. Usually it referes to a section on a module page.
|
||||
|
||||
### Component
|
||||
|
||||
The component is a `module`, `type` and `element` specific subpart which only should be set if the `element` is defined in the permission. For further information what kind of components are available for a module, type and element please refere to the module specific documentation. Usually it referes to a single input or option in a module.
|
||||
The component is a `module`, `type` and `element` specific subpart which only should be set if the `element` is defined in the permission. For further information what kind of components are available for a module, type and element please refer to the module specific documentation. Usually it refers to a single input or option in a module.
|
||||
|
||||
### Permission
|
||||
|
||||
The actual permission consists of create (C), read (R), update (U), delete (D), permission (P) options.
|
||||
The actual permission consists of create (C), read (R), update (U), delete (D), permission (P) options.
|
||||
|
||||
#### Create (C)
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Accounts can have the following status:
|
|||
* Banned (login not possible)
|
||||
* Timeout (login possible in x-minutes)
|
||||
|
||||
The status doesn't represent account activity it's only perpose is to allow or disallow the login to the application. Only active accounts can login to the application. It is often necessary to create accounts in the system for ineraction but disallow them to login to the system, this can be achived by simply assigning the inactive status.
|
||||
The status doesn't represent account activity it's only purpose is to allow or disallow the login to the application. Only active accounts can login to the application. It is often necessary to create accounts in the system for interaction but disallow them to login to the system, this can be achieved by simply assigning the inactive status.
|
||||
|
||||
## Group Management
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ In the security section it's possible to define and modify the global security s
|
|||
|
||||
#### Password Regex
|
||||
|
||||
In this field the password strucutre can be defined that is required by every account. Examples are:
|
||||
In this field the password structure can be defined that is required by every account. Examples are:
|
||||
|
||||
##### Password Example 1
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ In this field the amount of retries can be defined until the user login receives
|
|||
|
||||
#### Timeout Period
|
||||
|
||||
In this field the timeout period after inputting a incorrect password too often can be specified. During this period the user cannot login even if the password is correct.
|
||||
In this field the timeout period after inputting a incorrect password too often can be specified. During this period the user cannot login even if the password is correct.
|
||||
|
||||
**Recommended:** `30 minutes`
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user