---
title: "UCM"
slug: "ucm"
description: "Understand UCM in Decisions, including how settings are migrated from the database to the file system, and how environment settings support Deployment Tower pushes."
updated: 2026-07-15T20:43:58Z
published: 2026-07-15T20:43:58Z
canonical: "documentation.decisions.com/ucm"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# UCM

## Overview

This article discusses the UCM changes introduced in [v10](https://documentation.decisions.com/v99/docs/about-version-10). These changes establish a unified configuration management system that enables centralized deployment, governance, and auditing of platform settings.

---

## UCM Updates

- Settings that were previously stored in the database have been migrated to the **File System**.
- Existing settings are preserved during upgrades.
- The Settings.xml format has been changed from **settings.xml** to **settings.json**.
  - **Application-level settings** have been removed from **settings.json** and moved to **applicationsettings**.
  - **settings.json** now contains only **node-specific settings** (e.g, file storage paths, ports, HTTPS certificates)
  - Logging configuration has been centralized and moved to:
    - **/filestorage/primary/settings/config**