First draft

administration/groups.md

@@ -0,0 +1,11 @@
+# Groups
+
+User groups are used for permission management, process flow as well internally by modules for user grouping. There should be no fear of creating too many user groups. A well structured user group management is key for maintianing permissions and efficient work flow. Don't be afraid to implement many groups for all kinds of purposes. 
+
+User groups can inherit permissions of other user groups. One group can inherit permissions from multiple different groups. It's only important to not create any circular inheritence structures e.g.
+
+    Group A inherits from group B which inherits from group C which however inherits from group A. 
+
+Such a group structure is possible but highly inefficent since all three groups now have the same permissions. Performance wise many groups and complex group relations hardly have any effect.
+
+Permissions in general are following the whitelist approach. You cannot assign permissions that block users from performing or accessing sensitive data and functions, it's only possible to grant users the permissions for accessing these. It's highly recommended to only grant permissions to a group/user in a step-by-step aproach. All changes to groups and permissions for user accounts are logged and can be documented with comments as well documents through file upload.

administration/jobs.md

@@ -0,0 +1,11 @@
+# Jobs
+
+Depending on the server environment it's possible to setup automated jobs/tasks that run at a specific time or interval. This can be useful for automatic updates, backups etc. The application provides a list of default jobs that it can setup. Other modules may provide additional jobs which can also be monitored in the jobs overview.
+
+Simple web servers usually don't allow to register automated jobs. For this purpose jobs can get registered on our own servers which then in return call your application thorugh an api interface. While this enables the use of automated jobs/tasks in situations where this usually wouldn't be possible also is highly dependent on a stable internet connection and server. If possible the local registration of jobs is always prefered. 
+
+Jobs don't have to be used they simply provide a convenient way to automate certain tasks that otherwise have to be performed manually.
+
+Jobs work on all operating systems that are supported by the application. Jobs either rely on the operating system or they can also get executed by the server/socket application. Which of the jobs should get executed by the operating system and which by the socket application can be configured on a job basis.
+
+Failures in jobs are automatically documented and stored on the server. The documentation can be found and downloaded in the jobs.

maintenance/backup.md

@@ -0,0 +1,15 @@
+# Backups
+
+Backups are very important in order to reset or retrive lost data. The application provides an all around eco system for generating and importing exports. Be aware that backups of different versions may not necessarily work with the current installed version which is why it is so important to perform regular backups. 
+
+## Export
+
+Depending on your server environment you can implement automated backups for files and database data. Unscheduled backups can also be generated by a simple click of a button. The backend system automatically generates backup files for the database and local files. In case of limited stroage it's also possible to only backup the database. 
+
+The backup files will be stored on the server where they are getting generated and can be downloaded afterwards. The storage location is completely configurable and can be even a remote location. For security reasons make sure the socket or web applications don't have delete permissions on any files at these locations.
+
+## Import
+
+The import of the backups is also straight forward by simply clicking import and selecting the backup file. In case the backup version is not support by the current application or module version you'll receive a error message. 
+
+During the import process it's also possible to choose which modules should be imported during the import process for better control. Before importing data into the application it's recommended to perform a backup in case of data corruption. In fact the application automatically offers you to perform a backup right before the import.