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

Update Change Management.md

Browse Source
This commit is contained in:
Dennis Eichhorn 2022-07-25 18:18:41 +02:00 committed by GitHub
parent 1f5ef91cf5
commit 5f9d6ed7aa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
Policies & Guidelines/IT/Change Management.md
View File

@ -6,6 +6,10 @@ Permission changes are sometimes necessary if a role of an employee changes or i
Permissions should always be defined as low as possible and only get expanded if required. The IT department can decide to reject a permission change if they consider the request inappropriate.
Potential documents to be changed are:
* Permission List
### Flowchart
```mermaid
@ -24,6 +28,23 @@ graph TD;
## Software
Software changes include software updates, new software or functional/feature changes. Change requests can be made by any employee but must get approved by the respective HOD. If the change request is justified the IT department performs the change in a testing environment where the employee or HOD can test the change.
The IT department can decide to reject a permission change if they consider the request inappropriate.
Potential documents to be used are:
* Third Party Software Validation - New.md
* Third Party Software Validation - Update.md
Potential documents to be changed are:
* IT Equipment & Software
* Automated Jobs
* Permission List
* Approved Customer Software
* Key Supplier Evaluation
### Flowchart
```mermaid