Powered by ZigaForm version 4.0

Deployment Strategy for Directory Creation Function

This function has arisen from the grievances surrounding the current exchange folders in most companies. Users are no longer working in such rigid environments. Collaboration is the new magic word. This is where the IT departments reach their limits. Why there are places in the file system where the complete security is compromised. There, each user can freely create directories and store "secret" data without any access protection.

In our projects we could see what dangers arise from such circumstances.
The most extreme example was the list of all HIV positive tested patients in a hospital for all 4000 MA in direct access. We could give many more examples. But that has an end!

With migRaven.24 / 7 Folder Self-Service Feature for creating directories with clearly defined permissions, a user creates the folders he needs on the basis of templates and can / must autonomously manage the permissions. This is fast and promotes self-responsibility.

In this PDF document you will find the extensive documentation for the use of the function by Admins and Enbenutzer:

Folder Selfe-Service User Guide - PDF

Templates make the system as flexible as possible

Templates include the combination of:

  • storage location
  • Type of authorization assignment
  • Retention period / automatic deletion
  • Group for which the template is unlocked
  • predefined directory structure

Examples of use

  1. Exchange folder with automatic deletion of the directory, the possibility to extend the runtime, to create the directories on a certain share. eg automatic deletion of the folder after 7 days and the owner (s) can extend the runtime twice per 2 days.
  2. Process directory with recertification of the directories and permissions after one year, are generated in a special process folder on the share x at location y. Authorizations are generated individually.
  3. Project folder with a fixed directory structure and different permissions on the subdirectories. Authorizations are set directly via role groups so that the tokenize or token count is not used.

The different forms of authorization assignment

migRaven can set permissions for different variants. This is done according to meaning and deviates from rigid "best practice" forms. Rights to exchange folders are assigned directly to the accounts, for example, because they only have a short existence and therefore no authorization groups are required.

The traceability or the reporting capability is by migRaven ensured. All authorizations are located in the DB and can therefore be understood or reported. Even if directories have not existed for a long time.

Permanent link to this post: https://help.migraven.com/einfuehrungsstrategie-fuer-funktion-verzeichniserstellung/