Test scenario:
Create/Update batch api will accept an attribute "premissionMap" with key as userId and value as list of permission , user is having.
when ever update batch api call came system need to check the caller authentication , call must be either creator or Mentor.
Added mentor must be part of same rootOrg
If a mentor has view access then he/she can view course batch but can't edit it.
if a mentor has edit access then he/she can add or remove any user (mentors or participant ) even he/she can remove batch creator as well (if creator is in mentor list.
Any added mentors should be allow to update course batch
During batch update i can update mentors list , what ever mentor list i will receive in request should be final list.
During batch create i can pass participant list
During batch update i user can pass updated participant list
Once batch end date is today or passed they can't remove added participant
Once any participant completed 100% then they can't be removed
Removed participant can be added back to batch if batch is not closed.
Removed participant history need to be maintain.