Idea ID 1688026
But larger CSA instances you will have multiple Teams taking care for different Usecases/Designs or even on Offering Level ... eg. Design A -> Offering 1 is for Customer 1 and supported by Team 1 but Design A -> Offering 2 is for Customer 2 and supported by Team 2.
this implies that not one Support team is sufficent any more on Org level but best would be on Offering Level.
this allows CSA to be used for larger Enterprises
a model similar to the different Roles in the MPP would be needed here... split down the Service Operator Role on Provider Side into different Service Operator Teams authorized by LDAP being responsible for a set of Offerings.
Using a catalog is probably not good as with Customer Admin Role customers can sort offerings them self into catalogs interfering with Operations Model
when creating offerings you select an Service Operations Team (or stick with classic -> Serivce Operator Role) when a Member of the Service Operations Team log into Provider Org he/she will have Service Operator Role for just those Offerings.
Cloud Svc Automation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.