Description


To give access to keys, there is a couple of different steps to do, along with which licences that need to be purchased. 


Process


For access to Keys, there is 3 items that need to be completed.


1) User to be licenced

2) User to be given access to an environment

3) User to be given environment roles.


If the user does not appear in Keys to add the roles to/we've run out of licences, we need to add more.

4) Checking and purchasing licences


1) User to be licenced


There is 3 cloud licence groups

  • GRP.KeysCRM.Lic.Service
  • GRP.KeysCRM.Lic.Sales
  • GRP.KeysCRM.Lic.SalesAndService


Which group a user goes in depends on which roles they are getting, below is the logic for this:


GRP.KeysCRM.Lic.Service

The user is in a customer service team/technician etc. having the role in Dynamics of “Bovis - Base (Care)” and does not need any of the roles under GRP.KeysCRM.Lic.Sales

 

 

GRP.KeysCRM.Lic.Sales

The user is in a sales/marketing etc. primarily having one of the role in Dynamics of "Bovis - Base (Sales)", "Vistry Group Administrators", "Vistry Regional Marketing Administrator", "Vistry Regional Sales Administrator", "Vistry Group Call Centre Sales Consultant", "Vistry Regional / Hub-based Sales Consultant", "Vistry IT Support" and does not need any of the roles under GRP.KeysCRM.Lic.Service

 

 

GRP.KeysCRM.Lic.SalesAndService

This roles licence group is for any users that would need to be included in both of the group above, do not add them to both groups above, just this one. Its also used for admin roles as well.


Please bear in mind, if they are accessing sales in one environment and Service in another, they will need the dual licence (SalesAndService).



2) User to be given access to an environment


Once they have been given a licence, they will need adding to the environment, there is several, this is done via adding to the security group.


GRP.KeysCRM.LIV - This is the live environment, a user setup form should have been completed.

GRP.KeysCRM.TRN - This is the training environment, users are added at the request of L&D for courses.


The remaining environments have special purposes, and the requests should come from/be approved by the Keys team and not users.

GRP.KeysCRM.DEV

GRP.KeysCRM.UAT

GRP.KeysCRM.SIT

GRP.KeysCRM.SUP

GRP.KeysCRM.PRA



3) User to be given environment roles.


One the above two steps have been done, then the System Support team/Keys team will need to configure the user in Keys.




4) Checking and purchasing licences

You can check the licence status by going to https://admin.microsoft.com/Adminportal/Home?source=applauncher#/licenses and look under billing, if these are 0 available licences, then we need more (once we have checked if there is any not in use).


Licences are purchased from the Bytes portal by someone with permissions, these relate to the above licences.