applications are an easy way to logically separate different tables and functionality to assist in a logical separation of administrative capabilities or otherwise for the average user within the platform, this is not a concept they need to worry about and is a concept more so for the system administrator applications can be upgraded and deployed separately, which allows you to test and plan upgrades of different upgrades when is convenient for each group recommended practice when creating an application, it is recommended that it is set out in a way for a logical set of functionality (such as emails) or business unit (such as human resources) a simple way to determine if a new application makes sense is if you need to have a different role / permission set for the people who are fulfilling the processes an example of this is that your human resource term will be focused on cases around payroll or other workplace requests, but they would likely not be fulfilling it requests therefore, separating these two processes in two separate applications make sense contrarily if you have a different process, such as to deal with training requests, but the human resource team are the ones that fulfil these requests it may make sense to put them within the same application the more the processes differ, the more it make sense to separate them into two different applications, even if it is the same team fulfilling the requests an example of this is that an occupational health and safety processes are often quite varied from human resource processes, so even though it may be the same team who needs to handle both requests, it would make sense to create a new application finally, to assist with differentiating your applications with the standard servicely applications, it is recommended you prefix it with your company name for the namespace creating a new application to create an application, you need to follow the subsequent steps on the left menu, found under the "application" application menu and section, select the "applications" menu item press the "new" button the majority of recommended information will be defaulted the only fields we recommend you change and enter are as follows namespace we recommend the following format \<company name> \<application name> for example "acme ohs" name the name of the application as applications are an admin concept, we recommend keeping it lower case and separating words with underscores to assist with scripting the other fields will be automatically changed and populated as you install and manage your application all done at this point you can select the application via your user profile selecting your application once you have created your application, you should then select it for your user to ensure that configuration done for that application, is placed in the application to view selected application, please view under the change set mode options, next to your user's first name example below showing the "platform" application selected to select another application, please follow the steps below click your name in the top menu item to view the available menu actions and click on "user settings" once done, there will be an application drop down from this drop down, select the application press the "save" button at the bottom of the screen and your selected application will be what you chose on the previous step new configurations you perform such as creating new field or trigger or table operation, etc will result in those configuration record associated to your user's selected application