better documentation? Easier enumeration via bloodhound? #4

Hi,

can you please add more documentation?

For me it's not clear:
-why the solution needs: Privileged Access Management Feature
-how exactly the elevation process is working:

1. A schedule task (create group task) who create a group for each computer object.
2. A scheduled task to add a user to one of these tasks (what are these?). this task is triggered by an event
3. A powershell script which triggers the scheduled task (which one?)
   which task is RequestAdminAccess.ps1 triggering?
   should the AD identity requesting the admin access a different one then for the access itself?

-what is the advantage if you compare it with a powershell JEA endpoint on each machine that is adding a user to the local admin group?
-if the user session is continously logged in (lingering RDP session), it doesn't expire or does it?
-does the use of AD groups not allow an easier enumeration via bloodhound?

greetings
Carsten

PS: Very interesting project!!