GOVERNANCE PART 3 by @danholme #ESCP13

Automation framework:
1. Request:……data points……………………. sps list
2. Workflow: …approval………………………. approval
3. Provision :…policies and logic………….. powershell
4. Proxy:……….elevation and isolation….. scheduled tasks
5. LOG:…………document…………………….. sps list
6. REPORT:……insight compliance………… Excel
(howest has work to do on this ) i often forget step 5. = to document

Create Howest service desk
1. List for Site Request:
      business owner =/= site owner, request step with the 6 steps above.
     Teamtype: opleiding, project, samenwerking, opleidingdoverschreidend, ….
      Yes/no for Records, confidential, PII, export controlled, confidential, allow all authenticated users users read access
       Base name for SP goup names + owners, members & visitor names
       Open. Docs in client application (not all groups have BOYD users 😉 )….
       Need lists?

2. Workflow runs
3. Someone or Powershell makes the site + script the documentation and the rest
You can do this for every request (ex make library)  instead of giving one administration rights. GENE will be happy 🙂

Things to remember: Our Howest IW services team have to even use more lists for our own tasks , documentation and reporting
Aha:branding = title and description field
I need to have a better idea of the ‘record’ concept.
Very usefull, practical session for me. Should I learn Powershell?