# Application Configuration Make use of Tomorrow Software configuration features that allow for application configuration, avoiding the need for maintenance of custom configuration files. An advantage of the Tomorrow Software configuration is that access to the configuration can be centrally controlled through the Tomorrow Software console and permissions can be granted or revoked for any Tomorrow Software users. System administrators should ensure that the Tomorrow Software file system has restricted access, so that changes to the Tomorrow Software file system can only be done through the same user that executes the Tomorrow Software console Below is an example of a configuration that has “Global Fields” which are used to set application settings, that can easily be changed in the “Servers” node, once the configuration has been deployed. ![Maintain Configuration example](/files/zHCvRAoWzVcMVlYgnNsp) In the “**Servers**” node below, under the corresponding server to which our configuration has been deployed, we can change the application settings that have been declared as “**Global Fields**”. Under “**Server Settings**” choose “**Change..**”. These settings do not need a configuration redeploy to take effect. ![Server Settings](/files/yD1V0QPUo16b1HaOCTyU) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tomorrowx.com/cap/best-practices/application-configuration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.