**Requirements for a new Customer** __New customers using their own environment__ * Support Request Page - Deploy version for this customer. * ScottyPro - New workflow. * ScottyPro - New visibility/Market. * ScottPro QA - Update Transform scripts for reinit to account for the addition of new customer where relevant. __New SCO customers__ * Support Request Page - The fields Point of Contact and CC email need to only show that company's email addresses for non-admins. * ScottyPro - New workflow. * ScottyPro - New visibility/Market. * ScottyPro QA - Update Transform scripts for reinit to account for the addition of new customer where relevant. __New customers using their own environment__ * Support Request Page - Deploy version for this customer. * ScottyPro - New workflow. * ScottyPro - New visibility/Market. * ScottyPro QA - Update Transform scripts for reinit to account for the addition of new customers where relevant. __New SCO customers__ * Support Request Page - The fields Point of Contact and CC email need to only show that company's email addresses for non-admins. * ScottyPro - New workflow. * ScottyPro - New visibility/Market. * ScottyPro QA - Update Transform scripts for reinit to account for the addition of new customers where relevant. __Database updates/configs needed for new customer__ __In the Support Request config entry table__ The first two entries need to be updated: * The value for Customer - Visibility needs to be set to the market/Visibility of customer in ScottyPro * The value for Customer - Workflow needs to be set to the customer workflow in ScottyPro * The Support Request needs to be pointed to ScottyPro. __Kanban__ * Need to add customer to Kanban in ScottyPro. * Go to Kanban admin and select new and fill out the details. * Use current customer as reference. * Might have to add cluster to current user in Userprofile to see new customer visibility **__Adding Visibility in Database__** You won't be able to add new Visibility in ScottyPro, you will have to add it via the database. Add entry in the tables : * ticketer.visibility * ticketer.visibility_lookup