Recommendation for sharedservice.worker, instance.sec.user, ml_report.user usersIssue Recommendation for sharedservice.worker, instance.sec.user, ml_report.user usersReleaseAnyCauseThe customer reported 3 users which are seen OOB and asked what is the recommendation for these users? Can they be deactivated? What is their usage?ResolutionThese user roles is available and are included as part of the Predictive Intelligence plugin for (NLU - natural language understanding). The predictive intelligence app is being used by NLU app for utilization in Virtual Agent (chat bot) and AI Search (artificial intelligence search). If you plan to use these functionality and features then it is necessary for them to remain active The ml_report.user can be deactivated if you are not looking to do/use anything with NLU or any predictive intelligence features. However, if machine learning is not used customers may opt to disable the users but need to take note to activate them again if ML will be used. The recommendation is you can inactive if not using the NLU or any predictive intelligence features. The sharedservice.worker - When it comes to predictive intelligence, solution models have to be trained. This is the user that is used to run jobs to train the data.instance.sec.user - [PA AppSec] jobs use this user to run jobs.The recommendation is to keep them active but change the password to something complex and ensure that the "Web service access only" attribute is set to true.